Growth & Digital/Content & Copy
EDIT VIA GITHUB · /content

Content & Copy

Where every word on the site lives, who signs it off, and what's still pending. One copy source feeds ~103 pages — change it once, every page updates.

Program brief →
COPY SOURCE
1 module
nav, spine, products, proof, CTAs
SURFACES
103 pages
PENDING REVIEW
5 families
PMM · comms · engineering gates
NAMING GATE
open
answer engines repeat what we publish
VOICE RULESsentence caseverb-first CTAsno em dashesno exclamation points"fast" not "quick"abbreviate apps/devs/docsTT Trailers all-caps H1s

How copy works on the new site

One shared content module carries the copy the whole site reuses — nav, chapter spine, product one-liners, use cases, proof points, CTAs — and the templates consume it, so a copy change lands everywhere at once instead of page by page. During the design phase, edits happen in the design project's content module; post-launch, copy lives in Sanity and the content module, maintained by the Content Manager and Digital Media & Content Specialist lines, with the AI content workflow drafting against it.

Every family below answers the provenance question directly: where the words came from, who approves them, and what state they're in.

The copy registry

Nav & chapter spineEvery page — header, footer, mega menusBrand + PMMLocked
Product one-liners (7 products)Product pages · homepage · menusPMMNaming gate
Capability primer copy (9)Build chapterPMM + content leadsDrafting
Solutions snippets (42)The 14 solutions pagesEngineeringValidation pending
Proof points & figuresMetric strips on every templatePMM + DataIllustrative — pending review
Customer outcome linesCustomers page · proof bandsBrandMigration pending
Offer copy (4 offers)Chapter 05 offer pagesPMM — Decision 03Gated
Blog launch seedsCorporate · engineering · AI postsCommsPlaceholders pending
Glossary term copyEvery term pageSEO/AEO + content leadsIn program — keep/fix/retire
CTAsVerb-first, every CTA routes to Get StartedBrandLocked

What's still placeholder in the design

The design ships with flagged placeholder copy so structure could move faster than approvals: bracketed names and partner lines in blog seeds ("pending comms review"), illustrative figures on metric strips, and customer outcome lines awaiting migration from the current site. None of it publishes without clearing its gate above. [owner to complete]

How copy works on the new site

One shared content module carries the copy the whole site reuses — nav, chapter spine, product one-liners, use cases, proof points, CTAs — and the templates consume it, so a copy change lands everywhere at once instead of page by page. During the design phase, edits happen in the design project's content module; post-launch, copy lives in Sanity and the content module, maintained by the Content Manager and Digital Media & Content Specialist lines, with the AI content workflow drafting against it.

Every family below answers the provenance question directly: where the words came from, who approves them, and what state they're in.

The copy registry

Nav & chapter spineEvery page — header, footer, mega menusBrand + PMMLocked
Product one-liners (7 products)Product pages · homepage · menusPMMNaming gate
Capability primer copy (9)Build chapterPMM + content leadsDrafting
Solutions snippets (42)The 14 solutions pagesEngineeringValidation pending
Proof points & figuresMetric strips on every templatePMM + DataIllustrative — pending review
Customer outcome linesCustomers page · proof bandsBrandMigration pending
Offer copy (4 offers)Chapter 05 offer pagesPMM — Decision 03Gated
Blog launch seedsCorporate · engineering · AI postsCommsPlaceholders pending
Glossary term copyEvery term pageSEO/AEO + content leadsIn program — keep/fix/retire
CTAsVerb-first, every CTA routes to Get StartedBrandLocked

What's still placeholder in the design

The design ships with flagged placeholder copy so structure could move faster than approvals: bracketed names and partner lines in blog seeds ("pending comms review"), illustrative figures on metric strips, and customer outcome lines awaiting migration from the current site. None of it publishes without clearing its gate above.

Statuses are set by hand — flip a badge here (`content/pages/copy.md`) as gates clear. The Content Creation agent's approval queue maps to these families; the review pipeline is Phase 04's brief-to-production workflow with brand review built in.