Content types

Every page has a content type that decides where it lives on your site and how it is presented. One site can hold a blog, documentation, standalone pages, and a homepage at the same time. You set the content type in the page editor, or in front matter when publishing through the API.

Blog

Blog posts appear together in a feed at /blog/, ordered by date, with each post at a URL like /blog/why-we-moved-to-postgres. They are the right choice for anything time-based. Posts support tags, which group related posts together.

---
title: Why we moved to Postgres
contentType: blog
tags: [engineering, databases]
---

Docs

Docs pages appear under /docs/ with sidebar navigation instead of a feed. They suit guides, references, and anything a reader moves through by topic rather than by date.

Docs pages can be grouped into sections, which produce URLs like /docs/guides/getting-started.

---
title: Getting started
contentType: docs
section: guides
---

Standalone

A standalone page lives at its own URL, like /about or /contact. Use it for pages that stand on their own.

Standalone pages can also carry a section, which places them under a top-level path of your choosing, such as /recipes/pasta or /projects/redesign, with a generated listing page at /recipes/. This is how you add whole sections to your site beyond blog and docs. See Sections.

Homepage

The homepage is what visitors see at the root of your site. A site has one homepage page. Depending on your theme settings it can show recent posts and section listings below your content, or stand alone as a fully custom page.

Changing your mind later

The same slug can exist under different content types and sections. For example, /docs/guides/overview and /docs/tutorials/overview are separate pages. And because the content type is just a field on the page, you can restructure later without recreating anything.