DocFW Comparison

English

日本語

English

日本語

Appearance

VitePress assessment ​

This page separates hands-on impressions of this sample from researched facts. The maintenance snapshot and linked sources were checked on 2026-07-11.

Bottom line ​

Hands-on impression ​

VitePress feels fast both while serving and while navigating this small site. For documentation that lives beside a product, its baseline is exceptionally low-friction; the deliberately richer bilingual and plugin-enabled sample here is still easy to reason about.

Researched facts ​

VitePress includes GitHub-style Alerts. The official getting-started wizard supports installing in an existing project, choosing a nested docs/ directory, creating one .vitepress/config baseline, and adding docs:dev, docs:build, and docs:preview scripts. A separate documentation repository is not required, and the default theme has documented customization paths.

Strengths ​

Hands-on impression ​

The default theme looks polished without a design pass, while CSS variables and theme extension points leave room to match a product. Markdown-first authoring, fast feedback, and a static deploy model make the common docs path pleasant.

Researched facts ​

Static generation, locale configuration, local search, alerts, and default theme configuration are VitePress/default-theme features. This sample goes beyond that baseline: its bilingual content, Mermaid renderer, filesystem sidebar, MathJax, footnotes, and Vue demo component intentionally add authored content or plugins.

Concerns and trade-offs ​

Hands-on impression ​

The richer sample has a clear cost: authors must keep two locale trees aligned and maintain each plugin boundary. It remains manageable here, but it is more than the wizard's minimal setup.

Researched facts ​

Initial visits receive prerendered static HTML, then VitePress hydrates it to a Vue SPA. Basic document text is therefore available without JavaScript, but search, theme controls, the Vue Counter, Mermaid, and client-side navigation need it. The documented mpa: true mode is explicitly experimental: it ships 0kb JavaScript by default, but drops SPA navigation and Vue event handlers unless client scripts are explicitly opted in. This sample does not enable it because it demonstrates interactivity and plugins.

Shared findings with Nextra ​

Shared hands-on impression (subjective): both default themes feel polished, and both expose useful customization paths.

Evidence from both samples: both frameworks prerender and then hydrate. Base text is present in HTML while enhancements use JavaScript, and English/Japanese parity is authored manually. Their ecosystem trade-offs differ: VitePress integrations such as Mermaid are third-party plugins, whereas Nextra inherits Next/React and static-export constraints.

Maintenance snapshot — 2026-07-11 ​

VitePress ​

Research indicates active development, not abandonment: npm's stable release is 1.6.4, published 2025-08-05; 2.0.0-alpha.1 was published 2025-01-22; and alpha.18, the latest prerelease, was published 2026-07-06. The repository history includes commits through 2026-07-10 and 2026 alpha releases. The roughly 1.5-year v2 prerelease and slow stable cadence are release-planning concerns, not evidence that the project is abandoned. This sample deliberately pins 2.0.0-alpha.18; its static build succeeds at this snapshot, but it remains a prerelease rather than the stable channel. VitePress v2's official runtime requirement names Node.js 22 or later. This repository instead forces the CLI onto Bun 1.3.14 and treats its successful static build as project-level compatibility evidence, not an upstream support declaration.

Mermaid integration ​

vitepress-plugin-mermaid is third-party, not VitePress core. Its latest npm package is 2.0.17 (published 2024-09-24), while its latest GitHub release/tag is V2.0.8 (2022-09-24) and the repository shows a latest commit on 2025-04-16. This npm/release-history divergence needs review. The plugin declares a VitePress 1 peer range, not v2, so it is unsupported with VitePress 2. This sample's alpha.18 static build is project test evidence, not an upstream compatibility declaration: lock, audit, and test upgrades. Old release metadata alone does not establish a vulnerability.

Maintenance assessment (opinion): I treat the npm/release-history divergence as a negative sign of inadequate release-management discipline. It makes it hard to be confident that ongoing maintenance is a priority, and leaves a realistic risk that the plugin could become effectively unmaintained without a clear signal. That uncertainty is a negative selection factor even though it does not prove the maintainer's intent or the package's security state.

Documentation ​

VitePress's official guides and references are broad, which is a strength. During the current v2 prerelease transition, use the documentation matching the installed version and verify important configuration changes in a build.

Decision guidance ​

Choose VitePress when a product repository needs a fast, static, polished documentation site with a very small baseline and Vue-friendly extension points. Keep the baseline simple when possible. Adopt this richer pattern only when bilingual ownership and plugin upgrade testing are funded; otherwise, avoid adding integrations merely because they are available.