Statamic Assessments Laravel Package

Getting Started

• Upgrade to v0.3.2 normally: there is no migration and no new config key.
• First check whether statamic-brand-context is installed and whether it is version 1.16 or newer. That version is what makes the new settingsNavParent() declaration take effect.
• First use case: open the Control Panel and verify where this addon’s settings appear. On brand-context 1.16+, they should show as the “Einstellungen” sub-item under the addon’s own CP navigation entry.
• If the addon has no CP navigation entry of its own, expect its settings to appear on the shared “Addon-Suite” page under Settings.

Implementation Patterns

• Treat settingsNavParent() as the integration point when an addon has its own Control Panel navigation entry and wants settings nested under it. It returns [section, name] matching that navigation entry.
• Keep the returned section/name aligned with the addon’s registered CP navigation. If you maintain a similar addon, declare the method in the service provider and reuse the same identifiers used for navigation registration.
• For addons without their own CP navigation, do not add settingsNavParent() just to force placement; letting brand-context group settings under the shared “Addon-Suite” page is the intended fallback.
• During local development, test against both brand-context 1.16+ and older versions if the project supports older installs. The settings layout intentionally differs by brand-context version.

Gotchas and Tips

• Older statamic-brand-context versions ignore settingsNavParent() and keep the previous settings layout. Do not treat that as a regression in this addon.
• Because v0.3.2 has no migration and no new config key, upgrade risk is low; deploy normally and clear CP/cache if navigation changes do not appear immediately.
• The return shape must be exactly [section, name], and the values should match the addon’s CP navigation entry. Mismatches can leave settings in the fallback/shared location.
• Debug settings placement by checking the installed brand-context version first, then the addon’s CP navigation registration. There is no config toggle for this behavior.
• If the addon intentionally has no CP navigation, the shared “Addon-Suite” page is expected behavior, not a missing configuration.