# Roadmap

> What's planned for vagejs next, from AVIF images and page scaffolding to Netlify and Vercel deploys, an MCP server and multi-language sites.

These are our plans, not promises: priorities change as people use vagejs and tell us what they need. Released work moves to the [changelog](https://vagejs.com/changelog/). Want something that isn't here? [Open an issue](https://github.com/agevenkat/vagejs/issues).

## 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](https://vagejs.com/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](https://vagejs.com/compare/vagejs-vs-nextjs/)).