Statamic Affiliates Laravel Package

Product Decisions This Supports

• Adoption/upgrade sequencing: v0.2.1 is a zero-risk upgrade (no migration, no new config key), so it can ride along with any routine dependency bump rather than needing its own release slot.
• Control Panel information architecture: The addon now declares settingsNavParent(), letting its settings render as the sub-item "Einstellungen" under its own CP navigation entry instead of floating loose. This is a UX/discoverability decision for admins, not a new capability — relevant if CP tidiness is part of your client handoff or white-label story.
• Ecosystem alignment (build vs. buy): The behaviour is conditional on statamic-brand-context ≥ 1.16. Adopting both together gives a coherent "Addon-Suite" settings page; adopting this alone still works because older brand-context versions simply ignore the method. That graceful degradation is the strongest signal in this release.
• Version risk budgeting: The package is still 0.x and iterating on CP integration details. Treat it as an early-stage dependency: pin versions, keep an upgrade test for the CP settings screens, and avoid building bespoke admin workflows directly on its nav structure.
• Roadmap input: Releases like this suggest the maintainers are investing in suite-level cohesion (shared settings surfaces, branding context) rather than standalone features. If suite cohesion is on your roadmap, this is a compatible building block; if you need standalone depth, it isn't.

When to Consider This Package

Consider it when:

• You are already on Statamic (this is a Statamic addon inside the Laravel ecosystem, not a general-purpose Laravel package) and want settings surfaced inside the Control Panel.
• You run multiple brands, sites, or client installs where consistent CP navigation and white-labeling matter, and you either already use statamic-brand-context ≥ 1.16 or plan to.
• You are assembling an addon suite and want a single "Addon-Suite" settings page rather than N scattered settings entries.
• You need a low-ceremony upgrade: no migrations or config changes means low operational cost to trial.

Look elsewhere when:

• You need a vanilla Laravel package — the value here is Statamic CP surface area, and it is inert outside that context.
• You require semantic-versioning stability (1.x+ API guarantees); 0.x iteration on navigation and settings behaviour is expected to continue.
• Your admin UX requirements go beyond nav placement — this release changes where settings appear, not what they can do.
• You are on an older brand-context and unwilling to upgrade: the method is ignored, so you gain nothing from this version specifically.

How to Pitch It (Stakeholders)

To executives: A small, low-risk maintenance release for our Statamic addon. It makes the addon's settings easier for administrators to find in the control panel and keeps our admin experience consistent with the wider addon suite — the kind of polish that matters at client handoff and in demos. No database migration, no configuration changes, no downtime; upgrade cost is effectively zero.

To engineering: v0.2.1 declares settingsNavParent() returning the addon's own CP navigation entry. With statamic-brand-context ≥ 1.16, settings render as "Einstellungen" beneath that entry; without our own nav, addons consolidate under a shared "Addon-Suite" page. On older brand-context the method is ignored and the previous layout is retained — a safe soft dependency, not a hard requirement. No migration, no new config keys. Recommended action: bump the pin, smoke-test the CP settings screen on one staging install, and confirm which brand-context version each client environment is on so expectations about the new sub-item match reality. Note the package remains 0.x — keep it pinned and re-check nav behaviour on minor releases.