Statamic Booking Laravel Package

Product Decisions This Supports

• Approve v1.7.0 as a low-risk upgrade: it is a settings-navigation integration release with no migration and no new config key.
• Improve Control Panel UX for Statamic sites using statamic-brand-context 1.16+: the addon’s settings can appear as the sub-item “Einstellungen” under its own navigation entry.
• Support multi-addon administration: addons without their own navigation can share an “Addon-Suite” page under Settings, reducing settings sprawl and admin confusion.
• Reinforce a buy/adopt decision for teams that want native Statamic settings integration rather than maintaining custom Control Panel navigation code.
• Roadmap signal: this is a polish/compatibility release, not a major capability expansion. Treat it as maintenance and ecosystem-alignment work.

When to Consider This Package

• Consider adoption or upgrade if you run Statamic, use statamic-brand-context 1.16 or newer, and want addon settings surfaced more cleanly in the Control Panel.
• It is especially relevant for sites with multiple addons where settings discoverability and consolidated navigation matter.
• It is also a good fit when low-risk upgrades are important: v1.7.0 requires no migration and no new configuration.
• Look elsewhere or defer if you are not on Statamic, do not use statamic-brand-context, are pinned to an older brand-context version and cannot upgrade, or need functionality beyond Control Panel settings navigation.
• Older brand-context versions ignore the new method and keep the previous layout, so the release is backward-compatible but delivers its main UX benefit only with newer brand-context versions.

How to Pitch It (Stakeholders)

For executives: v1.7.0 is a low-risk maintenance release that improves admin usability by making addon settings easier to find in the Statamic Control Panel. There are no migrations or new config keys, so rollout risk and operational cost are low.

For engineering: the addon now declares settingsNavParent() with the [section, name] of its Control Panel navigation entry. With statamic-brand-context 1.16+, settings appear as “Einstellungen” under that entry; addons without their own navigation share an “Addon-Suite” Settings page. Older brand-context versions ignore the method, preserving existing behavior. Upgrade is safe and primarily a UX/ecosystem alignment change.