Skip to content
Sign in

Content structure

Flat-file pages, host database, Control Panel, and public routes.

Two layers.

  • Flat files — pages, branding, theme, forms, libraries, and navigation-related JSON under content/sites/{CMS_SITE}/

  • Host database (SQLite by default) — users, roles, sessions, form submissions, audit / security logs. Not used for page HTML; pages stay on disk.

Pages. Each page is Markdown with YAML front matter plus an HTML body (classic editor), or a companion {slug}.sections.json when Page Builder is enabled:

content/sites/{CMS_SITE}/pages/home.md
content/sites/{CMS_SITE}/pages/home.sections.json

With Translation enabled, locale sidecars use {slug}.{locale}.md and {slug}.{locale}.sections.json (same public URL).

Common front-matter fields include title, published, access (public or members), show_in_nav, nav_order, parent_entry (for nested nav), and SEO fields when set from the Control Panel.

Site chrome.

  • site.json — site name, homepage slug, search / robots visibility, component toggles

  • branding.json — colors and logos (also edited at Control Panel → Branding)

  • theme.json — Site Theme layout and footer options (/cp/theme)

  • styling.json — content typography

  • translation.json — locales, switcher, nav label overrides (Translation module)

  • redirects.json — path redirects; public /sitemap.xml lists published public pages

  • seo-libraries.json — meta for public library index pages (Identity → SEO)

Control Panel (/cp). Identity (theme, styling, site settings, branding, SEO, redirects, translation), Content (navigation, pages, assets, forms), Libraries & Extras (when enabled), People (users, roles), Tools (updates, email, CAPTCHA, backup/export, optimization), System (info, security, analytics, audit), and License status. Editors and Contributors can open the CP with capability-scoped access; Contributors cannot publish.

Public routes. Homepage from Site Settings; other pages at /{slug} (and knowledgebase articles under /docs/… on this product site). Guests use Light / Dark / System locally; signed-in users can persist theme under Account Settings (/account).

Related: Page Builder · Navigation · Assets · Control Panel · Libraries.