On this page
Landing pages#
A landing page is a Markdown file with template: landing.html. Its sections are described in front matter, so the page stays data you can review in a diff — no HTML, no components to import. The home page of this site is one.
---
template: landing.html
hero:
eyebrow: "v2.0 is out"
title: "Ship docs<br>*people read*."
text: One sentence that explains the product.
actions:
- {text: Get started, link: guide/, icon: rocket, primary: true}
- {text: GitHub, link: "https://github.com/me/project", icon: brand-github}
install: pip install my-project
sections:
- type: features
title: Why it is different
items:
- {icon: zap, title: Fast, text: Builds in under a second., link: guide/speed/}
- {icon: lock, title: Private, text: Runs entirely on your machine.}
- type: cta
title: Ready?
actions:
- {text: Read the guide, link: guide/, primary: true}
---
A link to a Markdown file, such as guide.md or guide/speed.md#cache, leads to the page built from it. Like a Markdown link, it is relative to the landing page, and the build warns when the file doesn't exist. Other links are relative to the site root, like nav entries. Text fields accept inline Markdown.
Hero#
eyebrowstringtitlestring<br> breaks lines; *emphasis* is drawn in the accent colour. Defaults to the page title.textstringsite_description.actionslisttext, link, icon, primary.installstringcodeobjecttitle, lang, content.imagestringcode.Sections#
Every entry in sections has a type and optional eyebrow, title, text, id and tone: soft (a tinted background).
featuresKeys items, columnsicon, title, text and an optional link.splitKeys bullets, actions, code or image or markdown, reversestatsKeys itemsvalue and label.stepsKeys itemstitle and text.faqKeys itemsq and a (Markdown).ctaKeys actionscontentsections is omitted, the body is shown under the hero.Tip
Keep the page body for content that agents and search should see. The front-matter sections are visual; the Markdown copy of a landing page contains its title, text and body.