feat: migrate from Fumadocs/Next.js to VitePress

[vitbokisch]

Summary

Complete rewrite of the documentation site from Fumadocs (Next.js) to VitePress for better alignment with Pyreon's Vite-native ecosystem.

What changed

• Framework: Next.js 16 + Fumadocs → VitePress 1.6.4 + Vue 3.5
• Components: 5 React components → Vue SFCs (PackageBadge, PropTable, APICard, CompatMatrix, Since)
• Content: 52 MDX pages → VitePress markdown with code groups
• Search: Fumadocs static search → VitePress built-in local search (MiniSearch)
• Styling: Tailwind CSS v4 + custom CSS → VitePress default theme + brand overrides
• Dependencies: 10 deps → 3 deps (vitepress, vue, @biomejs/biome)

Why

• Pyreon is a Vite-native framework — docs should use Vite tooling, not React/Next.js
• VitePress is what Vue, Vite, Rolldown, and similar projects use
• Faster builds (~18s vs ~20s), simpler stack, smaller dependency footprint
• Built-in code groups for package manager tabs (npm/bun/pnpm/yarn)

Output

• 56 HTML pages rendered
• Build: ~18s
• Emerald/teal brand colors matching Pyreon identity

Test plan

• bun run lint passes (3 files, no issues)
• bun run build passes (56 pages rendered)
• All 52 documentation pages converted
• Custom components render correctly
• CI workflow runs cleanly

🤖 Generated with Claude Code