Skip to content

Roadmap
What we're building next.

These are our plans, not promises: priorities change as people use vagejs and tell us what they need. Released work moves to the changelog. Want something that isn't here? Open an issue.

Recently released

Version 0.3 shipped image optimization, a crawlability check, menus from frontmatter, blog feeds and Markdown copies for AI tools. See the changelog.

Next

AVIF images, alongside today's WebP copies, once vagejs can build <picture> safely.
Audits that count optimized images, so page-weight budgets measure the files browsers really download.

Later

vage new page and vage new post, to start pages with the right frontmatter
Submitting your sitemap to Google Search Console from the command line
Netlify and Vercel deploys, and sites hosted in a subfolder (GitHub project pages)
An MCP server, so AI assistants can call check, build and links directly
Sites in several languages

Not planned

A visual admin screen. Your content stays in files you own; AI assistants and editors work on those files.
Server rendering. vagejs builds static sites. For apps with logins and live data, an application framework is a better fit (see vagejs vs Next.js).

Start with one command.
You'll have a site running in a minute.

npm create vagejs@latest my-site

Read the docs Use it with your AI assistant