Sveltia CMS
A free, modern drop-in replacement for Netlify/Decap CMS that lets non-technical editors manage a static site's content through a polished, translatable, git-based editor.
🔗 Visit Sveltia CMS
Description
If your website is built with a static site generator like Hugo, Jekyll, or Next.js, your content usually lives as Markdown or YAML files in a Git repository — great for developers, painful for anyone else who just wants to edit a blog post or update a page. Sveltia CMS solves that by giving non-technical editors a clean, form-based interface that reads and writes those same files through Git, with no separate database and no code required to make an edit.
Sveltia CMS is a full from-scratch reimplementation of the Netlify CMS / Decap CMS config format and API, built specifically to fix the long-standing UX and reliability issues in the original (which lost most of its maintenance momentum after Netlify stepped back from it). It adds first-class internationalization support for multi-language sites, a mobile-friendly responsive UI, dark mode, an improved digital asset/media manager with built-in stock photo search (Unsplash, Pixabay, Pexels), and is delivered as a lightweight, framework-agnostic single-page app served from a CDN. Because it speaks the same config schema as Decap CMS, migrating an existing site usually means swapping a script tag, not rewriting a config file. The project reports fixing over 315 issues inherited from Decap CMS and is under active, frequent development.
💬 Our review
The short version: if you're currently running Netlify CMS or Decap CMS and finding it clunky, slow to update, or missing basic things like decent i18n, Sveltia CMS is close to a strict upgrade — same config format, noticeably better execution, and it's free.
The real value here isn't a new idea, it's execution on an old one: Decap CMS solved 'let a non-developer edit a Jamstack site's Markdown' years ago but stalled on UX and maintenance after Netlify deprioritized it. Sveltia rebuilt the same concept with a modern frontend stack, fixed a long tail of usability bugs, and treats multi-language sites as a first-class case instead of an afterthought — a real gap for any site that isn't English-only. Being a compatible reimplementation (not a fork) also means the migration cost from Decap CMS is close to zero.
The honest limits: it's still fundamentally a Git-file editor, not a general CMS — there's no database, no built-in workflow engine beyond what the config format offers, and it only makes sense if your site already fits the Jamstack/static-generator model. For a WordPress-style dynamic site or a team that wants a hosted backend with real user roles and a REST API, something like Payload CMS is the better fit.
💰 Pricing
📊 Global score
🤖 AI-enriched data
Entièrement gratuit et open-source (MIT), aucun palier payant.
Pros
Compatible avec la config Decap/Netlify CMS existante — migration quasi immédiate
i18n de premier ordre, rare chez les CMS git-based concurrents
315+ correctifs de bugs hérités de Decap CMS, UI mobile-friendly, dark mode
Gratuit et open-source, aucune dépendance à un service tiers payant
Cons
Reste un éditeur de fichiers Git, pas un CMS avec base de données
Pertinent seulement pour des sites Jamstack/générateur statique existants
Pas de couche backend/API — pour ça il faut un framework comme Payload CMS