Statamic Clientrooms Laravel Package

Product Decisions This Supports

• Control Panel information architecture: v0.9.2 adds settingsNavParent() so the addon can declare which Control Panel navigation entry its settings belong under. PMs can decide whether settings should appear as a dedicated sub-item (“Einstellungen”) under the addon’s own nav entry or share an “Addon-Suite” settings page with other addons.
• Upgrade sequencing and compatibility: The improved placement depends on statamic-brand-context 1.16+. Older versions ignore the method and keep the previous layout. This supports a phased rollout decision: upgrade brand-context when consistent addon settings navigation matters, without forcing an immediate breaking change.
• Portfolio consistency: For teams maintaining multiple Statamic addons with settings, this pattern supports standardizing where settings live and reducing one-off navigation implementations.
• Release risk management: The release has no migration and no new config key, making it suitable for routine maintenance windows and low-ceremony deployment.
• Support and discoverability: Better settings placement can reduce “where are the settings?” support requests, but only for installations on the newer brand-context version.

When to Consider This Package

• Consider it when building or maintaining Statamic addons that expose Control Panel settings and you want predictable navigation placement under an existing addon entry or shared Addon-Suite page.
• Consider it if you are already on, or plan to upgrade to, statamic-brand-context 1.16+ and want the newer settings layout.
• Consider it when multiple addons in a suite need consistent settings grouping rather than scattered or custom navigation.
• Look elsewhere if you are not building on Statamic, do not expose Control Panel settings, or need navigation behavior independent of statamic-brand-context.
• If you are pinned to an older brand-context version, this release is effectively inert for navigation and does not create urgency; the previous layout remains.

How to Pitch It (Stakeholders)

Executives: v0.9.2 is a low-risk UX alignment release. It makes addon settings easier to find by placing them under the addon’s own Control Panel navigation entry when statamic-brand-context 1.16+ is present; older versions keep the current layout. There is no migration and no new configuration, so upgrade cost and operational risk are minimal.

Engineering: The addon now declares settingsNavParent() with the [section, name] of its own Control Panel navigation entry. With brand-context 1.16+, settings appear as the “Einstellungen” sub-item; addons without their own navigation share an “Addon-Suite” page under Settings. Older brand-context versions ignore the method. Test both brand-context version ranges, but no data or config changes are required.

Product: This improves admin discoverability and suite consistency without customer-facing breaking changes. The main product decision is whether to upgrade brand-context to unlock the improved placement and whether to adopt the same settings-navigation convention across the addon portfolio.