Skip to content
duxt

Frontmatter

The fields a page may carry beyond title and description, and the two the build fills in.

Content stores only what a collection's schema declares, so this is the complete list — an undeclared field is dropped silently, before the sidebar or the search ever sees it.

What you write

FieldTypeWhat it does
titlestringRendered as the page's <h1>, and its SEO and social title
descriptionstringThe page's summary — sidebar, cards, OG image, llms.txt
iconstringShown beside the entry in the sidebar, the section row and cards
navigationbooleanfalse hides the page from the navigation
layoutstringlanding renders the page without the docs layout
redirectFromstring[]Old URLs for this page — see Move a page
datestringWhen this page is dated, for the feed

title and description are the two the build warns about when they are missing. Neither breaks a page, and both quietly degrade the table of contents, the social card and llms.txt.

What the build fills in

FieldFilled byHolds
lastUpdatedthe git-meta moduleThe last commit that touched the file
contributorsthe git-meta moduleName, commit count and username, per author
rawbodythe collection schemaThe Markdown as written
sitemapthe sitemap integrationWhat puts the page in /sitemap.xml at all

Writing any of these by hand is pointless: the build overwrites them. Both git fields need a real history, so a remote source needs history: true — see the sources reference.

The file name carries two more things

  • A numeric prefix orders the tree and is stripped from the URL: 3.guides/2.deploy.md is served at /guides/deploy. Reordering never moves a URL.
  • .draft.md is a draft. It is served in the dev server and absent from the build. There is no draft: true, because a collection's contents are declared before any file has been read — see Collections.
Was this page helpful?