Make your site safely editable by an AI content agent. Guardrails, validation, and a reviewed publish flow: bulk content work that can’t break the site.

1.2.1

September 25th, 2026

Changed

  • Shorter README. The pitch, the safety story, getting started and a short developer section. The full design walkthrough moved to docs/how-it-works.md.
  • Clearer about what the kit asks of your site. It needs a replicator page builder, because that's what keeps the agent safe: it composes pages from your blocks and fills in their fields, so it never writes markup and every edit can be validated. Everything else (blocks, templates, CSS, front-end tooling) is up to you.
  • Blade is documented. Block partials can be .antlers.html or .blade.php. The README shows the Blade page-builder loop.

Fixed

  • When a block template is missing, content:validate now says it expects .antlers.html or .blade.php. Blade partials were already accepted, but the message only mentioned Antlers.

1.2.0

September 25th, 2026

Cheaper CI for Control Panel saves

With Statamic's git automation on, every Control Panel save is its own commit and push, and each one ran the full validate-and-test job (~4 billed minutes). On an active site that used up GitHub's free 2,000 Actions minutes in a few weeks.

  • The kit now ships config/statamic/git.php, which prefixes git automation commits with [BOT].
  • validate-and-test skips [BOT] pushes to staging. The next agent or developer push validates all content again.
  • path-allowlist still runs on every push. It's cheap, and a commit-message skip would let any commit bypass the allowlist.

Fewer false failures on staging

A single CP action can land as several commits seconds apart (an asset delete, then the reference cleanup), and an in-between commit can fail validation on its own. If staging has already moved on to a newer head, that run now passes with a warning. It still fails when the newer head is a [BOT] commit, since that one never gets validated.

Clearer errors for broken YAML

content:validate parses every content file first and reports YAML errors (duplicate keys and so on) per file, for example content/collections/pages/about.md: Duplicate key "title". Before, one broken file crashed the whole Stache load with an error that didn't name the file.

Upgrading an existing site

  • Copy config/statamic/git.php (or just add [BOT] to the commit -m command in yours).
  • Copy .github/workflows/content-guardrails.yml, keeping your filled-in MAINTAINER_EMAILS and MAINTAINERS.
  • Copy app/Console/Commands/ValidateContent.php.

1.1.0

July 22nd, 2026

Automated editor onboarding

Hand-over no longer means driving the editor's computer yourself. Two prerequisites (the client's GitHub account added as collaborator, Claude Code signed in on their own account), then you email one prompt from the new ONBOARDING.md — and the editor's own agent installs gh, walks them through the GitHub sign-in, clones the repo, sets a git identity that stays off the maintainer list, and verifies push access.

  • agentic:setup gains --repo-url and stamps ONBOARDING.md (repo URL + maintainer emails; empty keeps current).
  • Interactive agentic:setup re-runs are now safe: every prompt defaults to the currently stamped value.
  • Guardrail allowlist adds uuidgen and git pull --rebase (both prescribed by the agent brief; previously triggered permission prompts).

Docs restructure

  • SETUP.md: git init -b main; private/public decision up front (branch protection on free plans needs a public repo); CI PHP-pin note; preview + repo URL stamped in a step-4 re-run; a new step 5 — build the site — covering the staging PR flow, merge commits (not squash), and the catalog obligation; step 6 rewritten around the emailed prompt with per-tier commands; an explicit "this file is for the developer" header.
  • AGENTS.md: stache:refresh rationale corrected — it's for local checks; the preview site refreshes on push.
  • README: synced with the new setup structure and deduplicated.

1.0.0

July 21st, 2026

First release. A Statamic starter kit that makes a site safely editable by an AI content agent: guarded local editing (PreToolUse hook + command allow-rules), blueprint validation for flat-file content, an auto-generated block catalogue, and default-deny CI that keeps non-maintainer commits content-only and production behind a reviewed PR. MIT.