The roadmap below is not ordered and will be built around the core Versoly product roadmap. We welcome code contributions especially for new frameworks.
- GitHub Actions - This will allow customers to publish inside Versoly which will trigger a webhook to GitHub that will then run Versoly sync, git push and finally your hosting provider will push those changes to production.
- 3rd party integrations - Update integrations such as Google analytics, Hubspot and other analytics inside Versoly and sync to your repo.
- Named images - Currently images are exported as UUID, with named images they will be based on the name of the image, however caching will be an issue so need to create a robust solution.
- Collection schema sync - With code first headless CMSs such as Payload it would be possible to create collection schemas inside Versoly while prototyping and then sync that to your repo.
- CMS sync - For small websites it may make sense to keep everything inside Versoly and sync as JSON or YAML so meta frameworks like Astro can use it.
- Other frameworks
- Next.js - Exporting React components is possible, however to create SEO friendly pages would need to parse Versoly pages to the correct Next.js format.
- Tanstack Start
- Nuxt.js
- Statamic - It is possible to generate PHP from Versoly code using an AST similar to how Astro components/pages work.
- Eleventy
- Jekyll