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.
Next: 0.3
- Image pipeline. Resize images, convert them to WebP and AVIF, and write
srcset so phones download smaller files. Width and height are already filled in today.
- Crawlability check. Extend
vage verify to fetch your site as the major search and AI crawlers, catch blocks and challenges from your host, test that http and www addresses redirect, and flag scripts your CDN injects.
- Navigation from frontmatter.
order and section fields that build sidebars, previous and next links, and breadcrumbs, with their structured data, automatically.
- Blog feeds. RSS and Atom feeds generated from your posts.
- Pages as Markdown. A Markdown copy of every page for AI tools, and
lastmod dates in the sitemap from your git history.
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).