- What is el-schneider/statamic-admin-bar?
- It is a Composer package for Statamic sites that adds a front-end admin bar for logged-in editors. The bar lets editors edit the current page, open the control panel, and navigate quickly without leaving the page they are working on. It is a pre-1.0 addon, currently at v0.3.2, so conventions may still change.
- How do I install statamic-admin-bar in a Laravel or Statamic app?
- Install the package via Composer, then publish its assets and clear Laravel caches. The package ships frontend assets and expects its font assets to resolve from a published addon path. After publishing, verify the admin bar font request and run a quick smoke test in staging before promoting to production.
- Does statamic-admin-bar support Laravel 10 or Laravel 11?
- The provided release notes do not state explicit Laravel or PHP version constraints. Check the package's composer.json for the supported Laravel and PHP ranges, then test against your application's exact version. Because the package is pre-1.0, confirm compatibility before a production rollout.
- Do I need to run npm build to use statamic-admin-bar?
- The package uses npm-driven asset builds and publishable assets, but the notes do not confirm whether production assets are shipped prebuilt. Teams should verify whether asset publishing alone is enough or whether a local npm build is required. Validate this in staging and follow the package's publishing instructions.
- Why is the admin bar font returning a 404 after installation?
- v0.3.2 fixes font assets resolving from the host app's /build/assets path instead of the published addon path. If you see 404s, republish the package assets, clear Laravel caches, and confirm the font URL points to the addon path. Also check web server and CDN caching for stale asset responses.
- Is v0.3.2 a breaking change from earlier 0.3.x releases?
- The release notes call out no breaking changes or deprecations; v0.3.2 is a patch focused on asset-path resolution. Treat it as a low-risk patch upgrade from earlier 0.3.x versions. Still run smoke tests because the package is pre-1.0 and asset conventions may evolve.
- What are the production deployment steps for statamic-admin-bar?
- Pin v0.3.2, update Composer dependencies, publish the package assets, and clear config and view caches. Rebuild frontend assets only if your deployment model requires it. Verify the admin bar font loads from the addon path and monitor for asset 404s after deployment.
- Does statamic-admin-bar have automated tests for asset URL resolution?
- The provided assessment does not confirm automated test coverage for asset URL resolution and lists it as a key question to verify. Review the repository's test suite and CI configuration before relying on the package in production. If coverage is missing, add your own smoke checks for the admin bar assets.
- Is statamic-admin-bar safe to use in production?
- Technical risk is low-to-moderate: it is a pre-1.0 package with a narrow asset fix in v0.3.2. Approve it for staging or pilot validation now, and defer broad rollout until version support, asset build expectations, and test coverage are confirmed. Monitor for font and asset 404s after deployment.
- How is statamic-admin-bar maintained and what about dependency updates?
- The project uses Dependabot for npm, Composer, and GitHub Actions plus an npm release-age guardrail, which is a positive maintenance signal. Dependency updates can still introduce build-time risk, so validate them in staging. Release cadence and security policy are not specified in the provided notes; check the repository for details.