Roadmap
As the true successor to Netlify CMS, our goal is to address all relevant and fixable Netlify/Decap CMS issues over the course of this project. We also have lots of ideas to make Sveltia CMS a great product.
We cannot promise any specific release dates, but here is a rough roadmap for the next few years.
Upcoming Releases
v1.0
Due early 2026. This will be the first stable release of Sveltia CMS, suitable for production use in many scenarios. This release also solves 300 issues of Netlify/Decap CMS, including many highly requested features and important bug fixes.
- Enhanced compatibility with Netlify/Decap CMS
- Tackling some more Netlify/Decap CMS issues, including:
- PKCE for GitHub[1] — It’s not yet supported by GitHub, was planned for Q4 2025
- Amazon S3 and Cloudflare R2 media storage providers[2]
- Thorough CMS config validation[3]
- Entry pre-validation/normalization[4]
- Accessibility audit
- Localization
- Live demo site
See also the 1.0 RC and 1.0 milestones for a list of issues planned for v1.0.
v2.0
Due mid-2026. This release completes the core features of Sveltia CMS as a successor to Netlify/Decap CMS.
- Implementing a few deferred Netlify/Decap CMS features, including editorial workflow and nested collections, while addressing a number of bugs in their implementations
- They will probably first be included as beta features in v1.x releases
- Tackling even more Netlify/Decap CMS issues, including:
See also the 2.0 milestone.
v3.0
Due late 2026. This release provides an alternative to the deprecated Netlify Identity and Git Gateway services used by Netlify/Decap CMS.
- Sveltia CMS Additions: Edge functions for Cloudflare Workers and possibly other platforms that provide features that cannot be implemented client-side:
- User management (Netlify Identity alternative) with roles[8]
- Commits without a Git service account (Git Gateway alternative)
- More enhancements are planned for the future; see the TBD list below
- Contributor documentation
TBD
- Tackling most of the remaining Netlify/Decap CMS issues (some may be included in v2.0 or v3.0):
- Their top-voted features, including:
- MDX support[9]
- Preview Workflow[10]
- Tables in Markdown[11]
- Config editor[12]
- Theming[13]
- Reusable field groups[14]
- Offline support[15]
- Features to turn the CMS into a powerful NoSQL database management system (DBMS):
- Automatic asset file renaming with templates[21]
- and many more (100+ issues and discussions)
- Their top-voted features, including:
- Enhancements to Sveltia CMS Additions (some may be included in v3.0):
- Post locking[22] (like WordPress)
- Scheduled posts[23]
- Private configuration
- Credential management for service API keys, deploy hook URL, etc.
- Proxy for services that don’t support CORS:
- Content editor enhancements:
- Field navigator
- Sidebar
- View, compare and restore revisions (like WordPress)
- Reverse reference lists
- Validation errors
- Input UI improvements
- Slider input for number fields
- Custom color picker
- Custom date/time picker
- Image field enhancements:
- Camera input, screen capture, QR code generation, AI image generation, etc.
- Quick cropping and resizing
- Search enhancements:
- Customizable search fields[25]
- Advanced search options
- Fuzzy search
- Local repository workflow improvements: Git mode[26] and change detection
- Preact+HTM or Vue support for custom field types, editor components and preview templates[27]
- More integration options: stock photos, stock videos, cloud storage providers, translation services, maps, analytics tools, etc.
- More AI features for image generation, content writing, etc.
- Advanced digital asset management (DAM) features, including image editing and tagging[28]
- Marketplace for custom field types, etc.[29]
- Official starter templates for the most popular frameworks, including Astro, Eleventy and Hugo
- and so much more!
Non-Goals
- Serving 100% of the existing Netlify/Decap CMS user base. While we aim to support most use cases, some users may be unable to migrate to Sveltia CMS due to unsupported features or technical limitations. See the Compatibility section for details.
- Support for non-Git backends. Sveltia CMS is a Git-based headless CMS and will remain so to avoid feature creep and increased maintenance costs. We may support custom backends through an API in the future, but it’s not a priority right now.
- Framework-specific integrations, including a WYSIWYG editor and out-of-the-box live site preview. We will focus on framework-agnostic core features that are essential for succeeding Netlify/Decap CMS and modernizing the platform.
- Enterprise features. We want to keep Sveltia CMS simple and easy to use for small teams and individual developers.
- Monetization. We may offer an affordable cloud version in the future since self-hosting the CMS can be a hassle. However, we will not charge for the CMS itself. We want to keep it free and open source forever.