Skip to content

docs: source the Mintlify docs site from docs/ - #2

Open
lzrscg wants to merge 1 commit into
mainfrom
claude/mintlify-docs-jfjh6s
Open

docs: source the Mintlify docs site from docs/#2
lzrscg wants to merge 1 commit into
mainfrom
claude/mintlify-docs-jfjh6s

Conversation

@lzrscg

@lzrscg lzrscg commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Makes docs/ the single source for the hosted docs site at xspec.mintlify.site, replacing the Fumadocs site under website/.

What's in here

  • docs/docs.json — Mintlify config: same theme/colors/GitHub button as the current site, nav in the docs' existing reading order (Guide / Reference and workflows), and redirects mapping all 27 URLs of today's AI-generated site onto the 11 real pages.
  • docs/README.mddocs/index.md so the overview serves as the site root.
  • Body H1s hoisted into frontmatter (title, plus sidebarTitle where the nav label differs) — Mintlify renders the frontmatter title, so body H1s would show twice. GitHub still shows the title via the frontmatter table.
  • website/ removed (Fumadocs, superseded by Mintlify) along with docs/meta.json; README now links the hosted site.
  • Five verified back-ports from reviewing the AI-generated site against these docs: tag case-sensitivity note (writing-specs), ❌ invalid-marker-usage block + shadowing example (typescript), gitignore-pattern safety note (workspace), hash-independence consequence (impact), and an edge-kind table in the overview.

The AI-generated site content itself was checked claim-by-claim against specs/SPEC.md and src/: 22+ substantive errors (invented CLI output formats, a fabricated six-category impact model, a nonexistent --version flag, wrong exit codes). The repo docs won every disputed case, so this PR ports nothing else from the site; the site gets regenerated from these files instead.

Turning on auto-sync

After merging: in the Mintlify dashboard (xspec project → Settings → Git/GitHub), install the Mintlify GitHub App on modularcloud/xspec. The deployment then tracks docs/docs.json on main and every push to docs/ deploys automatically.

🤖 Generated with Claude Code

…s site

The hosted docs move to Mintlify (xspec.mintlify.site), pulling content
directly from docs/ — no separate content copy:

- add docs/docs.json (Mintlify config): nav mirroring the existing page
  order, the live site's theme, and redirects covering every URL of the
  current AI-generated site
- rename docs/README.md -> docs/index.md so it serves as the site root
- hoist each page's body H1 into frontmatter title (+ sidebarTitle where
  the nav label differs) so titles render once on the site
- commit the site favicon; drop the Fumadocs site (website/) and its
  docs/meta.json; point README.md at the hosted site

Also fold in the few verified improvements found while reviewing the
AI-generated site against these docs: tag case-sensitivity note, invalid
marker-usage examples, shadowing example, gitignore-pattern safety note,
hash-independence consequence, and an edge-kind table in the overview.

Co-Authored-By: Claude Fable 5 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant