Valaxy is an MIT-licensed static blog framework built on Vue 3 and Vite that turns Markdown files into a fast, file-based blog site, aimed at writers and developers who want to own their publishing stack rather than rent a hosted platform.
What it is
Valaxy is a static site generator for blogs, written in TypeScript and built on Vue 3, Vite 8, pnpm and Rolldown. Content lives as Markdown with extended frontmatter, routes are derived from the file tree through vue-router's file-based routing, and the built-in Valaxy SSG engine renders the result as static pages while still permitting a single-page-app mode. Configuration is centralised in a typed valaxy.config.ts, so editors and IDEs can surface tooltips for every option instead of leaving authors to consult documentation for each key.
The concrete problem it solves is the gap between a general-purpose site generator and a blog. In the Vue ecosystem, the project positions itself explicitly as a Hexo alternative: where Hexo users assemble plugins and themes around a generator built for an earlier toolchain, Valaxy ships the blog concerns โ themes, RSS, sitemap, deployment configuration โ on top of a modern Vite pipeline that accepts any Vite plugin. Themes are extended through a layout system with automatic layout registration, and a separate valaxy-theme-starter repository exists for people building their own.
Key capabilities
- Hot reload covers both Markdown content and configuration changes, so edits to
valaxy.config.ts take effect without a restart.
- Static-site generation runs through the built-in Valaxy SSG engine, with SPA output also supported.
- RSS feed and sitemap generation are included rather than delegated to plugins.
- Styling is available through UnoCSS, including Tailwind CSS utilities and class-based icons drawn from any icon set.
- Themes can be extended via the layout system with automatic layout registration, and components are auto-imported through
unplugin-vue-components.
- AI-facing output is opt-in: Agent Skills install with
npx skills add YunYouJun/valaxy, a local read-only MCP server is enabled with mcp: true, and llms.enable produces llms.txt and Markdown output.
- Zero-config deployment targets are provided for Netlify via
netlify.toml and GitHub Pages via .github/workflows/gh-pages.yml, and PWA support can be added with vite-plugin-pwa.
Who uses it and how
- Individual writers run a personal blog from a local Markdown repository and publish the generated static files, as the
demo/yun folder and the yun.valaxy.site demo illustrate.
- Theme authors start from
valaxy-theme-starter and distribute themes that hook into the layout registration system; the official Press theme has its own documentation and preview site.
- Developers who want to try the framework without a local toolchain can open the project in StackBlitz and run it in the browser.
- Teams deploying to Netlify or GitHub Pages can rely on the committed configuration files instead of writing a build pipeline.
- Multilingual authors can use the CSS i18n approach documented as "CSS i18n in One Page" to serve content across locales.
Getting started
Scaffold a blog locally with pnpm create valaxy (recommended), or the equivalent npm init valaxy and yarn create valaxy commands; an online StackBlitz template is also available for trying it without installing anything.
How it compares
Among the tools named in its own materials, Valaxy sits closest to Hexo, whose topic tag it adopts as hexo-alternative, but it targets the Vue 3 and Vite toolchain rather than the older generator model. Its implementation draws on VitePress, Vitesse and Slidev, so it inherits conventions familiar to people who have built documentation or slide decks in the Vue ecosystem while adding blog-specific output such as RSS and sitemaps.
When to use it โ and when not to
Choose Valaxy if the site is a blog, the content is Markdown in a repository, and the toolchain should be Vue 3 and Vite with static hosting on Netlify or GitHub Pages. A self-hoster must operate a Node and pnpm build environment and a static host, and must accept that there is no database, admin interface or server-side content API โ publishing means committing files and rebuilding. Anyone who needs a browser-based editor, multi-user editorial workflow or dynamic server rendering should look elsewhere, and the AI features only apply if mcp: true or llms.enable are deliberately switched on.
