@sveltia/cms 0.39.17 → 0.39.18
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 +6 -3
- package/dist/sveltia-cms.js +270 -264
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +231 -225
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +5 -5
package/README.md
CHANGED
|
@@ -79,13 +79,14 @@ We are working hard to create a **significantly better alternative to Netlify CM
|
|
|
79
79
|
|
|
80
80
|
### Better performance
|
|
81
81
|
|
|
82
|
-
- 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 during the build process.
|
|
82
|
+
- 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 or static site generator (SSG) that can load static data files during the build process.
|
|
83
83
|
- Small footprint: The bundle size is less than 450 KB when minified and brotlied, which is much lighter than Netlify CMS (1.5 MB), Decap CMS (1.8 MB) and Static CMS (2.6 MB)[^57][^64], even though we haven’t implemented some features yet. That’s the power of Svelte + Vite.
|
|
84
|
-
- We have upgraded from Svelte 4 to [Svelte 5 Release Candidate](https://svelte.dev/blog/svelte-5-release-candidate) to further
|
|
84
|
+
- We have upgraded from Svelte 4 to [Svelte 5 Release Candidate](https://svelte.dev/blog/svelte-5-release-candidate) to further improve performance, including an even smaller bundle size. A full migration to the _runes_ reactivity API will follow.
|
|
85
85
|
- Sveltia CMS is free of technical debt and [virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead).
|
|
86
86
|
- 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].
|
|
87
87
|
- Saving entries and assets to GitHub is also much faster thanks to the [GraphQL mutation](https://github.blog/changelog/2021-09-13-a-simpler-api-for-authoring-commits/).
|
|
88
88
|
- Using caching and lazy loading techniques. A list of repository files is stored locally for faster startup and bandwidth savings.
|
|
89
|
+
- Sorting, filtering and grouping of entries is done instantly without reloading the entire content.
|
|
89
90
|
- Thumbnails of assets, including videos and PDF files, are generated and cached for faster rendering of the Asset Library and other parts of the CMS[^39].
|
|
90
91
|
- No typing lag on input widgets, especially within nested lists and objects[^77].
|
|
91
92
|
|
|
@@ -137,6 +138,7 @@ We are working hard to create a **significantly better alternative to Netlify CM
|
|
|
137
138
|
- The GitLab backend support comes with background [service status](https://status.gitlab.com/) checking, just like GitHub.
|
|
138
139
|
- Service status checks are performed frequently and an incident notification is displayed prominently.
|
|
139
140
|
- You can quickly open the source file of an entry or asset in your repository using View on GitHub (or GitLab) under the 3-dot menu.
|
|
141
|
+
- We provide [our own OAuth client](https://github.com/sveltia/sveltia-cms-auth) for GitHub and GitLab.
|
|
140
142
|
- You won’t get a 404 Not Found error when you sign in to the GitLab backend[^115].
|
|
141
143
|
- Features the all-new local backend that boosts DX. See the [productivity section](#better-productivity) above.
|
|
142
144
|
- You can select the local and remote backends while working on a local server.
|
|
@@ -184,6 +186,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
184
186
|
- Single quotes in a slug will be replaced with `sanitize_replacement` (default: hyphen) rather than being removed[^52].
|
|
185
187
|
- You can set the maximum number of characters for an entry slug with the new `slug_length` collection option[^25].
|
|
186
188
|
- Entry listing
|
|
189
|
+
- The collection list displays the number of items in each collection.
|
|
187
190
|
- A folder collection filter with a boolean value works as expected[^93].
|
|
188
191
|
- Hugo’s special `_index.md` files are ignored in folder collections unless the `path` option is configured to end with `_index` and the `extension` is `md`[^120]. You can still manage these files as part of a file collection if necessary.
|
|
189
192
|
- 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].
|
|
@@ -589,7 +592,7 @@ collections:
|
|
|
589
592
|
label: Blog posts
|
|
590
593
|
create: true
|
|
591
594
|
folder: data/posts/
|
|
592
|
-
slug: '{{title | localize}}'
|
|
595
|
+
slug: '{{title | localize}}' # This does the trick
|
|
593
596
|
format: yaml
|
|
594
597
|
i18n: true
|
|
595
598
|
fields:
|