Statamic Choices Laravel Package

Product Decisions This Supports

• Content modeling / editorial UX roadmap: Evaluate whether to adopt a dedicated “choices” fieldtype for Statamic blueprints instead of relying on built-in select fields or custom fieldtype development.
• Build vs. buy for Control Panel UI: Informs whether to spend engineering time building a Vue/Vite-powered fieldtype or adopt this package to accelerate delivery of configurable choice/option selection in the CMS.
• Pilot and prototype decisions: At v0.1.x, the package is best positioned for internal tools, prototypes, or low-risk editorial sites where faster iteration outweighs long-term API stability.
• Adoption friction reduction: The v0.1.1 fix—automatic asset publishing after composer require—removes a common first-install failure (Vite manifest not found), making trials, CI setups, and developer onboarding more reliable. This directly supports “can we test this quickly?” decisions.
• Dependency risk tracking: The release cadence and scope indicate an early-stage addon. PMs should treat it as an experiment, not a platform-critical dependency, until the package matures.

When to Consider This Package

Consider adoption when:

• You are building on Statamic v5 or v6 and need a Control Panel fieldtype for managing choices/options that goes beyond the default select field.
• You want a Composer-installable addon with packaged frontend assets and minimal setup; the new automatic asset publishing improves the “try it in a sandbox” experience.
• You are comfortable with pre-1.0 software: expect possible breaking changes, limited documentation, and API churn.
• You have a non-critical use case—internal tools, editorial prototypes, or projects where a custom fieldtype build would otherwise consume sprint capacity.
• You can validate the package in a sandbox before committing it to a client-facing or long-lived product.

Look elsewhere when:

• You require stable APIs, long-term support, or vendor SLAs; v0.1.x is not appropriate for platform-critical dependencies.
• The built-in Statamic select/choice capabilities already satisfy the editorial requirement.
• Your team cannot absorb the risk of an early-stage addon or lacks capacity to fork/maintain it if needed.
• You need a PHP-only solution or cannot support a Vite-built Control Panel asset pipeline.

How to Pitch It (Stakeholders)

For executives: This is a small, early-stage Statamic addon that can reduce custom development for editorial choice fields. The latest release fixes a first-install asset issue, lowering trial friction. It is not yet mature enough to treat as a platform dependency—recommend a limited pilot in a non-critical project, with a build-vs-buy review if adoption expands.

For engineering: The package is a Composer-installable Statamic v5/v6 addon with a Control Panel UI. v0.1.1 automatically publishes its Vite build to public/vendor/statamic-choices/build after install, eliminating the Vite manifest not found failure common in fresh sandboxes and CI. The fix is narrow and CI-verified, but the package remains pre-1.0: budget time for sandbox validation, dependency pinning, and a fallback custom fieldtype if the addon stalls.