Can VitePress be used as a blog?
Yes, with caveats. VitePress can host a blog. Its own docs list blogs beside documentation, and point to the Vue.js blog as the example: a custom theme, and an index generated from local Markdown. The default theme is for technical documentation. A typical blog’s post list, tag pages, archives, RSS feed, and blog theme are not included, so you build and maintain them. Valaxy is a Vue blog framework that includes them. Hexo is a blog framework too: a site from hexo init includes the post index, tags, categories, archives, and a blog theme, and the feed is a separate official plugin. This page is qualitative. Hugo and Astro are in How to choose a static blog framework.
Valaxy was started when blogging was not yet a first-class VitePress use case. Compared with VitePress, it still ships more blog features out of the box, and more complete AI support for a blog: experimental Agent Skills, an opt-in MCP server, and llms.txt (Work with AI). VitePress 2.0 is still an alpha (releases). On 2026-11-05, npm latest is 1.6.4 and next is 2.0.0-alpha.21. That alpha line started with 2.0.0-alpha.1 on 2025-01-22.
TIP
Checked against the VitePress and Hexo docs, and the npm vitepress dist-tags, on 2026-11-05 (Asia/Shanghai). Qualitative only.
What a typical blog still has to add
| Need | VitePress | Valaxy | Hexo |
|---|---|---|---|
| Post list | A custom index, as on the Vue.js blog | From pages/posts | Included in hexo init |
| Tags and categories | Custom pages | Tag and category layouts | Included in hexo init |
| Archives | A custom page | Archives layout | Included in hexo init |
| RSS | A feed you add | Built in, and on by default once url is set (RSS) | Official plugin hexo-generator-feed, not part of hexo init |
| Blog theme | The default theme is for docs. A blog uses a custom theme | Yun for a blog. Press when the same site should read as docs | Landscape ships with hexo init. The Chinese catalog is larger, and those themes do not run on Valaxy |
Valaxy keeps the date, tags, and categories in post front matter, and the theme renders the list. See Posts and Why Valaxy.
When to stay on VitePress
Stay when the site is a library or product manual. The default docs theme is the product, and a post list, tags, archives, and a feed are not. A standalone manual stays on VitePress.
When to use Valaxy
Use Valaxy when those blog pieces are the product, or when you are leaving Hexo and can accept a new theme. Start with pnpm create valaxy and Yun. From Hexo, copy source/_posts to pages/posts and follow Migration.
Use Press for a docs-shaped site that still has Valaxy’s posts, tags, addons, and Vue component overrides. Press is inspired by VitePress. Configuration lives in valaxy.config.ts, site.config.ts, or theme.config.ts. See Migrating from VitePress.
Where Hexo still fits
Valaxy is for people who want to migrate from Hexo for a more modern development experience: Vite and Vue 3, hot reload, typed config, component overrides, SSG then SPA navigation, and the AI surface of Skills, MCP, and llms.txt (Work with AI), while keeping a familiar blog workflow (posts, tags, a theme, and a migration path). Stay on Hexo when an existing theme or plugin is the product. Why Valaxy and How to choose cover that trade-off.