For AI agents: the complete documentation index is available at https://ciderpress.dev/llms.txt, the full documentation bundle is available at https://ciderpress.dev/llms-full.txt, and this page is available as Markdown at https://ciderpress.dev/reference/frontmatter.md.
Get started →
ciderpress

    Frontmatter Fields

    ciderpress pages support standard Rspress frontmatter fields. Frontmatter is defined in YAML at the top of markdown files or injected via the defaults field on a Page / Workspace (renamed from the legacy frontmatter field — same type, different name).

    ---
title: My Page
description: A short summary of this page.
---

# My Page

    See the Content concept for injection and inheritance patterns.

    Standard fields

    FieldTypeDefaultDescription
    titlestring—Page title (used in sidebar, browser tab, SEO)
    titleTemplatestring | boolean—Title template override (%s is page title)
    descriptionstring—Meta description for SEO and card previews
    layoutstring'doc'Page layout mode — 'doc' / 'page' / 'home' ship out of the box (see Layout values)
    sidebarbooleantrueShow or hide the sidebar
    asideboolean | 'left'trueTable of contents position
    outlinefalse | number | [min, max] | 'deep'—Outline heading depth
    navbarboolean | { width?: 'container' | 'full' }trueShow or hide the top navigation bar, or configure its width (see Navbar width)
    editLinkbooleantrueShow or hide the "Edit this page" link
    lastUpdatedbooleantrueShow or hide the last updated timestamp
    footerbooleantrueShow or hide the page footer
    pageClassstring—Custom CSS class added to the page container
    head[string, Record<string, string>][]—Extra elements injected into <head> (see below)
    seoPageSeoConfig—Canonical, crawler, Open Graph, and Twitter overrides (see below)
    badgestring | BadgeConfig | array—Ad-hoc page badge(s) shown in the sidebar and breadcrumb (see Badges)
    statusstring | string[]—Named status id(s) from the registry (see Badges)

    Layout values

    ValueDescription
    'doc'Standard documentation layout with sidebar and table of contents
    'page'Full-width page with no sidebar or table of contents
    'home'Home page layout with hero section and feature cards

    Set navbar.width in page frontmatter independently of the page layout:

    ---
pageType: custom
navbar:
  width: container
---
    • container aligns the navigation with the home page frame and its theme-defined max width.
    • full spans the viewport like documentation navigation.
    • Omit width to keep existing behavior: home pages use container; other page types use full.

    navbar: false hides the navigation. navbar: true or an object shows it. No enabled property is needed.

    The same option works in config-side Page.defaults and Workspace.defaults:

    {
  title: 'Features',
  path: '/features',
  include: 'docs/features.mdx',
  defaults: { navbar: { width: 'container' } },
}

    Per-file frontmatter replaces the config-default navbar value; it is not deep-merged. For example, navbar: true restores the page type's default width even when config defaults set a width. The width option changes only navigation width, not the page layout, sidebar, or footer.

    Outline values

    ValueDescription
    falseDisable the outline entirely
    numberShow headings up to this depth (e.g. 3 for h1–h3)
    [min, max]Show headings within a depth range (e.g. [2, 4])
    'deep'Show all heading levels

    Aside values

    ValueDescription
    trueShow table of contents on the right (default)
    'left'Show table of contents on the left
    falseHide the table of contents

    SEO

    All page-specific search and social overrides are nested under seo:

    ---
title: Configuration
description: Complete reference for configuring Ciderpress.
seo:
  title: Ciderpress Configuration Reference
  canonical: https://ciderpress.dev/reference/configuration
  socialImage: /social/configuration.png
  robots:
    index: true
    follow: true
  openGraph:
    type: article
  twitter:
    card: summary_large_image
    creator: '@ciderpress'
---
    FieldTypeDefaultDescription
    titlestringpage titleSearch and social title override
    descriptionstringpage descriptionSearch and social description override
    canonicalstring | falseseo.origin plus routeAbsolute canonical URL, or false to omit
    socialImagestringsite defaultOpen Graph and Twitter image override
    robotsRobotsConfigsite defaultPer-page index and follow directives
    openGraphPageOpenGraphConfig | falsesite defaultOpen Graph title, description, type, or image
    twitterPageTwitterConfig | falsesite defaultTwitter title, description, card, or creator

    Head format

    The head field accepts an array of tuples. Each tuple is [tagName, attributes]:

    head:
  - - meta
    - name: og:title
      content: My Page
  - - link
    - rel: canonical
      href: https://example.com/my-page

    Equivalent injected via Page.defaults in the config:

    {
  title: 'Architecture',
  path: '/architecture',
  include: 'docs/architecture.md',
  defaults: {
    head: [
      ['meta', { name: 'og:title', content: 'My Page' }],
      ['link', { rel: 'canonical', href: 'https://example.com/my-page' }],
    ],
  },
}

    Custom fields

    The two surfaces have different rules:

    • YAML frontmatter in .md / .mdx source files — arbitrary keys are accepted and passed through to Rspress's page data object. Use these for metadata that theme components or plugins consume.
    • Config-side defaults — validated against a .strict() Zod schema. Only the fields documented above are accepted; unknown keys fail at config load time with a clear error.
    ---
title: API Routes
category: reference
difficulty: advanced
---

    Custom fields are accessible in theme components via the page data object.