Editor Routes
The editor route group provides a dedicated full-screen content authoring environment for the posts module.
On this page
Route structure
| Maintainer reference | Purpose | Maintainer reference |
|---|---|---|
| src/app/(editor)/layout.tsx | Minimal editor layout without dashboard chrome. | Editor route group |
| src/app/(editor)/content/editor/[kind]/[id]/page.tsx | Content editor entrypoint. | Implementation referencesrc/features/cms/ui/editor |
| src/app/(editor)/content/editor/[kind]/[id]/preview/page.tsx | Preview entrypoint for draft or published output. | Implementation referencesrc/features/cms |
Editor.js canvas
The CMS uses Editor.js-compatible content blocks and module-owned validation before content is saved or published.
Kind-based routing
The kind parameter maps content workflows such as post, page, faq, changelog, case-study, and team content.
Scheduling and revisions
Scheduled publishing, revision history, and local recovery are part of the posts module behavior.
Editor modification rules
- Validate editor output server-side before publishing.
- Test create, edit, save, schedule, publish, preview, and public render paths after CMS changes.
- Keep content rendering separate from editor state management.
- Document new content kinds in both route and product module docs.