Documentation site for Roves, built with Next.js and Fumadocs.
Structurally modeled after pixi-vn.wiki's own docs site (Fumadocs setup, theming pattern, custom search/OG/comments), scoped down for a single-product, English-only docs site — no i18n, no jsdoc auto-generation, no live playgrounds/AI chat.
npm install
npm run devOpen http://localhost:3000.
| Path | What |
|---|---|
app/(home) |
Landing page. |
app/docs |
Documentation layout and pages, rendering content/docs/**/*.mdx. |
app/api/search/route.ts |
Search API (Orama, via fumadocs-core/search/server). |
app/og/docs/[...slug]/route.tsx |
Per-page OG image generation (next/og). |
content/docs/ |
All documentation content. Each subfolder has a meta.json controlling sidebar order/titles. |
lib/shared.ts |
Site-wide constants — app name, GitHub repo, giscus config. |
lib/layout.shared.tsx |
Shared nav/layout options (logo, GitHub link). |
components/search.tsx |
Custom search dialog UI, still Orama-backed. |
components/giscus-comments.tsx |
Per-page comments, rendered on every doc page once configured (see below). |
Colors and the heading font are pulled directly from the engine's own brand assets:
- Primary/secondary colors are extracted from
icon.svg(seeapp/global.css). - The heading font is Metal Mania — the same font used for the "Roves" wordmark on the engine's own boot splash screen.
- Body text is Space Grotesk.
Comments are wired up but render nothing until two IDs are filled in:
- Enable Discussions on the
rovesGitHub repo. - Go to giscus.app, point it at
DRincs-Productions/roves, pick a discussion category, and copy the generateddata-repo-id/data-category-id. - Paste them into
lib/shared.ts'sgiscusConfig.