Add a Real Content Model
This chapter stops treating “a page” as one HTML field and starts modeling editorial state explicitly.
Replace app.toml With A Real Content Model
At this stage the manifest should not only declare sites and modules. It should also declare the page shape the CMS is allowed to store.
name = "tutorial-app"
display_name = "Tutorial App"
[i18n]
default_locale = "en-GB"
supported_locales = ["en-GB", "fr-FR"]
[[sites]]
id = "tutorial-uk"
display_name = "Tutorial UK"
brand_name = "Tutorial"
canonical_domain = "uk.127.0.0.1.nip.io"
additional_domains = ["www.127.0.0.1.nip.io"]
default_locale = "en-GB"
supported_locales = ["en-GB"]
[[sites]]
id = "tutorial-fr"
display_name = "Tutorial France"
brand_name = "Tutorial"
canonical_domain = "fr.127.0.0.1.nip.io"
additional_domains = []
default_locale = "fr-FR"
supported_locales = ["fr-FR"]
[[content_models]]
name = "landing_page"
label = "Landing page"
[[content_models.fields]]
name = "title"
type = "string"
required = true
[[content_models.fields]]
name = "slug"
type = "slug"
required = true
[[content_models.fields]]
name = "summary"
type = "text"
required = true
[[content_models.fields]]
name = "page_type"
type = "string"
required = true
[[content_models.fields]]
name = "template"
type = "string"
required = false
[[content_models.fields]]
name = "seo_title"
type = "string"
required = false
[[content_models.fields]]
name = "seo_description"
type = "text"
required = false
Add One Real Page Record
Do not stop at schema. Check in one real page instance as tutorial content.
content/pages/spring-sale.json
{
"id": "page-spring-sale",
"type": "landing_page",
"title": "Spring Sale",
"slug": "spring-sale",
"summary": "Fresh arrivals and seasonal offers for the new quarter.",
"settings": {
"page_type": "landing_page",
"template": "pages/landing-page",
"seo_title": "Spring Sale | Tutorial App",
"seo_description": "Fresh arrivals and seasonal offers for the new quarter.",
"show_in_navigation": true,
"allow_indexing": true
}
}
This is the minimum useful distinction to make explicit:
- content fields
- page settings
- future ordered blocks
What Each File Is Doing
app.toml
This file defines the content schema the CMS is allowed to use.
The important section is [[content_models]]. It says that a landing_page record exists and
lists the fields a valid page of that type can contain.
In this example:
title,slug, andsummaryare normal page contentpage_type,template,seo_title, andseo_descriptionestablish the shape of page settings
That matters because it keeps page structure explicit. The manifest says which fields the product supports before any editor creates records.
content/pages/spring-sale.json
This file is the actual content instance.
The important sections are:
- top-level fields such as
title,slug, andsummaryThese are the page’s actual editorial values. settingsThis is where the page instance stores page-level behavior and metadata.
That separation is important for later chapters:
- content fields are what the page says
- settings tell the runtime how to treat the page
Examples from the file:
templatechooses which page template should render the recordseo_titleandseo_descriptionprovide search metadatashow_in_navigationandallow_indexingaffect page visibility and crawl behavior
What Behavior This Enables
Once these two files exist together:
- the app can distinguish content schema from real page records
- a page record can carry both editorial copy and page-level settings
- later CMS admin forms have a real place to save structured page settings
- later block chapters can add ordered blocks without redefining the page model
- later render-model shaping can load a page instance instead of improvising one from template code
Checkpoint
Run:
cargo run -p tutorial-app-bin -- validate
cargo run -p tutorial-app-bin -- serve
Then verify:
- the schema exists
- one real page instance exists
- the page record has settings as well as content
- the app still validates and serves with the new content model