@sveltia/cms 0.37.1 → 0.38.0
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 +14 -8
- package/dist/sveltia-cms.js +116 -116
- package/dist/sveltia-cms.mjs +116 -116
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -2,15 +2,15 @@
|
|
|
2
2
|
|
|
3
3
|
Sveltia CMS is a Git-based lightweight headless CMS under active development as a modern, quick replacement for Netlify CMS and Decap CMS. In some simple cases, migration is as easy as a single line of code change, although we are still working on improving compatibility. The free, open source, UX-focused alternative to Netlify/Decap CMS is now in public beta — with more features to come.
|
|
4
4
|
|
|
5
|
-
<br>
|
|
5
|
+
<br>
|
|
6
6
|
|
|
7
|
-
<br>
|
|
7
|
+
<br>
|
|
8
8
|
|
|
9
|
-
<br>
|
|
9
|
+
<br>
|
|
10
10
|
|
|
11
|
-
<br>
|
|
11
|
+
<br>
|
|
12
12
|
|
|
13
|
-
<br>
|
|
13
|
+
<br>
|
|
14
14
|
|
|
15
15
|
## Motivation
|
|
16
16
|
|
|
@@ -46,7 +46,7 @@ While we are fixing reported bugs as fast as we can, the overall progress may be
|
|
|
46
46
|
|
|
47
47
|
- Ensuring maximum [compatibility with existing versions of Netlify/Decap CMS](#compatibility)
|
|
48
48
|
- Tackling as many [issues reported to Netlify/Decap CMS](https://github.com/decaporg/decap-cms/issues) as possible
|
|
49
|
-
- So far,
|
|
49
|
+
- So far, 115+ of them (or 190+ including duplicates) have been effectively solved in Sveltia CMS
|
|
50
50
|
- Target: 125 issues by GA, 250 in a future release
|
|
51
51
|
- [Let us know](https://github.com/sveltia/sveltia-cms/issues/new) if you have any specific issues you’d like to see solved!
|
|
52
52
|
- Responding to user feedback
|
|
@@ -55,7 +55,7 @@ While we are fixing reported bugs as fast as we can, the overall progress may be
|
|
|
55
55
|
|
|
56
56
|
Sveltia CMS **version 1.0 is expected to ship by the end of 2024**. Check our [release notes](https://github.com/sveltia/sveltia-cms/releases) for updates. See also our [roadmap](#roadmap).
|
|
57
57
|
|
|
58
|
-
<br>
|
|
59
59
|
|
|
60
60
|
## Features
|
|
61
61
|
|
|
@@ -78,7 +78,7 @@ We are working hard to create a **significantly better alternative to Netlify CM
|
|
|
78
78
|
### Better performance
|
|
79
79
|
|
|
80
80
|
- Built completely from scratch with Svelte instead of forking React-based Netlify/Decap CMS. The app starts fast and stays fast. The compiled code is vanilla JavaScript — you can use it with any framework that can load static data files while building your website or application.
|
|
81
|
-
- Small footprint: The bundle size is less than
|
|
81
|
+
- Small footprint: The bundle size is less than 550 KB when minified and gzipped, which is much lighter than Netlify CMS (1.5 MB), Decap CMS (1.8 MB) and Static CMS (2.6 MB), even though we haven’t implemented some features yet[^57][^64].
|
|
82
82
|
- The ongoing [Svelte 5](https://svelte.dev/blog/svelte-5-release-candidate) upgrade is anticipated to deliver further performance improvements, including accelerated speed and even smaller bundle size (an estimated 100 KB reduction).
|
|
83
83
|
- Sveltia CMS is free of technical debt and [virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead).
|
|
84
84
|
- Uses the GraphQL API for GitHub and GitLab to quickly fetch content at once, so that entries and assets can be listed and searched instantly[^32][^65]. It also avoids the slowness and potential API rate limit violations caused by hundreds of requests with Relation widgets[^14].
|
|
@@ -182,6 +182,8 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
182
182
|
- You can set the maximum number of characters for an entry slug with the new `slug_length` collection option[^25].
|
|
183
183
|
- Entry listing
|
|
184
184
|
- A folder collection filter with a boolean value works as expected[^93].
|
|
185
|
+
- Hugo’s special `_index.md` files are ignored in a folder collection. You can still manage these files as part of a file collection if necessary[^120].
|
|
186
|
+
- If there was an error while parsing an entry file, such as duplicate front matter keys, it won’t show up as a blank entry, and a clear error message will be displayed in the browser console[^121].
|
|
185
187
|
- Sorting entries by a DateTime field works as expected[^110].
|
|
186
188
|
- Assets stored in a [per-collection media folder](#using-a-custom-media-folder-for-a-collection) can be displayed next to the entries.
|
|
187
189
|
- The New Entry button won’t appear when a developer accidentally sets the `create: true` option on a file collection because it’s useless[^89].
|
|
@@ -1029,3 +1031,7 @@ This software is provided “as is” without any express or implied warranty. W
|
|
|
1029
1031
|
[^118]: Netlify/Decap CMS [#7267](https://github.com/decaporg/decap-cms/issues/7267)
|
|
1030
1032
|
|
|
1031
1033
|
[^119]: Netlify/Decap CMS [#5640](https://github.com/decaporg/decap-cms/issues/5640)
|
|
1034
|
+
|
|
1035
|
+
[^120]: Netlify/Decap CMS [#2727](https://github.com/decaporg/decap-cms/issues/2727), [#4884](https://github.com/decaporg/decap-cms/issues/4884)
|
|
1036
|
+
|
|
1037
|
+
[^121]: Netlify/Decap CMS [#7262](https://github.com/decaporg/decap-cms/issues/7262)
|