Iconamic Laravel Package

Product Decisions This Supports

• Roadmap timing for Statamic upgrades: Version 3.0.0 adds Statamic 6 support, which unblocks any initiative that requires the CMS upgrade. If Statamic 6 is on the roadmap, this package moves from "blocker" to "resolved" — but confirm whether 3.x also supports Statamic 5 or is a hard fork in the road.
• Build vs. buy for icon management: Icon sets, SVG sprite handling, and an in-CMS icon picker are commodity capabilities. This package removes a build task from the backlog; the decision is now "adopt or skip," not "adopt or build."
• Major-version migration cost: The 3.0.0 semver bump is the PM-relevant signal. Any project pinned to 2.2.3 must assume breaking changes and budget an upgrade ticket rather than a routine dependency bump.
• Content author workflow: Icon selection inside the Statamic control panel is an editor-experience feature. Value should be framed against editorial time saved and reduction in developer hand-holding for adding icons to pages.
• Scope check: This is a narrow, single-purpose addon. It should not be evaluated as a design-system or asset-pipeline solution.

When to Consider This Package

Adopt when:

• You run (or are migrating to) Statamic 6 and need icon picker/fieldtype functionality in the control panel.
• Your icon needs are modest and editor-facing — selecting from a defined set, not generating sprites, optimizing SVGs, or managing a full icon design system.
• You want maintained, vendor-supported compatibility rather than an in-house fieldtype you'd have to keep in sync with CMS major releases.
• Your team is comfortable with a small third-party addon in the critical content-editing path.

Look elsewhere or hold when:

• You are on Statamic 5 and not upgrading soon. 3.0.0's headline is Statamic 6 support; verify whether Statamic 5 remains supported. If not, stay on 2.2.3 and track it as technical debt with an upgrade trigger.
• You need asset optimization, SVG sanitization at scale, or a design-token-driven icon system — this isn't that.
• Single-maintainer dependency risk is unacceptable for the workflow; check issue responsiveness and release cadence before committing.
• The icon picker is a nice-to-have and a plain asset field or a text field with a naming convention would satisfy editors.

How to Pitch It (Stakeholders)

To executives: A small, low-cost addon that gives content editors a proper icon picker inside our CMS instead of a developer-assisted workaround. The new 3.0.0 release adds support for Statamic 6, which means it no longer blocks our CMS upgrade path. Cost is a dependency bump plus a short upgrade ticket, not a build project.

To engineering: Statamic icon-fieldtype addon, now at 3.0.0 with Statamic 6 compatibility. Treat the major version bump as a breaking change: validate Statamic 5 support status, review the diff between 2.2.3 and 3.0.0, and pin deliberately. Confirm test coverage of the control-panel fieldtype before rollout, and check maintenance signals (release frequency, single-maintainer risk) since this sits in the editorial critical path.