Rules Claude reads
CLAUDE.md lists the blocks, the SEO rules and what Claude must never touch. Helpful, but only guidance.
Every page on this site is built from one approved block library. The CMS and Claude Code edit the same files, and the build stops anything outside the library.
See an example pagePick blocks, fill in the fields. Or ask Claude to write the page. Both save to the same YAML file in Git.
Every change has an author, a diff and an undo. One source of truth, no second database.
The schema rejects unknown blocks and extra fields. A check script stops HTML in content and broken redirects.
Content goes straight to production. New features go to staging first and pass a human review.
CLAUDE.md lists the blocks, the SEO rules and what Claude must never touch. Helpful, but only guidance.
Claude Code settings deny edits to components, layouts and config. Marketing seats can only change content.
Content collections with a strict schema. If a page uses anything outside the library, nothing deploys.
Astro sends plain HTML with almost no JavaScript, so pages load fast on any device.
Organization and WebPage schema by default, FAQ schema when a page has an FAQ block.
Old WordPress URLs map to new pages with 301 redirects, checked automatically for chains and dead targets.
Ask for a new block. An engineer or a reviewed Claude session builds it on a feature branch, it goes to staging, and once approved it appears in the CMS for everyone.
No. It cannot edit the components or styles, and the build rejects pages that do not match the block schema.
No. The CMS handles commits for you. Claude Code users see a normal chat; Git runs underneath.
The designer delivers named blocks with fields, variants and mobile versions, plus colour and spacing tokens. Each block becomes one component and one CMS option.
Ask Claude Code for a custom pricing layout, or paste HTML into a field. The guardrails should stop both.
Back to the home page