docs: rewrite the Orbit / GitLab Knowledge Graph docs

Meg Correnrequested to merge
angelo-meg-v2-docs into main

What does this MR do and why?

Full rewrite of the public Orbit / GitLab Knowledge Graph docs.

Structure. Splits the docs into two parallel surfaces in docs/source/:

  • remote/ - Orbit Remote, the .com / SaaS service
  • local/ - Orbit Local, the developer-preview CLI

Each side has its own overview, get started, how it works, indexing scope, schema reference, and Access section. This matches the customer-facing naming convention ("Orbit Remote" and "Orbit Local") and stops conflating the two products.

Remote pages.

  • Overview, How Orbit works, Get started, What Orbit indexes, Schema reference (all 24 node types across 6 domains), Cookbook
  • Access: Duo Agent Platform, MCP, glab orbit, REST API

Local pages.

  • Overview, Get started (slim "pick an access method" page), How it works, What Orbit Local indexes (code-only scope, no SDLC layer), Schema reference (4 node types)
  • Access: orbit CLI, glab orbit, MCP

Cookbook QA. All 13 cookbook queries QAed against live Orbit (v0.51.0). Removed 6 examples that fail today; kept 7 verified. Bug list sent to Angelo for follow-up. See the build log for the breakdown.

Forward-looking docs. glab orbit and glab orbit local subcommands, plus glab orbit setup, are documented as the planned shape so docs land before the code.

Out of scope here.

Testing

  • All Remote and Local pages render and return 200 against the local Hugo server (make view against docs-gitlab-com)
  • 7 cookbook queries verified end-to-end against live Orbit v0.51.0
  • Naming convention ("Orbit Remote", "Orbit Local") applied consistently across pages, headings, anchors, and tables

Performance Analysis

Docs-only change. No runtime or query-path impact.

  • This merge request does not introduce any performance regression. If a performance regression is expected, explain why.
Edited by Meg Corren

Merge request reports