- How do I install goldnead/statamic-inbox in a Laravel Statamic project?
- Install it as a Composer package in your Laravel-based Statamic application. Because it is a Statamic addon, it exposes its inbox and settings screens inside the Control Panel rather than as a standalone headless module. Check the repository README for any addon registration, publishing, or configuration steps specific to your Statamic version.
- What changed in goldnead/statamic-inbox v0.2.4?
- v0.2.4 changes Control Panel information architecture, not inbox data. The addon now declares settingsNavParent returning a section and name for its own CP navigation entry, so its settings screen renders as a sub-item under that entry instead of the shared Addon-Suite page. The release does not touch ConversationQuery, the inbox:summary command, fetch handling, or snooze logic.
- Does goldnead/statamic-inbox require statamic-brand-context 1.16 or newer?
- The new v0.2.4 settings layout requires statamic-brand-context 1.16 or newer according to the release notes. Older brand-context versions ignore the navigation method and keep the previous layout, which is graceful degradation. Confirm in the package constraints whether this is a hard Composer requirement or a soft check before upgrading a fleet.
- Will upgrading goldnead/statamic-inbox to v0.2.4 break my inbox data?
- No migration, config key, or breaking data change is described for v0.2.4. The release is a code-level Composer bump focused on settings navigation and leaves the inbox domain untouched. Still confirm the tag belongs to the inbox/helpdesk package you assessed before merging.
- Why does my Statamic settings menu show Einstellungen for this addon?
- The v0.2.4 notes show the settings sub-item label as Einstellungen, which is German. The notes do not confirm whether the addon ships translations or whether an English Control Panel will show a mixed-language settings tree. Check the lang files and whether you need to publish translations or accept the default.
- Does goldnead/statamic-inbox have its own Control Panel navigation entry?
- Yes, v0.2.4 declares settingsNavParent for its own CP navigation entry, so its settings screen nests under that entry. Addons without their own navigation share a single Addon-Suite page under Settings. On your installs, determine whether this addon already had its own nav entry, because that decides whether the v0.2.4 change is a visible move or a no-op.
- Is goldnead/statamic-inbox a headless Laravel package or a Statamic addon?
- It is a Statamic addon, which means it is also a Laravel package but not purely a headless domain module with only an Artisan surface. It owns Control Panel navigation and a settings screen in addition to its inbox functionality. That CP surface matters for access control, screenshots, and user training.
- What happens if different sites run different statamic-brand-context versions with this addon?
- The same goldnead/statamic-inbox version can produce different settings layouts depending on whether statamic-brand-context is 1.15 or 1.16. That creates a support-matrix problem and can make runbook screenshots wrong on part of the fleet. Align brand-context versions across sites before rolling out v0.2.4.
- Does the navigation counter affect the goldnead/statamic-inbox settings sub-item?
- The release notes say the settings sub-item carries the same name as the navigation entry, including when the entry shows a counter. That means the settings label inherits whatever that label evaluates to. It is mostly harmless, but check for sidebar truncation or layout shift if the counter-bearing label is long.
- Where is the repository and how do I verify the v0.2.4 tag?
- The repository is https://github.com/goldnead/statamic-inbox. The assessment flags provenance risk because v0.2.4 notes discuss Statamic settings navigation and statamic-brand-context but not inbox, mailboxes, or the summary command. Confirm the tag belongs to this addon rather than a sibling Statamic addon before merging.