A page can override the site defaults with a fenced block at the very top of the file:
---
title: Deploying to production
description: The checklist we follow every Thursday.
author: Priya
date: 2026-07-14
tags: deploys, checklist
---
# Deploying to production
Body starts here.
The --- fence is required. Without it, the lines are just text — this is
what stops an ordinary paragraph beginning with "Note:" from being read as
settings.
The keys#
| Key | What it does |
|---|---|
title | Page title, in the browser tab, share previews and navigation |
description | Summary under the title, and in search results |
author | Shown in the page byline |
image | A share image for this page. Overrides the generated card |
date | Shown as "Updated …". Falls back to the file's modified time |
tags | Comma-separated, shown as chips |
How settings resolve#
Page front matter wins, then _config.md, then a built-in default.
title is the exception — it never inherits the site title, because
that would name every untitled page the same. An untitled page falls back
to its _toc.md link text, then to its file name.
Tip
If a page needs no settings, leave the block out entirely. A file that
starts with a # Heading is perfectly valid.