How Compass Is Organized
Understand how Compass is structured so you know where to customize content, navigation, and layout.
Compass is a docs theme built around a small set of moving parts. Once you know where each part lives, the project becomes much easier to customize.
Theme structure
The theme is organized into a few main areas:
src/pagescontrols routessrc/componentscontains shared UI piecessrc/layoutswraps page structuresrc/content/docsstores article contentsrc/data/docs.tsdefines the docs information architecture
How content is grouped
Compass uses a three-level model:
- Parent categories such as
Getting StartedorIntegrations - Sub-categories such as
Compass DocsorStart Here - Individual articles inside those sub-categories
This structure powers:
- the homepage sections
- the left sidebar on docs pages
- the article search experience
Where navigation comes from
The docs navigation is not inferred only from folders. It is primarily defined in src/data/docs.ts, which gives you explicit control over:
- labels
- slugs
- parent grouping
- card descriptions
- icons for the homepage
Where article metadata comes from
Each article in src/content/docs uses frontmatter like this:
---
title: "Manage Docs"
description: "Update structure, copy, and article metadata across your Compass docs."
category: "compass-docs"
order: 2
updatedAt: 2026-06-03
---
The category value links an article to one of the sub-categories declared in src/data/docs.ts.
How the pages connect
/renders the homepage sections and cards/:parentrenders a parent landing page such asgetting-started/:parent/:categoryrenders a sub-category page such asgetting-started/compass-docs/:parent/:category/:slugrenders the individual article
Once this model makes sense, you can start swapping in your own structure without fighting the theme. For a deeper route-specific walkthrough, see How Navigation Works.