Move documentation to GitBook (Git Sync)? #468

Thinking about moving our docs to GitBook via Git Sync — markdown stays in /docs/, navigation via SUMMARY.md, just a .gitbook.yaml at repo root. No new build pipeline.

Why now

Docs today are scattered: README.md (~500 lines) + SETUP.md + /docs/*.md + /ee/docs/*.md + per-package READMEs. No TOC, no search, no navigation, inconsistent voice between files.

Why GitBook over alternatives

• Markdown stays in-repo and PR-reviewable (no proprietary editor lock-in).
• SUMMARY.md is portable — works with honkit/mdBook later if we ever move off GitBook.
• Hosted search + nav + versioning with zero CI/CD to maintain.
• Docs ship independently of backend releases.

Considered and skipped

• Docusaurus / Mintlify / MkDocs — all add a build step we would own.
• Staying as-is — scaling pain only grows as the registry and CLI surface grow.

Ask

Is GitBook the right call, or does anyone have a strong preference for a different tool before I start the restructure?