sambadocsDocs
Sign inGet early access

Getting started

  • Quickstart
  • Connect your GitHub repo

Writing docs

  • Project structure
  • Writing pages
  • Components

Features

  • API reference from OpenAPI
  • AI editor assistant
  • Search & reader chat

Quickstart

Connect a GitHub repo and get a hosted docs site live in a few minutes.

On this page
  • 1. Connect your repository
  • 2. Add a docs.json
  • 3. Write a page
  • 4. Push, and you're live
  • Where to next

Sambadocs turns a GitHub repository of Markdown into a hosted documentation site. Point it at a repo, and every push publishes — no build config, no CI to wire up, no separate hosting to manage.

This guide takes you from zero to a live docs site.

What you need

A GitHub account and a repository with at least one .mdx (or .md) file. Don't have one yet? You can start from an empty repo — Sambadocs can scaffold a starter docs.json and a first page for you.

1. Connect your repository

Sign in, then connect a repo through the GitHub App. You choose exactly which repositories Sambadocs can see — it never gets blanket access to your account. The full walkthrough lives in Connect your GitHub repo.

2. Add a docs.json

docs.json at the root of your repo tells Sambadocs what your site is called and how the pages are organized into the sidebar:

{
  "name": "Acme Docs",
  "navigation": [
    {
      "group": "Getting started",
      "pages": ["introduction", "quickstart"]
    }
  ]
}

Each entry in pages is the path to an .mdx file (without the extension), relative to the repo root. That's the whole config for a basic site — you add groups and pages as your docs grow.

3. Write a page

Pages are plain MDX: Markdown, plus a small set of components for callouts, tabs, and code. Frontmatter sets the page title and description:

---
title: Introduction
description: What Acme is and why you'd use it.
---
 
Welcome to Acme. This guide walks you through the basics.

4. Push, and you're live

Commit and push to your default branch. Sambadocs builds the site and publishes it — typically within seconds — at your project's URL (your-project.sambadocs.com, or a custom domain on Pro).

That's the whole loop

Edit Markdown in Git → push → it's live. Your repo stays the source of truth, and there's no proprietary format to export if you ever leave.

Where to next

  • Connect your GitHub repo — the connection flow in detail, including how builds trigger on each push.
  • Prefer not to write everything by hand? The built-in AI editor can draft whole pages from your repo and keep them current.