Architecture
High-level shape of the integrated product and where Nuxt Content fits.
Architecture
The system is split into three layers:
Product shell
- public docs routes
- edit-mode routes
- navigation, publishing, and settings entry points
Content layer
- content files
- collection schemas
- markdown parsing
- content queries
Platform layer
- authentication
- permissions
- navigation management
- search
- media metadata
- publishing records
Architectural stance
Use Nuxt Content where it is strong.
Do not split reading and editing into separate frontend products.
Do not force platform workflows into plain markdown files when they clearly belong in a service layer.