Statamic Teams Laravel Package

Getting Started

• Install/upgrade with Composer, then clear caches (php artisan cache:clear, php artisan statamic:stache:clear if applicable). No migration or new config key is required for v0.4.2.
• First place to look is the addon’s Control Panel navigation registration and its settingsNavParent() method. Confirm it returns a [section, name] pair matching an existing CP nav entry.
• First use case: after upgrading, open the Control Panel and verify the addon’s settings appear as the “Einstellungen” sub-item under its own navigation entry when statamic-brand-context 1.16+ is installed. If the addon has no nav entry of its own, expect settings to appear under the shared “Addon-Suite” page under Settings.

Implementation Patterns

• Treat settingsNavParent() as the single source of truth for where settings live. If you maintain an addon that declares CP navigation, return the same [section, name] used by that navigation entry so brand-context can nest settings correctly.
• For addons without their own CP navigation, do not force a custom parent; let the shared “Addon-Suite” settings page handle placement.
• When integrating with statamic-brand-context, check the installed version at runtime or in your service provider before relying on nested settings behaviour. On versions below 1.16 the method is ignored and the previous layout remains, so no conditional code is strictly required.
• In day-to-day development, use this as a low-risk upgrade: deploy, clear caches, and visually confirm the settings entry in the CP. No data migration or config publish step is needed.

Gotchas and Tips

• Older statamic-brand-context versions silently ignore settingsNavParent(). This is expected and not a bug; the settings keep their previous layout.
• The [section, name] pair must exactly match an existing CP navigation entry. A typo or renamed nav entry can cause settings to fall back to the shared “Addon-Suite” page.
• Since v0.4.2 adds no config key or migration, rollback is simple: downgrade the package and clear caches. There is no schema or config cleanup required.
• Debugging tip: if settings appear in the wrong place, first confirm the brand-context version, then inspect the return value of settingsNavParent() and compare it with the addon’s registered navigation.
• Extension point: override settingsNavParent() in your own addon to deliberately group settings under a different existing CP nav entry when that improves discoverability.