Skip to content

Handbook Usage

The handbook is organized to help you quickly find the information you need. It’s built on a Git-Ops model, meaning the entire handbook is managed like a software project in a Git repository. This approach is inspired by industry leaders like GitLab, who have pioneered transparent, collaborative documentation at scale.

This handbook is not a typical document—it’s a static website generated from a collection of Markdown files. Here’s how it works:

  1. Content is in Markdown: Every page in this handbook is a .mdx file located in the src/content/docs/ directory of our repository.
  2. Astro Builds the Site: We use a static site generator called Astro with the Starlight theme to convert these Markdown files into the web pages you see.
  3. Changes are Merged: When you contribute an edit, you’re changing one of these source files. Once your change is approved and merged, the site automatically rebuilds and publishes the new version.

This process ensures that our documentation is always up-to-date, version-controlled, and open to collaboration.

The handbook uses a simple structure:

  • Engineering - Technical documentation, workflows, and engineering practices
  • About the Handbook - This section, covering handbook philosophy and contribution

The sidebar on the left provides quick navigation to all sections. Click any section to expand and see its pages.

Use the search functionality (Command/Ctrl + K) to quickly find specific information across the entire handbook.

All internal links use relative paths. This ensures information remains connected even as we reorganize content.

The handbook supports Mermaid diagrams for flowcharts, sequence diagrams, and other visual representations. Use fenced code blocks with the mermaid language to create diagrams:

```mermaid
graph TD
A[Start] --> B{Decision}
B -->|Yes| C[Action 1]
B -->|No| D[Action 2]
```

The handbook is updated regularly. Check the Handbook Changelog to see recent changes.

  1. Start with the Overview - Each section has an index page that provides an overview
  2. Follow Links - Internal links help you discover related information
  3. Check the Date - Some information may have timestamps or “last updated” dates
  4. Ask for Updates - If you find outdated information, contribute an update (see Contribution Guide)

Inspired by GitLab’s handbook model, we organize content to:

  • Make it easy to find what you’re looking for
  • Encourage discovery of related information
  • Support quick onboarding for new team members
  • Maintain a historical record of our evolution