Getting Started

What A Relevate Project Looks Like

Start with a small, easy-to-navigate docs project.

Step 1: Start With A Small Project

Create a small docs.json and a few key pages.

{
  "$schema": "https://relevate.app/schemas/docs/0.1/schema.json",
  "version": "0.1",
  "name": "Acme Docs",
  "description": "Product guides, rollout docs, and team documentation",
  "logo": {
    "light": "/public/light.svg",
    "dark": "/public/dark.svg"
  },
  "favicon": "/public/favicon.svg",
  "navigation": {
    "tabs": [
      {
        "id": "docs",
        "label": "Docs",
        "icon": "book",
        "content": [
          {
            "title": "Getting Started",
            "pages": ["index", "getting-started", "quickstart"]
          },
          {
            "title": "Product Features",
            "pages": ["features/changelog", "personalization", "content-formats", "assistant"]
          }
        ]
      }
    ]
  }
}

Step 2: Write A Clear Homepage

Your homepage should answer three questions:

• What is this product?

• Where should a new reader start?

• What should an experienced reader open next?

Keep the copy short and point readers to the next step.

Step 3: Add One Task-Based Guide

Your first guide should help readers do one real task.

Good first guides:

• Install the CLI

• Start a local preview

• Add a logo and brand colors

• Publish the first version of your docs

Step 4: Add Product Signals

Once the first guide exists, add pages that help readers trust the docs over time:

• A changelog for product updates and fixes

• Personalization for showing the right guidance and API defaults to signed-in readers

• Markdown and text export notes for agents, search, and support workflows

• Assistant guidance so AI answers stay grounded in your docs

Step 5: Plan Your Languages Early

If you plan to support more than one language, decide on the structure early and keep page names consistent.

Step 6: Translate Navigation Labels

Turn on language switching, then translate the labels readers actually see.

{
  "navigation": {
    "languages": {
      "default": "en",
      "items": ["en", "fr", "nl", "jp"]
    },
    "tabs": [
      {
        "id": "docs",
        "label": {
          "en": "Docs",
          "fr": "Documentation",
          "nl": "Documentatie",
          "jp": "ドキュメント"
        },
        "content": [
          {
            "title": {
              "en": "Getting Started",
              "fr": "Bien demarrer",
              "nl": "Aan de slag",
              "jp": "はじめに"
            },
            "pages": ["getting-started", "cli"]
          }
        ]
      }
    ]
  }
}

Recommended First Milestone

Ship these basics before adding more pages:

• One homepage

• One getting-started guide

• One CLI quickstart

• One changelog or product updates page

• One localized landing page

Next Pages