Sveltia CMS reaches feature parity with Netlify and Decap CMS

A compatibility milestone

Sveltia CMS, an open-source Git-based content management system, has reached feature parity with Netlify CMS and its successor Decap CMS. According to a post on dev.to by a contributor to the project, every feature from Netlify and Decap now exists in Sveltia, with the exception of a small set that was intentionally dropped because it is deprecated or no longer makes sense. The milestone was originally announced in a discussion on the project's GitHub repository.

The last missing pieces — editorial workflow, open authoring, deploy previews and nested collections — shipped over the preceding weeks. These were the more complex collaboration features that had kept some Decap installations from moving over. On top of that, volunteer translators have localized the editor interface into more than 25 languages.

From Netlify to Decap to Sveltia

Some background on why a replacement was needed. Netlify CMS was a widely adopted open-source CMS where content lives as plain files in a Git repository, while editors work through a conventional forms-and-editor interface rather than touching code. Netlify eventually abandoned the project, and the community revived it as Decap CMS. But according to the dev.to post, development under the new name also slowed, and long-standing bugs went untouched for years.

Sveltia CMS was created by developer Kyoshino with two stated aims: stay close enough to Netlify and Decap that switching requires minimal effort, and work through the backlog of issues those projects never fixed. The first aim is now considered complete.

Adoption signals

The project's showcase lists more than 530 sites running Sveltia, of which over 160 migrated from Netlify or Decap CMS. The author reports that in most cases Sveltia works as a drop-in replacement, and characterizes it as faster, more secure and more reliable than what it replaces — though these claims come from someone inside the project rather than an independent evaluation. One harder number backs the growth story: Sveltia now records more weekly npm downloads than Decap CMS.

What comes next

With compatibility settled, the roadmap turns to the second goal: clearing the inherited issue backlog. The post states that 335 or more bugs reported against Netlify or Decap CMS have already been resolved in Sveltia, rising to 765 or more when duplicates are counted. The stated targets are 350 resolved issues (800 with duplicates) for the v1.0 release, and 450 (1,000 with duplicates) as a long-term goal.

The project is free and maintained largely by a single person, funded through GitHub sponsorship. The contributor's ask to users is modest: sponsor if the software saves you or your clients time, and otherwise report issues, star the repository or simply tell other developers about it.

Why it matters

Decap CMS users have been stuck in an awkward position: dependent on a tool whose maintenance has visibly slowed. Sveltia offers them something the original project's revival could not sustain — an actively developed, feature-compatible alternative they can move to without retraining content teams or re-architecting their repositories. That matters most for agencies and site builders who hand projects to non-technical clients, since those clients need a stable editing interface indefinitely.

The story also illustrates a recurring pattern in open source: when a revival effort loses momentum, a compatible reimplementation with an engaged maintainer can absorb the user base entirely, as the npm download figures suggest is happening here.

One caveat worth noting: the details in this story come from a single post written by a project contributor. Teams running large Decap installations, particularly those using the recently shipped editorial workflow or nested collections features, should test their own configurations against Sveltia before committing to a migration.