- How do I install Statamic Certificates?
- Install it with Composer using composer require goldnead/statamic-certificates, then publish the addon configuration as described in the README. From v0.1.6 the package also requires statamic-courses ^0.6, so Composer must be able to resolve that version alongside your other dependencies. No migrations or extra cache-clearing steps are introduced beyond a normal autoload refresh. If you run multiple environments, install in CI first so any constraint conflict surfaces early.
- Which Laravel and Statamic versions does this addon support?
- It is a Statamic control panel addon shipped as a Laravel/PHP Composer package, so the Statamic and Laravel versions you can use come from the constraints in its composer.json rather than from a separate support matrix. From v0.1.6 it also hard-requires statamic-courses ^0.6. Separately, statamic-brand-context acts as a soft feature gate: at 1.16 or above the addon settings render as a sub-item labelled Einstellungen beneath its own CP nav entry, and below 1.16 that method is ignored and the previous layout persists. Check composer.json before assuming support on an older Statamic release.
- How does PDF certificate generation work?
- Certificate layouts are defined as blueprint-driven templates, and the addon generates the PDF from that template while merging dynamic recipient and course data at issue time. Everything is driven from the Statamic control panel, so you define the layout once and reuse it across many issued certificates. Because the output is a PDF, the addon handles the rendering step rather than requiring a separate PDF service. Check the README and package source for the exact rendering engine if fonts or page size customisation matter to you.
- How do unique verification codes and public certificate validation work?
- Every issued certificate carries a unique verification code, and the addon exposes a simple public route where a recipient or third party can validate that code. Validation does not require control panel access, which makes it usable on a public-facing site. That gives you an authenticity check you can link to from the certificate itself or from a confirmation email. The overview describes this as a public endpoint for validation rather than a full API.
- Can I define my own certificate layout or template?
- Yes. Templates are blueprint-driven, which means the certificate layout is defined declaratively and can be reused across as many issued certificates as you need. You define the template once, then assign it to the relevant entries or users. That keeps a course, event or training programme certificate design consistent across recipients. Because it is blueprint-based, the fields you expose on the template are the fields populated at issue time.
- What use cases is this addon built for?
- It is aimed at courses, events and training programmes where you need to hand out proof of completion. You define a certificate template, assign it to the relevant entries or users, and issue certificates with unique verification codes. Recipients can then validate authenticity through the public route. It is a control panel workflow, so issuing is an editor-driven action rather than a public self-service form.
- How do I display certificate data in my Antlers templates?
- The package ships Antlers tags for rendering certificate data on the frontend. Use them when you want to show a recipient certificate, its verification code, or a link to the public validation route in your Statamic templates. The tags read the data the addon stores, so you do not need to query the database directly. Check the README for the exact tag names and available parameters before wiring them into production templates.
- How do control panel permissions work for managing certificates?
- The addon registers its own control panel navigation entry and integrates with Statamic permissions, so you can control which roles can view templates, issue certificates or change settings. That matters when issuance is an administrative action rather than something every editor should be able to do. Because it appears as its own CP nav entry, it can be permissioned independently of other addons. Review the permission names in the package before mapping them to your existing role setup.
- Why does composer update fail with a statamic-courses constraint conflict?
- Version 0.1.6 adds statamic-courses ^0.6 to the Composer constraints, so any other package in the host that requires statamic-courses below 0.6 will make installation fail at dependency resolution. The failure is loud rather than silent, which is preferable, but it usually appears in CI rather than on a developer machine. The quickest fix is to align the statamic-courses version across the packages in your suite or to hold this addon at an earlier release. It is also worth confirming whether ^0.6 widened or tightened the previous constraint, since a tightening can be breaking for hosts already on 0.5.
- Is Statamic Certificates safe to run in production and how actively is it maintained?
- Technically the risk is low: the recent releases are Composer-level changes with no migrations, no new config keys and no data-shape changes. The risk profile has shifted from presentational to dependency-graph, because installability now depends on two third-party packages rather than one. Three tags, 0.1.4, 0.1.5 and 0.1.6, landed in a short window, and 0.1.5 is not documented in the release notes reviewed, so confirm it carried nothing material before treating 0.1.6 as the cumulative state. Pin the version in production and read the changelog before each upgrade.