Content types

Use collections to publish blogs, courses, products, and more alongside your docs.

Blode.md supports more than just documentation. You can publish blogs, courses, product pages, and other content types by defining collections in your configuration. Each collection has its own content directory, URL prefix, and navigation structure.

Define a collection

Collections use the SiteConfig format with a top-level collections array. Each collection is an object with its own id, type, and content root:

{
  "collections": [
    {
      "id": "docs",
      "type": "docs",
      "root": "content/docs",
      "slugPrefix": "/docs",
      "navigation": {
        "groups": [
          { "group": "Getting started", "pages": ["index", "quickstart"] }
        ]
      }
    },
    {
      "id": "blog",
      "type": "blog",
      "root": "content/blog",
      "slugPrefix": "/blog",
      "sort": "date:desc",
      "index": true
    }
  ]
}

Collection properties

Field	Type	Description	Required	Default
`id`	string	Unique identifier for the collection.	Yes	—
`type`	string	The content type. Determines which frontmatter fields are available and how pages are rendered.	Yes	—
`root`	string	Path to the content directory for this collection, relative to the project root.	Yes	—
`slugPrefix`	string	URL prefix for all pages in this collection.	Yes	—

Available types

Type	Use case
`site`	General-purpose website pages
`docs`	Documentation with sidebar navigation
`blog`	Blog posts sorted by date
`courses`	Ordered learning content with progress
`products`	Product pages with pricing and metadata
`notes`	Short-form notes and snippets
`forms`	Form pages with input fields
`sheets`	Spreadsheet-style data pages
`slides`	Presentation slides
`todos`	Task lists and checklists

Type-specific frontmatter

Each collection type supports additional frontmatter fields beyond the standard title and description.

---
title: Launch week recap
description: Everything we shipped this week.
date: 2025-01-15
tags:
  - announcements
  - releases
author: Jane Smith
image: /images/launch-week.png
---

Full example

Here is a complete docs.json that defines both documentation and a blog:

{
  "name": "my-project",
  "theme": "mint",
  "colors": { "primary": "#0D9373" },
  "collections": [
    {
      "id": "docs",
      "type": "docs",
      "root": "content/docs",
      "slugPrefix": "/docs",
      "navigation": {
        "groups": [
          {

When you use the collections array, it replaces the top-level navigation field. Each collection manages its own navigation independently.

Define a collection

Collections use the SiteConfig format with a top-level collections array. Each collection is an object with its own id, type, and content root:

{
  "collections": [
    {
      "id": "docs",
      "type": "docs",
      "root": "content/docs",
      "slugPrefix": "/docs",
      "navigation": {
        "groups": [
          { "group": "Getting started", "pages": ["index", "quickstart"] }
        ]
      }
    },
    {
      "id": "blog",
      "type": "blog",
      "root": "content/blog",
      "slugPrefix": "/blog",
      "sort": "date:desc",
      "index": true
    }
  ]
}

Collection properties

Field	Type	Description	Required	Default
`id`	string	Unique identifier for the collection.	Yes	—
`type`	string	The content type. Determines which frontmatter fields are available and how pages are rendered.	Yes	—
`root`	string	Path to the content directory for this collection, relative to the project root.	Yes	—
`slugPrefix`	string	URL prefix for all pages in this collection.	Yes	—

Available types

Type

Use case

site

General-purpose website pages

docs

Documentation with sidebar navigation

blog

Blog posts sorted by date

courses

Ordered learning content with progress

products

Product pages with pricing and metadata

notes

Short-form notes and snippets

forms

Form pages with input fields

sheets

Spreadsheet-style data pages

slides

Presentation slides

todos

Task lists and checklists

Full example

Here is a complete docs.json that defines both documentation and a blog:

{
  "name": "my-project",
  "theme": "mint",
  "colors": { "primary": "#0D9373" },
  "collections": [
    {
      "id": "docs",
      "type": "docs",
      "root": "content/docs",
      "slugPrefix": "/docs",
      "navigation": {
        "groups": [
          {

When you use the collections array, it replaces the top-level navigation field. Each collection manages its own navigation independently.