Let non-developers change content without losing Git control
Editors, marketers, translators, and reviewers can work through Studio while developers keep branches, diffs, validation, and source-of-truth control.
Problem
Content teams need access without breaking the Git workflow
Non-developers should be able to change structured content, but product teams still need schemas, validation, diffs, and approval. Studio sits between those needs.
- Content editing without direct repository work
- Schema-aware fields for different model kinds
- Git-backed review before production
Editing
Structured views match the content type
Studio includes collection, document, dictionary, singleton, vocabulary, and content panel surfaces. Editors do not need to know the file layout to work within the model.
- Collection and document editing
- Dictionary and singleton workflows
- Vocabulary visibility for consistent language
Approval
Reviewers see the change, not just the final page
Branch detail, diff, branch health, moderation, and review flows make content approval concrete. Teams can reject, merge, or continue work with the content state still represented in Git.
- Branch detail view
- Diff and health checks
- Reviewer-oriented workflow
Operations
Media and delivery belong in the same workspace
Real content teams manage images, forms, submissions, webhooks, and delivery rules alongside text. Studio includes those surfaces so content operations do not fragment across tools.
- Asset manager and image picker
- Form configuration and submissions
- CDN and webhook panels
AI assist
AI assists inside controlled boundaries
The chat panel can help content teams change structured content, but the server builds permission and project context before tools are available. That keeps AI assistance attached to governance.
- Project-aware chat context
- Permission-filtered tools
- Streaming tool results for content operations
Common questions
Can non-developers use Contentrain?
Yes, through Studio. The local packages are developer-first, while Studio provides the editor and reviewer experience for content teams.
Does Studio remove engineering review?
No. It gives content teams a usable interface while preserving branch, diff, validation, and merge workflows for controlled release.
What content types can Studio manage?
The app has surfaces for collections, documents, dictionaries, singletons, vocabulary, media, forms, and delivery configuration.
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.