Statamic Booking Laravel Package

Technical Evaluation

• Architecture fit: The package is a Statamic addon within a Laravel/PHP stack. This release adds settingsNavParent() to declare its Control Panel navigation parent, integrating with statamic-brand-context (v1.16+). This is a presentation-layer change with no data model or core logic impact.
• Integration feasibility: Straightforward for existing Statamic installations. No migration or new config key. Requires statamic-brand-context 1.16+ to activate the new settings sub-item layout; older versions safely ignore the method and retain the previous layout.
• Technical risk: Low. The change is additive and guarded by version checks. No breaking changes, no database changes, no configuration changes. Risk is limited to UI navigation placement if dependency versions are mismatched.
• Key questions: What is the minimum supported statamic-brand-context version? Does the addon declare a hard or soft dependency? Are there any Control Panel permission implications for the new settings entry? How does the fallback layout behave for users on older brand-context versions?

Integration Approach

• Stack fit: Compatible with Laravel and Statamic addon conventions. Uses Statamic’s Control Panel navigation APIs and the statamic-brand-context addon for shared settings pages.
• Migration path: No migration required. Existing installations upgrade normally via Composer. No config or database changes.
• Compatibility: Backward compatible. Older statamic-brand-context versions ignore settingsNavParent() and keep the previous settings layout. Newer versions (1.16+) render the addon’s settings as “Einstellungen” under its own navigation entry.
• Sequencing: To adopt the new layout, upgrade statamic-brand-context to 1.16+ first, then upgrade this addon to v1.7.0. No strict ordering required for functionality; the change is cosmetic until both are in place.

Operational Impact

• Maintenance: Minimal. No new configuration, migrations, or scheduled tasks. The change is isolated to settings navigation declaration.
• Support: Low support burden. Users on older brand-context versions see no change. Documentation should note the dependency version for the new layout.
• Scaling: No impact on performance, caching, or scaling. Navigation declaration is resolved at Control Panel render time.
• Failure modes: If statamic-brand-context is absent or below 1.16, the method is ignored and the previous layout persists. No fatal errors expected. Potential confusion if users expect the new layout without upgrading the dependency.
• Ramp-up: Minimal. Developers familiar with Statamic addons can adopt immediately. No new APIs beyond the optional navigation parent declaration.