Weave Code
Statamic Peak Browser Appearance Laravel Package
studio1902/statamic-peak-browser-appearance
A Statamic Peak addon that lets you customize browser appearance settings, like theme colors and favicons, so your site looks polished in tabs and on mobile devices. Simple to configure and built to fit seamlessly into the Peak workflow.
Belongs to the Statamic Peak Starter Kit and contains all Browser Appearance related fieldsets and partials.
Frequently asked questions about Statamic Peak Browser Appearance
- What does studio1902/statamic-peak-browser-appearance actually do?
- It is a Statamic Peak addon that bundles browser appearance fieldsets and partials. It helps you manage theme colors, favicons, and related settings so your site looks polished in browser tabs and on mobile devices. It is designed to fit into the Peak starter kit workflow rather than serve as a general-purpose Laravel package.
- How do I install statamic-peak-browser-appearance with Composer?
- Install it as a Composer dependency in your Laravel application using studio1902/statamic-peak-browser-appearance. The assessment indicates normal Laravel package discovery and service-provider registration, with no database migrations or external services indicated in the release notes. After installation, follow the package README to add its fieldsets and partials to your Peak setup and clear caches.
- Do I need the Statamic Peak Starter Kit to use this package?
- The package belongs to the Statamic Peak Starter Kit and contains browser appearance fieldsets and partials built for the Peak workflow. It is therefore best suited to projects already using Peak conventions. You can review the repository to see whether the fieldsets and partials can be adapted to a non-Peak Statamic project.
- Which Laravel and Statamic versions are supported?
- The v4.0.0 release notes indicate Statamic v6 support, which signals alignment with the current CMS major line. The provided context does not include the exact PHP, Laravel, and Statamic version matrix, so check the package composer.json and README before adoption. Do not assume v4 works on older Statamic v5 stacks without explicit confirmation.
- How do I configure theme colors and favicons with this addon?
- Configuration is handled through the package's browser appearance fieldsets and partials within the Peak workflow. You provide favicon assets and theme color values through Statamic global variables or the fields exposed by the addon, then render the partials in your layout head. Validate the rendered markup in a staging environment before relying on it in production.
- What fieldsets and partials does the package provide?
- The package contains browser appearance related fieldsets and partials for the Statamic Peak Starter Kit. The exact file names and available fields should be checked in the repository README and source, because the provided overview does not list them individually. These assets are intended to be included in your Peak templates and global variable setup.
- Is this package compatible with Statamic v5?
- Statamic v5 compatibility is not confirmed in the provided context, and v4.0.0 is a major version release that targets Statamic v6. Treat the upgrade as potentially breaking and confirm support in the release notes or composer constraints. If you are still on Statamic v5, sequence the Statamic v6 upgrade before or alongside the package upgrade.
- How does the GlobalVariablesSaved event affect my site?
- The assessment says the package reacts to Statamic global-variable lifecycle events, specifically GlobalVariablesSaved, to reduce the need for custom hooks. This makes it an event-driven integration point, but event timing and payload assumptions can change across major versions. Test whether the listener is idempotent and safe when global variables are saved multiple times.
- How should I test browser appearance changes before production?
- Use a staging or local environment and exercise create, update, and save flows for global variables multiple times. Check browser tab icons, theme colors, and mobile appearance after each save, and run your application test suite. Also monitor logs for listener exceptions or stale cached global variables that could affect save workflows.
- What should I check before upgrading to v4 in production?
- Treat v4 as a major upgrade: review the changelog or upgrade guide, update Composer constraints, and run application tests in staging. Validate global-variable save flows and watch for backward incompatibility with Statamic v5, duplicate event handling, or missed event handling. Statamic v6 support is a positive maintenance signal, but the assessment is provisional based only on v4.0.0 release notes, so verify issue backlog, test coverage, and release cadence before deploying.
Weaver
How can I help you explore Laravel packages today?