Weave Code
Statamic Site Essentials Laravel Package
stillat/statamic-site-essentials
A Statamic addon that bundles the essentials every site needs, including SEO and meta tags, sitemaps, redirects, and other common configuration helpers, so you can skip repetitive setup and keep your control panel tidy.
A collection of features to rapidly build and deploy @statamic sites.
Frequently asked questions about Statamic Site Essentials
- What features does stillat/statamic-site-essentials include?
- The addon is described as a bundle of the essentials most Statamic sites need: SEO and meta tags, sitemaps, redirects, and other common configuration helpers, all intended to keep the control panel tidy. It is aimed at skipping repetitive setup on every new build. No README or changelog was available during evaluation, so confirm the exact feature list and any control-panel surfaces against the repository before you commit to it.
- How do I install stillat/statamic-site-essentials?
- Install it with Composer from the root of your Statamic project by running composer require stillat/statamic-site-essentials. Statamic addons are normally discovered automatically through the addon manifest and service provider, so manual registration is usually unnecessary. The v1.4.0 release note does not state whether the registration path changed, so verify the provider, config, and any publishable assets after installing.
- Which Statamic versions does this addon support?
- Version 1.4.0 declares a requirement of Statamic ^5.73 or ^6.4 and removes support for the 4.x line entirely. The constraint is disjunctive with no overlap, so any given application resolves to exactly one branch. Because the addon inherits Statamic's own Laravel and PHP floors, check those for your target branch before upgrading.
- Does this addon still work on Statamic 4?
- Not on version 1.4.0, which drops the 4.x line and requires Statamic 5.73+ or 6.4+. If you must stay on Statamic 4, tighten your composer.json constraint to 1.3.* or <1.4 so the intent is explicit rather than an accident of the lockfile. Whether the 1.3.x line remains maintained, and for how long, is not documented in the release note and should be confirmed with the maintainer.
- Why did my composer update fail after version 1.4.0 was released?
- Dropping support for a dependency major is a breaking change for consumers, but it shipped in a minor release, so projects holding a caret constraint such as ^1.0 or ^1.3 get pulled toward 1.4.0 on the next composer update. Composer should fail dependency resolution outright rather than half-install, which is a loud failure, but it blocks unrelated dependency updates in that repository until someone intervenes. The fix is either a Statamic upgrade or an explicit constraint pin, not repeated update attempts.
- What Laravel and PHP versions do I need for this addon?
- The addon does not publish its own independent floors so much as inherit Statamic's, and Statamic 5.73+ and 6.4+ each correspond to different Laravel and PHP minimums. Check the composer.json of the resolved branch plus Statamic's own requirements before committing a target. A published compatibility matrix of addon version by Statamic, Laravel, and PHP is not documented in the release note, so ask the maintainer or record your own.
- Is version 1.4.0 a breaking change even though it is a minor release?
- Yes in practice. Removing support for a dependency major breaks consumers on that major, and shipping it as 1.4.0 rather than 2.0.0 means caret constraints will pull affected projects forward automatically. The release note documents no deprecation window, and it is unclear whether a notice was published earlier. Ask the maintainer why it was released as a minor and whether the driver was Statamic 4 end-of-life or new Statamic API dependencies.
- How should I sequence the upgrade to statamic-site-essentials 1.4.0?
- Start with an inventory: record the installed Statamic version, the installed addon version, and the declared constraint for every application using the addon, since that single data point determines the branch. Then upgrade Statamic as an isolated change with its own test pass, bump the addon afterwards, and do one regression pass over the control panel and content rendering before deploying. Do not combine the Statamic upgrade and the addon bump in a single change.
- What should I test after upgrading this Statamic addon?
- Statamic 5 and 6 are separate majors and cannot be co-resident, so there is no dual-running scenario to design for and a single regression pass on the target branch is enough. Focus on the control-panel surfaces the addon touches, plus rendered pages where meta tags, sitemap output, and redirects are emitted. Confirm redirects still resolve with the expected status codes and that sitemap URLs reflect the production domain.
- Do I need to publish config or run migrations after installing this addon?
- Statamic addons sometimes ship publishable config, fieldsets, or migrations, but the v1.4.0 release note does not describe the registration or publish path. Inspect the package service provider and any config files after installing, and follow the repository README for the current release. Run this in staging first, since a missing publish step is usually only visible in the control panel.
Weaver
How can I help you explore Laravel packages today?