Standalone pages
Pages outside the docs navigation, like a home page.
Standalone pages#
The top-level pages key declares routes that live outside the docs
navigation — a landing page, an about page, anything that should not appear in
the sidebar. Each entry maps a route path to a TSX, MDX, or Markdown file under
content/pages/:
path: the route, starting with/. An entry for/becomes the site home page, replacing the default redirect to the first docs page — the header brand link then points at/too.page: the file slug undercontent/pages, so"home"renderscontent/pages/home.tsx,.mdx, or.md. TSX takes precedence when more than one matching file exists.title: optional document title for the browser tab and social previews. Frontmattertitlewins when both are set.
Layout#
Standalone pages render with the site chrome — banner, header, and footer — but no sidebar, table of contents, or previous/next links. The content spans the full container width. Markdown and MDX pages receive the same typography styles and components as documentation pages:
TSX pages render as regular React components without the docs-markdown
wrapper, so they own their spacing, typography, and layout. Export a
frontmatter object for page metadata and per-page options:
All built-in components are available from
@umami/shiso/components in TSX pages. In MDX they remain available without
imports.
Behavior notes#
- Paths must not collide with docs URLs, sit inside the docs prefix, or use
/404(reserved for the error page). - Standalone pages are prerendered like docs pages, included in
sitemap.xml, and support last-modified timestamps. Markdown and MDX pages are also published with a raw Markdown copy (/about.md); TSX pages are not. Setnoindex: truein frontmatter to keep one out of the sitemap and search engines. - They are not included in site search.