Statamic Iconify Laravel Package

Product Decisions This Supports

• Build vs. buy for icon selection: Avoid building a custom icon picker for Statamic. This release adds configuration, filtering, cached API-backed dropdowns, and test coverage—capabilities that usually justify buying/adopting over maintaining bespoke CP JavaScript.
• Design-system governance: Global config/statamic-iconify.php lets teams lock down allowed icon sets, categories, and licenses site-wide. Field-level controls can only narrow the global allowlist, preventing editors from widening scope accidentally.
• License and brand compliance: Restricting by license (e.g., MIT, Apache 2.0) and icon set prefix supports legal/procurement reviews and reduces the risk of shipping incompatible or off-brand icons.
• Editor experience and content velocity: Native Statamic dropdowns, search-modal filter badges, grouped badges, and dark-mode fixes reduce editor friction and support self-serve content production.
• Multi-brand / multi-site roadmap: Global defaults plus per-field filtering make it easier to support different brands, sites, or content types while keeping centralized guardrails.
• Operational cost and performance: Iconify /collections metadata is cached for 24 hours, limiting API overhead while keeping configuration usable in the control panel.
• Platform roadmap inputs: The release highlights where the product is maturing—configuration governance, field-level constraints, cached metadata, CP config endpoint, and Pest/Vitest suites. It does not yet signal full digital asset management, granular role permissions, or audit logging.

When to Consider This Package

Consider adopting when:

• You are already using Statamic and need an Iconify-based icon field in blueprints.
• Content editors need a searchable icon picker inside the Statamic control panel.
• You need centralized control over allowed icon sets, categories, or licenses.
• You want field-level filtering that respects—but cannot override—global governance rules.
• You prefer a native Statamic field over a custom Vue/JS icon picker and are comfortable owning a small addon dependency.
• You can tolerate dependency on the Iconify API for collection metadata, with 24-hour caching.

Look elsewhere or validate further when:

• You are not on Statamic; this is not a general Laravel icon package.
• You need an offline/air-gapped icon library with no external API dependency.
• You need full digital asset management, icon uploads, custom proprietary icon libraries outside Iconify, versioned asset workflows, or audit trails.
• You require granular per-role permissions beyond global and field-level configuration.
• You cannot accept addon maintenance or need formal vendor support/SLA.
• You have strict supply-chain requirements and need to review the package’s API calls, caching behavior, and license posture before adoption.

How to Pitch It (Stakeholders)

For executives: This package gives Statamic content teams a governed icon picker without a custom build. The new release is mainly a risk-control and editor-productivity update: administrators can limit icon sets, categories, and licenses globally, while individual fields can be made stricter. That supports brand consistency and license compliance while reducing bespoke frontend maintenance.

For engineering: It is a Statamic addon with publishable configuration, field-level filtering via native select dropdowns, Iconify collections metadata cached for 24 hours, a CP config endpoint, and Pest/Vitest test suites. The main adoption considerations are Statamic/PHP version compatibility, external Iconify API dependency, and whether the current governance controls are sufficient versus a more formal DAM or asset-management system.