@sveltia/cms 0.100.0 → 0.100.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -8
- package/dist/sveltia-cms.js +201 -200
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +204 -203
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
- package/schema/sveltia-cms.json +21 -16
- package/types/public.d.ts +4 -0
package/README.md
CHANGED
|
@@ -116,10 +116,10 @@ We loved the simple setup of Netlify CMS that turned a Git repository into a dat
|
|
|
116
116
|
Due to its unfortunate abandonment in early 2022, Netlify CMS spawned 3 successors:
|
|
117
117
|
|
|
118
118
|
- [Static CMS](https://github.com/StaticJsCMS/static-cms): a community fork, initial commit made in September 2022 — discontinued in September 2024 after making meaningful improvements
|
|
119
|
-
- **Sveltia CMS**: not a fork but a **complete rewrite
|
|
120
|
-
- [Decap CMS](https://github.com/decaporg/decap-cms): a rebranded version, [announced in February 2023](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/) as the official successor with a Netlify agency partner taking ownership — mostly stagnant, no significant
|
|
119
|
+
- **Sveltia CMS**: not a fork but a **complete rewrite**, started in November 2022, first appeared on GitHub in March 2023
|
|
120
|
+
- [Decap CMS](https://github.com/decaporg/decap-cms): a rebranded version, [announced in February 2023](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/) as the official successor with a Netlify agency partner taking ownership — mostly stagnant, no significant improvements made since then
|
|
121
121
|
|
|
122
|
-
Sveltia CMS is the only project that doesn’t inherit the complexity, technical debt, and numerous bugs of Netlify CMS, which was launched in 2015. Our product is better by design: We have rebuilt the app from the ground up using a [modern framework](https://svelte.dev/) while closely monitoring and analyzing the predecessor’s issue tracker. We don’t use any of their code. This allows us to make [hundreds of improvements](#differentiators) without getting stuck in an old system.
|
|
122
|
+
Sveltia CMS is the only project that doesn’t inherit the complexity, technical debt, and numerous bugs of Netlify CMS, which was launched in 2015. Our product is better by design: We have rebuilt the app from the ground up using a [modern framework](https://svelte.dev/) while closely monitoring and analyzing the predecessor’s issue tracker. We don’t use any of their code. This “total reboot” allows us to make [hundreds of improvements](#differentiators) without getting stuck in an old system.
|
|
123
123
|
|
|
124
124
|
While Sveltia CMS was created to replace legacy Netlify CMS instances, it can also be used as an alternative to other Netlify CMS successors. With its [solid i18n support](#better-i18n-support), we’re hoping our product will eventually be an appearing option for anyone looking for a free headless CMS.
|
|
125
125
|
|
|
@@ -166,7 +166,7 @@ Note: This lengthy section compares Sveltia CMS with both Netlify CMS and Decap
|
|
|
166
166
|
|
|
167
167
|
- Created and actively maintained by an [experienced UX engineer](https://github.com/kyoshino) who loves code, design, marketing and problem solving. You can expect constant improvements to the user experience (UX) and developer experience (DX) across the platform.
|
|
168
168
|
- The maintainer tries to respond to bug reports as quickly as possible. While there are no guarantees, the typical turnaround time for a bug fix is less than 24 hours.
|
|
169
|
-
- Frequent releases deliver new features and enhancements to users faster.
|
|
169
|
+
- Frequent releases deliver new features and enhancements to users faster. Many of our minor [releases](https://github.com/sveltia/sveltia-cms/releases) address one or more Netlify/Decap CMS issues, giving you even more reasons to switch from the legacy predecessor.
|
|
170
170
|
- Offers a modern, intuitive user interface that utilizes the full viewport,[^178] inspired in part by the Netlify CMS v3 prototype.[^1][^211][^212][^213][^214]
|
|
171
171
|
- Provides immersive dark mode.[^2] The UI theme follows the user’s system preference by default and can be changed in the application settings.
|
|
172
172
|
- Users can easily manage content on-the-go with mobile and tablet support.[^18][^215]
|
|
@@ -575,9 +575,8 @@ Sveltia CMS supports all the [built-in widgets](https://decapcms.org/docs/widget
|
|
|
575
575
|
|
|
576
576
|
### Better customization
|
|
577
577
|
|
|
578
|
-
- The application renders within the dimensions of a [custom mount element](https://decapcms.org/docs/custom-mounting/), if exists.[^109]
|
|
579
578
|
- A custom logo defined with the `logo_url` property is displayed on the global application header and the browser tab (favicon).[^134] A smaller logo is also correctly positioned on the authentication page.[^135]
|
|
580
|
-
-
|
|
579
|
+
- Developers can specify the URL to redirect users after logging out with the `logout_redirect_url` global option.[^283]
|
|
581
580
|
- Enhancements to [custom editor components](https://decapcms.org/docs/custom-widgets/#registereditorcomponent):
|
|
582
581
|
- `CMS.registerEditorComponent()` accepts a component definition with the `icon` property. Developers can specify a Material Symbols icon name just like [custom collection icons](#using-a-custom-icon-for-a-collection).
|
|
583
582
|
- The `fromBlock` function can be omitted if the `pattern` regex contains [named capturing groups](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Regular_expressions/Named_capturing_group) for the values.
|
|
@@ -585,7 +584,8 @@ Sveltia CMS supports all the [built-in widgets](https://decapcms.org/docs/widget
|
|
|
585
584
|
- Field validation works as expected.[^279]
|
|
586
585
|
- No error is raised in the browser console saying `Sent invalid data to remark`.[^280]
|
|
587
586
|
- No error is raised in the browser console saying `onValidate is not a function`.[^281]
|
|
588
|
-
-
|
|
587
|
+
- Async functions can be used for [custom parsers/formatters](https://decapcms.org/docs/custom-formatters/).[^149]
|
|
588
|
+
- The application renders within the dimensions of a [custom mount element](https://decapcms.org/docs/custom-mounting/), if exists.[^109]
|
|
589
589
|
|
|
590
590
|
### Better localization
|
|
591
591
|
|
|
@@ -1765,7 +1765,7 @@ Due early 2026
|
|
|
1765
1765
|
- [Preact+HTM support](https://github.com/sveltia/sveltia-cms/discussions/153) for custom widgets, editor components and preview templates
|
|
1766
1766
|
- View, compare and restore revisions (like [WordPress](https://wordpress.com/support/page-post-revisions/))
|
|
1767
1767
|
- More integration options: stock photos, stock videos, cloud storage providers, translation services, maps, analytics tools, etc.
|
|
1768
|
-
- AI
|
|
1768
|
+
- More AI features for image generation, content writing, etc.
|
|
1769
1769
|
- Search enhancements:
|
|
1770
1770
|
- Customizable search fields[^274]
|
|
1771
1771
|
- Advanced search options
|
|
@@ -1777,6 +1777,7 @@ Due early 2026
|
|
|
1777
1777
|
|
|
1778
1778
|
### Non-goals
|
|
1779
1779
|
|
|
1780
|
+
- 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.
|
|
1780
1781
|
- Framework-specific integrations, including a WYSIWYG editor. Due to the crowded CMS market and our limited resources, we will focus on framework-agnostic core features that are essential for succeeding Netlify/Decap CMS and modernizing the platform.
|
|
1781
1782
|
- 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.
|
|
1782
1783
|
|