Statamic Assessments Laravel Package

Product Decisions This Supports

• Control Panel information architecture. v0.3.2 makes the addon declare settingsNavParent() — a [section, name] pointer to its own CP navigation entry. When statamic-brand-context ≥ 1.16 is present, settings render as a sub-item ("Einstellungen") under that entry; when absent, the previous layout is retained. This is an admin-UX decision, not an end-user feature: it determines how much CP surface area a single addon should own versus deferring to a suite-level shell.
• Single addon vs. product suite packaging. The documented fallback — addons without their own navigation share one "Addon-Suite" page under Settings — is a signal that a multi-addon suite is a first-class, supported deployment pattern. Relevant to build-vs-buy and to whether we ship capabilities as one addon or a family.
• Sibling-package upgrade policy. Behavior is version-gated on statamic-brand-context 1.16+. Feature parity therefore depends on a dependency's version, which argues for tracking that package in our upgrade cadence rather than treating it as incidental.
• Release scheduling / risk budget. Explicitly no migration and no new config key, with graceful degradation on older brand-context. This is a routine dependency bump, not an upgrade project — do not allocate migration or QA regression budget beyond a normal patch cycle.
• Roadmap positioning. No new user-facing capability; this is admin organization polish. Do not market it to end users, and do not let it displace roadmap items. It does make the addon marginally more attractive in a suite bundling conversation.

When to Consider This Package

Adopt when: you are on Statamic and need addon settings surfaced in the Control Panel; you already run statamic-brand-context 1.16+ (or are willing to upgrade to get the improved placement); you accept a pre-1.0 (0.x) version with the API-stability caveats that implies; and you are comfortable with settings living either under your own nav entry or in a shared "Addon-Suite" page.

Look elsewhere when: you are not on Statamic; you require SemVer stability guarantees this package's 0.x version does not offer; you are pinned below brand-context 1.16 and the new nav placement is a hard requirement (you'll get the old layout); or a shared "Addon-Suite" Settings page conflicts with your own CP navigation conventions. Also reassess if the settings UI is the only capability you need — a config file or a small in-house panel may be cheaper than a dependency.

Confidence note: this assessment is derived from the v0.3.2 release notes alone; feature scope, licensing, and maintenance posture have not been independently verified and should be confirmed before a build-vs-buy commitment.

How to Pitch It (Stakeholders)

Executives: Low-risk maintenance release with no migration and no new configuration. It tidies where the addon's settings appear in the admin Control Panel and keeps older setups working exactly as before. No new cost, compliance, or support surface. Treat it as a routine dependency bump.

Engineering: Patch-level change. The addon now implements settingsNavParent() returning the [section, name] of its own CP nav entry; statamic-brand-context ≥ 1.16 uses it to nest settings as "Einstellungen," and older versions ignore the method and fall back to the prior layout. Addons without their own nav consolidate under a shared "Addon-Suite" Settings page. No migrations, no new config keys — safe to absorb in a standard dependency update, with the only coordination point being our pinned brand-context version.