0docs vs VitePress

0docs is a free, open-source documentation platform that teams can self-host to create, style, version, and publish documentation. Its MIT-licensed editor arranges content into pages, sections, and blocks such as callouts, steps, code tabs, cards, accordions, and API endpoints. Users can change colors, fonts, sidebar presentation, and individual block styles, then publish documentation snapshots using a custom domain. The “Ask docs” feature answers questions from published documentation and requires an OpenAI API key; an OpenAI-compatible base URL override is documented. AI clients can use a built-in MCP endpoint to read and edit documentation with project tokens or anonymous read-only access. The platform requires PostgreSQL, storing uploaded media there by default or in optional S3-compatible storage. Local installation calls for Node.js 20+ and pnpm, plus Docker Compose or PostgreSQL 14+. The default upload maximum is 20 MB per upload. SMTP is optional, but without it password-reset and invitation links appear in server logs. The self-hosting guide recommends HTTPS, database backups, and production configuration.

VitePress turns Markdown content into themed static HTML pages for technical documentation and other content-focused sites. Its default theme targets documentation, while blogs, portfolios, and marketing sites are also supported. Markdown features include frontmatter, tables, syntax highlighting, and advanced code block options; pages can also use Vue templates, imported components, and in-page logic. The Vite-powered development server reflects edits in under 100 ms without a page reload. Production builds pre-render static HTML in Node.js, then use client-side routing for later navigation. Custom themes, Vite plugins, build-time data loading, and dynamically generated routes are available. Installation uses npm, pnpm, yarn, bun, or deno, with a command-line setup wizard. The project is free under the MIT License. Getting started requires Node.js version 22 or higher, and custom theme code must be compatible with server-side rendering. Deployment instructions cover a range of hosts, including Netlify, Vercel, GitHub Pages, Azure, and Firebase.