Statamic Figma Assets Laravel Package

Getting Started

• Check your Statamic version first. v2.0.0 is a Statamic 6 migration, published as a major. That means the 2.x line almost certainly constrains statamic/cms to ^6.0. If your app is still on Statamic 5, do not chase this release — pin the addon to ^1.0 and stay there until you plan the Statamic 6 upgrade.
• Install on a Statamic 6 app with composer require <vendor>/<package>:^2.0, then publish anything shippable: php artisan vendor:publish --provider="<Vendor>\<Package>\ServiceProvider" (config, views, and possibly translations).
• Follow with php artisan statamic:stache:clear && php artisan cache:clear before opening the Control Panel. Addon upgrades that touch fieldtypes or Vue components routinely leave a stale Stache index behind, and the resulting errors look like code bugs.
• Where to look first: the addon's src/ServiceProvider.php (what it registers — fieldtypes, tags, modifiers, navigation, permissions), config/*.php (the knobs you'll actually touch), and resources/js/ (the Vue components registered with the CP). With Statamic 6 the frontend build is Vite-based, so also open vite.config.js and confirm there's a committed dist/ or a build step in your pipeline.
• First use case: drop the addon's fieldtype into a blueprint and confirm it renders in the CP with a clean browser console. That single check exercises composer resolution, service provider boot, component registration, and asset manifest — it's the fastest signal that the Statamic 6 migration is wired correctly end to end. Only after the CP renders cleanly is it worth testing content round-tripping in templates.
• Expect to rebuild/refresh the CP assets after install. If the addon publishes resources/js, run the addon's build (or npm run dev inside the package when working from a path repository); a missing manifest shows up as a blank field or a "component not found" warning.

Implementation Patterns

• Blueprint-first usage. Add the fieldtype through the CP and let it write YAML, or hand-edit resources/blueprints/**/*.yaml and mirror it into version control. Treat the blueprint YAML as the source of truth and the CP as a convenience — it makes config drift visible in code review when you upgrade the addon.
• Reading values in PHP: prefer the fieldtype's augmentation over reaching into raw data. $entry->augmentedValue('field')->value() (or $entry->get('field') if the addon ships a value object/cast) keeps your templates stable if the addon changes its storage shape — which is more likely than usual across a Statamic major.
• Antlers/Blade surface: the addon's tag or modifier is the intended public API. Wrap it in a small partial or Blade component in your app rather than sprinkling tag syntax through templates, so the Statamic 6 migration surface is a handful of files rather than dozens.
• Vue components in the CP: Statamic 6 ships a shared component layer, and this release explicitly adopts it. If you maintain custom fieldtype UI on top of this addon, compose the addon's registered components from your own via props/slots rather than forking the SFCs into your app — forking is what turns a patch release into a rewrite next time.
• Local dev loop: use a Composer path repository (or composer link-style symlink) with the addon checked out, plus npm run watch inside it. Hot-reloading the CP while you edit templates is dramatically faster than composer update per iteration, and it's the only practical way to debug component prop mismatches.
• Deployment: build assets in CI and ship dist/, or rely on the addon's committed vendor build. Never add npm install to a production deploy. After deploy, run php artisan statamic:stache:warm so the first request isn't paying the rebuild cost.
• Headless/API consumers: if this addon exposes data through Statamic's REST or GraphQL layer, add a smoke test against the endpoint in CI. Addon majors are a common source of silently changed serialized shapes.

Gotchas and Tips

• The version constraint is the whole story of this release. Composer will happily keep you on 1.x if your app is on Statamic 5, so composer show <vendor>/<package> after upgrading — don't assume the major landed.
• Minimum platform requirements shifted. A Statamic 6 migration implies PHP 8.2+ and a modern Laravel (11/12). Check composer.json's require block before you plan the upgrade window; the addon bump may be the smaller half of the work.
• Custom Vue code is the likely breakage point. If you extended the addon's CP components, any import from an internal @statamic/cms/... path, any reliance on renamed props, or any old Statamic.$components.register() bootstrapping needs re-testing against the new shared components. Vue warnings in the console are the leading indicator; a silently unregistered component usually renders as an empty pane rather than an error.
• "Component not found" after upgrade is almost always cache. Do a hard refresh on the CP (Ctrl+Shift+R), then php artisan cache:clear && php artisan view:clear. The CP asset manifest is hash-versioned, and a stale bundle referencing old filenames produces errors that read like missing code.
• Stache indexes can go stale across majors. If content looks wrong or fields come back null, php artisan statamic:stache:clear before you start debugging the addon itself.
• Extension points before hacks: publish the config and views, and use the addon's documented registration hooks. Overriding a core component by registering a same-named one later in boot order works but is fragile across majors — if you find yourself doing it, it's a signal to open an upstream issue instead.
• Read the changelog, not just the release title. "Migrate to Statamic 6" is the only line here, so the real upgrade guide is the diff and the README's requirements table. Confirm whether stored data format changed; if it did, plan a backfill or a rollback path before upgrading production.
• If you're on Statamic 5, this release is a no-op. Don't take the major for "staying current" — a v2.0.0 on a new Statamic major is a coupling decision, and it should land in the same PR as the Statamic upgrade, not before it.