cms-architecture
Design content management systems — content models, editorial workflows, publishing pipelines, localization — with schema evolution and multi-channel delivery.
Goals
- Define content models that are reusable across channels
- Plan editorial workflows with roles and approval states
- Design multi-language and multi-site architecture
- Ensure content portability and schema versioning
Contract
Input
A content platform to design: content types, publishing channels, team structure.
Output
A CMS architecture with:
- Content model (entities, relationships, metadata)
- Editorial workflow (states, roles, transitions)
- Localization strategy
- API design for content delivery
Content Model Patterns
| Pattern |
Use case |
Example |
| Page |
Static, hierarchical |
Marketing sites |
| Article |
Time-based, rich media |
Blogs, news |
| Product |
Structured, transactional |
E-commerce |
| Component |
Reusable, composable |
Design systems |
| Taxononomy |
Classification |
Categories, tags |
Steps
- Audit content — existing content types, volume, reuse patterns
- Define content model — entities, fields, relationships
- Design workflow — draft → review → approved → published
- Plan localization — language variants, fallback, RTL
- Choose CMS architecture — headless (API), coupled, hybrid
- Design delivery API — query, filter, personalize
- Plan migration — content mapping, transformation scripts
References
../backend/backend-architecture/SKILL.md — API design../../frontend/frontend-design/SKILL.md — content rendering../../data/data-etl-pipeline/SKILL.md — content migration
1---2name: cms-architecture3description: Design content management systems — content models, editorial workflows, publishing pipelines, localization — with schema evolution and multi-channel delivery.4---56# cms-architecture78Design content management systems — content models, editorial workflows, publishing pipelines, localization — with schema evolution and multi-channel delivery.910## Goals11- Define content models that are reusable across channels12- Plan editorial workflows with roles and approval states13- Design multi-language and multi-site architecture14- Ensure content portability and schema versioning1516## Contract1718### Input19A content platform to design: content types, publishing channels, team structure.2021### Output22A CMS architecture with:23- Content model (entities, relationships, metadata)24- Editorial workflow (states, roles, transitions)25- Localization strategy26- API design for content delivery2728## Content Model Patterns2930| Pattern | Use case | Example |31|---|---|---|32| Page | Static, hierarchical | Marketing sites |33| Article | Time-based, rich media | Blogs, news |34| Product | Structured, transactional | E-commerce |35| Component | Reusable, composable | Design systems |36| Taxononomy | Classification | Categories, tags |3738## Steps39401. **Audit content** — existing content types, volume, reuse patterns412. **Define content model** — entities, fields, relationships423. **Design workflow** — draft → review → approved → published434. **Plan localization** — language variants, fallback, RTL445. **Choose CMS architecture** — headless (API), coupled, hybrid456. **Design delivery API** — query, filter, personalize467. **Plan migration** — content mapping, transformation scripts4748## References49- `../backend/backend-architecture/SKILL.md` — API design50- `../../frontend/frontend-design/SKILL.md` — content rendering51- `../../data/data-etl-pipeline/SKILL.md` — content migration
quantumquirkxyz