Product Decisions This Supports

Feature scoping: Decide whether to add icon selection to Statamic-driven content types instead of building a bespoke field or hard-coding icons in templates.
Build vs. buy: Use this package as a low-cost extension for editor-friendly icon picking rather than maintaining custom fieldtype JavaScript/PHP.
Roadmap fit: Supports design-system and brand-consistency work where editors need to choose approved icons from a controlled set.
Upgrade decision: 1.1.0 improves the authoring experience by using Statamic’s native icon picker and simplifies configuration by adopting unprefixed icon keys now supported upstream. No explicit breaking changes are called out, but teams with published configs should verify key names during upgrade.
Use cases: Marketing pages, navigation/settings schemas, feature grids, callouts, service listings, and other repeatable content blocks where non-technical editors select icons.

When to Consider This Package

Consider it when the product runs on Statamic and content authors need a native, CMS-native way to choose icons.
Good fit when the icon set is already curated and the team wants minimal custom UI, simple config, and alignment with Statamic conventions.
Evaluate 1.1.0 specifically if the project is on a Statamic version that includes the upstream support for unprefixed icon config keys and native icon picker fields.
Look elsewhere if the product is a non-Statamic Laravel app, needs advanced icon management such as SVG upload, tagging, search across large libraries, licensing enforcement, or cross-CMS portability.
Avoid or defer if the team has a strict minimal-addon policy, needs guaranteed long-term API stability without config migration checks, or already has a mature internal icon-picker component.

Executives: This is a small, targeted improvement to editorial workflow. Version 1.1.0 reduces custom UI surface by using Statamic’s native icon picker and simplifies configuration, lowering maintenance risk while improving content-team usability.
Engineering: The package now leans on native Statamic behavior instead of a custom picker and adopts unprefixed icon config keys enabled upstream. Upgrade risk appears low, but validate published config keys and confirm the required Statamic version before rollout.
Product/Content ops: Editors get a more familiar icon-selection experience, and the product can standardize icon usage without adding bespoke tooling. Treat 1.1.0 as an enhancement release, not a strategic replatforming decision.