Product Decisions This Supports
- Editor UX for set-heavy content models. This addon adds a header toggle for Statamic "Sets" in the Control Panel — a quality-of-life affordance that makes long, set-driven publish forms (page builders, flexible content blocks, modular landing pages) easier to scan and collapse. It directly affects editor satisfaction and time-to-edit on the content types where Sets are used most.
- Statamic 5 upgrade planning. v1.1.0 is a compatibility release: Statamic 5 support. If this addon is in
composer.json, it is a gating dependency for the Statamic 5 upgrade. That makes this release a roadmap enabler rather than a feature.
- Build vs. buy (buy/borrow). The capability is small and CP-only. Adopting a free, single-purpose OSS addon is cheaper than building and maintaining custom Control Panel JS or a forked fieldtype that must be re-validated on every Statamic major.
- Roadmap signal. Continued maintenance across a Statamic major is a positive health signal for a micro-addon. It does not justify new roadmap investment on its own, but it de-risks keeping it in the stack.
- Non-decision. This release changes nothing about data structures, APIs, or content modeling. It should not drive architecture or vendor decisions.
When to Consider This Package
Consider it when:
- You are on Statamic (3.4+ through 5) and use Sets meaningfully — especially multiple sets per entry or deeply nested sets — and editors have flagged long or unwieldy publish forms.
- You are upgrading to Statamic 5 and this addon is already installed: bump to v1.1.0 as part of the upgrade train, and verify the toggle renders correctly in the new CP.
- You want a zero-cost, low-surface-area UX improvement with no database, migration, or content-model impact.
Look elsewhere or skip it when:
- You are not on Statamic, or you use Replicator/Grid/Bard rather than Sets — the toggle does not apply.
- You are on Statamic 2 or pre-Sets 3.x — no compatible target for this release.
- Your team already handles this with Control Panel CSS or a custom CP customization, in which case adding a dependency buys you little.
- Maintainer risk matters more than the feature. This is a single-maintainer, single-feature addon with sparse release notes. Treat it as a convenience, not infrastructure: acceptable for editor ergonomics, inappropriate anywhere it could block publishing workflows if abandoned. Confirm it is not on a critical path and that removing it degrades gracefully.
- Verify whether native Statamic 5 CP behavior already covers the need before adding the dependency.
How to Pitch It (Stakeholders)
To executives: This is a small, free, open-source addon that improves the editing experience in our Statamic CMS by letting editors collapse section headers in complex content forms. The new v1.1.0 release adds Statamic 5 support, which keeps us on a currently supported platform version and removes a blocker from our CMS upgrade. Cost is negligible; risk is low because it only touches the admin interface — no content, database, or customer-facing changes.
To engineering: v1.1.0 is a compatibility-only release adding Statamic 5 support; the changelog contains no breaking changes, deprecations, or API changes. Action is a routine version bump in composer.json plus a staging pass over representative set-heavy publish forms (expand/collapse state, nested sets, reordering). Because the addon is CP-only and single-maintainer, keep it out of critical paths, pin the version, and confirm that disabling it leaves the Control Panel fully functional.
Caveat on this assessment: There is no prior assessment and the release notes are a single line, so this is a baseline evaluation. Confidence is high on compatibility impact, moderate on feature-level fit; validate the editor-UX value with the content team before treating it as a standard part of the Statamic baseline.