Meta Loaders

Control sidebar groups with meta.json or _meta.json — per-directory metadata for titles, icons, ordering, and collapse state.

Boltdocs automatically loads meta.json or _meta.json files from your docs directories to control sidebar group metadata without editing each individual page.

meta.json ReferenceLink

PropertyTypeDescription
titlestringDisplay name for this sidebar group.
orderstring[] | numberExplicit ordering — either a position number or an array of page slugs in the desired order.
iconstringLucide icon name or inline SVG string for the group icon.
collapsiblebooleanWhether users can collapse/expand this group. Default: true.
collapsedbooleanWhether the group starts collapsed on page load. Default: false.

ExamplesLink

Basic Group ConfigurationLink

json
{
  "title": "Getting Started",
  "icon": "Rocket"
}

Collapsed by DefaultLink

json
{
  "title": "Advanced Topics",
  "collapsed": true,
  "collapsible": true
}

Custom OrderingLink

json
{
  "title": "Guide",
  "order": ["installation", "configuration", "deployment"]
}

Or use a numeric position:

json
{
  "title": "Guide",
  "order": 2
}

Full ExampleLink

text
docs/
├── (guides)/
│   ├── meta.json
│   ├── index.md
│   ├── installation.md
│   └── configuration.md
└── (api)/
    ├── meta.json
    └── reference.md

guides/meta.json:

json
{
  "title": "Guides",
  "icon": "BookOpen",
  "collapsible": true,
  "collapsed": false
}

api/meta.json:

json
{
  "title": "API Reference",
  "icon": "Code2",
  "collapsed": true
}

Difference Between meta.json and _meta.jsonLink

Both work identically. The underscore variant is useful when you want the file hidden from the docs but still loaded:

  • meta.json — Visible in some IDEs, may show up in file explorers
  • _meta.json — Excluded from routing like other underscore-prefixed paths

Use whichever fits your workflow best.


PrecedenceLink

meta.json settings apply in this order (later ones override earlier ones):

  1. theme.sidebarGroups in configuration (global)
  2. meta.json / _meta.json in the folder
  3. Frontmatter of the folder's index.md (e.g., groupTitle, groupPosition)

DebuggingLink

If meta.json isn't taking effect:

  1. Verify the file is named exactly meta.json or _meta.json
  2. Check that the JSON is valid (no trailing commas)
  3. Make sure the file is inside a folder containing .md or .mdx files
  4. Check the console for "[Boltdocs] Failed to read meta.json" warnings
Last updated on October 18, 2026

Was this page helpful?