Run content governance as a repeatable operating system
Playbooks turn Contentrain adoption into repeatable workflows for AI agents, developers, editors, migrations, and Studio operations.
AI agent playbook
Govern AI agents that create and edit product content
A practical operating model for giving AI coding agents content authority without giving them uncontrolled repository access.
Editor playbook
Give content editors Studio workflows without losing Git control
A workflow for letting editors, reviewers, and marketers change structured content while engineering keeps schemas, diffs, validation, and release discipline.
Developer playbook
Implement Git-native content in a modern app
A developer-first path for adding models, content, validation, generated SDK access, and local agent workflows to a Nuxt, Next, Astro, SvelteKit, Vite, or Node project.
Migration playbook
Migrate hardcoded strings into governed content
A migration path for extracting AI-generated UI copy, labels, empty states, and page text from source files into structured Contentrain content.
Studio playbook
Adopt Studio when content work becomes a team operation
A commercial and operational adoption path from local open-source packages to Studio SaaS, managed delivery, and enterprise licensing.
Operating paths
Choose the workflow before choosing the interface
Each playbook turns a common adoption moment into a concrete operating path. Teams can start with local packages, move through Normalize, add content editor workflows, and adopt Studio when collaboration and delivery become valuable.
- Developer-first implementation path
- AI agent governance and validation path
- Studio adoption path for teams
Ecosystem bridge
Bridge open-source adoption into Studio revenue
The playbooks are useful because they connect the MIT packages with the AGPL Studio app. MCP, CLI, SDK, rules, and skills create the adoption channel; Studio turns that channel into collaboration, review, media, delivery, and enterprise control.
- Package workflows remain local and reviewable
- Studio adds seats, permissions, CDN, forms, and APIs
- The content contract stays in Git
Repeatability
Make content governance repeatable across teams
Content governance fails when every team invents its own process. Playbooks make implementation, migration, editor review, and Studio rollout visible enough for developers, AI agents, and content teams to repeat safely.
- Checklist-driven implementation
- Branch and validation expectations
- Clear next pages for each audience
Common questions
Which playbook should we start with?
Start with the developer implementation playbook when a team is installing Contentrain for the first time. Use Normalize migration when the codebase already has hardcoded copy.
Do playbooks cover both packages and Studio?
Yes. The playbooks are written for the full ecosystem: MCP tools and local packages first, then Studio when review, roles, delivery, and team operations are needed.
Why are playbooks important for AI teams?
They give AI agents and humans the same operating model: context, models, validation, branch review, checklists, and next steps instead of ad hoc content edits.
Next paths
Continue through the content system
Start local. Scale to Studio.
Build a governed content layer before content becomes product debt.
Developers can start with the MIT packages. Teams can move into Studio when review, roles, delivery, and licensing matter.