- How do I install goldnead/statamic-consent in a Statamic site?
- Install it like a typical Statamic addon using Composer: run composer require goldnead/statamic-consent and follow the addon's setup steps. You will usually publish the configuration, views, and translations, then add the consent banner to your layout. Check the repository README for exact commands and any required Statamic version.
- Does this package work with Laravel, and which Laravel and Statamic versions are supported?
- Because Statamic runs on Laravel, the addon is used within a Laravel application, but it is specifically a Statamic addon rather than a general Laravel package. Supported Statamic and Laravel versions depend on the package's Composer constraints, so check those before installing. If you are on an older Statamic release, verify compatibility first.
- How do I configure consent categories and the cookie consent banner?
- Consent categories and banner content are configurable, so you can define the cookie or script groups your site needs. The banner is rendered on the front end and lets visitors make choices per category. Publish the configuration and views if you need to adjust labels, layout, or behavior beyond the defaults.
- How does script gating work before consent is given?
- Script gating prevents tracking or embedded content from loading until the visitor has opted in to the relevant category. You mark or wrap scripts according to the addon's documented approach, and the addon checks stored consent before allowing them to run. This helps keep analytics, marketing, or third-party embeds from firing before consent.
- Where are consent decisions stored, and can visitors update preferences later?
- The addon stores consent decisions and lets visitors revisit and update their preferences later. That supports the common GDPR expectation that consent can be withdrawn or changed. Check the package configuration for where records are stored and how long they are retained.
- How do I publish and customize the views and translations?
- Views and translations are publishable, which means you can override the default banner markup and wording in your own project. Publish them through the addon's documented publish command and edit the copies rather than the vendor files. This keeps customizations upgrade-safe.
- Can I use this addon with Statamic Antlers templates?
- Yes, the addon is designed to work with Statamic's Antlers templating. You can include the consent banner or related consent checks in your Antlers layouts and templates. Consult the README for the exact Antlers tags or partials to use.
- How should I test cookie consent behavior before going live?
- Test in a local or staging environment by loading the site with a clean browser profile and checking the banner, category toggles, script blocking, and preference updates. Verify that scripts stay blocked before consent and load only after the correct category is accepted. Also test rejecting consent and changing preferences later.
- What should I check before using this in production for GDPR?
- Confirm that your categories match the cookies and scripts you actually use, and link to a privacy policy that explains them. Make sure consent is stored and that visitors can withdraw or change it. Review your legal requirements with a qualified professional, because a package alone does not guarantee GDPR compliance.
- What alternatives exist to goldnead/statamic-consent for Statamic cookie consent?
- Alternatives include other Statamic consent addons, general Laravel cookie consent packages, or a custom Antlers and JavaScript solution. Compare them on script gating, preference storage, translation support, and maintenance activity. If you need deep Statamic integration, an addon like this is usually simpler than building from scratch.