@sveltia/cms 0.70.0 → 0.70.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 +14 -14
- package/dist/sveltia-cms.js +199 -199
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +199 -199
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -2,19 +2,19 @@
|
|
|
2
2
|
|
|
3
3
|
Sveltia CMS is a Git-based lightweight headless CMS under active development as a modern, powerful, 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.
|
|
4
4
|
|
|
5
|
-
The free, open source alternative to Netlify/Decap CMS is now in public beta, turbocharged with great UX, performance, i18n support and so many more enhancements.
|
|
5
|
+
The free, open source alternative/successor to Netlify/Decap CMS is now in public beta, turbocharged with great UX, performance, i18n support and so many more enhancements.
|
|
6
6
|
|
|
7
|
-
<br>
|
|
8
8
|
|
|
9
|
-
<br>
|
|
10
10
|
|
|
11
|
-
<br>
|
|
12
12
|
|
|
13
|
-
<br>
|
|
14
14
|
|
|
15
|
-
<br>
|
|
16
16
|
|
|
17
|
-
<br>
|
|
18
18
|
|
|
19
19
|
## Table of contents
|
|
20
20
|
|
|
@@ -118,7 +118,7 @@ While Sveltia CMS is specifically designed to replace legacy Netlify CMS instanc
|
|
|
118
118
|
|
|
119
119
|
## Development status
|
|
120
120
|
|
|
121
|
-
Sveltia CMS is currently in **beta** and version 1.0 (GA) is expected to ship in
|
|
121
|
+
Sveltia CMS is currently in **beta** and version 1.0 (GA) is expected to ship in Q3 2025. Check our [release notes](https://github.com/sveltia/sveltia-cms/releases) for updates. See also our [roadmap](#roadmap).
|
|
122
122
|
|
|
123
123
|
While we fix reported bugs as quickly as possible, usually within 24 hours, our overall progress may be slower than you think. The thing is, it’s not just a personal project of [@kyoshino](https://github.com/kyoshino), but also a complicated system that involves various kinds of activities that require considerable effort:
|
|
124
124
|
|
|
@@ -137,11 +137,11 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
|
|
|
137
137
|
- Responding to requests from the maintainer’s clients
|
|
138
138
|
- Making the code clean and maintainable
|
|
139
139
|
|
|
140
|
-
<br>
|
|
141
141
|
|
|
142
142
|
## Differentiators
|
|
143
143
|
|
|
144
|
-
|
|
144
|
+
Netlify/Decap CMS users will definitely be pleased and surprised by the numerous improvements we have made, from the small to the large. Here’s what makes Sveltia CMS different. Look how serious we are!
|
|
145
145
|
|
|
146
146
|
### Better UX
|
|
147
147
|
|
|
@@ -150,7 +150,7 @@ We hope Netlify/Decap CMS users will be pleased and surprised by the numerous im
|
|
|
150
150
|
- Frequent releases deliver new features and enhancements to users faster. Most 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.
|
|
151
151
|
- Offers a modern, intuitive user interface that utilizes the full viewport,[^178] inspired in part by the Netlify CMS v3 prototype.[^1]
|
|
152
152
|
- Provides immersive dark mode.[^2] The UI theme follows the user’s system preference by default and can be changed in the application settings.
|
|
153
|
-
-
|
|
153
|
+
- Users can manage content on-the-go with decent mobile support.[^18] There are still rough edges though; we are working to fully optimize the app for small screens and touch devices.
|
|
154
154
|
- Made with [Svelte](https://svelte.dev/), not React, means we can spend more time on UX rather than tedious state management. It also allows us to avoid common fatal React application crashes.[^113][^129] Best of all, Svelte offers great performance.
|
|
155
155
|
- We build [our own UI component library](https://github.com/sveltia/sveltia-ui), including custom dialogs,[^196] to ensure optimal usability without compromising accessibility.
|
|
156
156
|
- The in-app Help menu provides all links to useful resources, including release notes, feedback and support.
|
|
@@ -159,14 +159,14 @@ We hope Netlify/Decap CMS users will be pleased and surprised by the numerous im
|
|
|
159
159
|
|
|
160
160
|
### Better performance
|
|
161
161
|
|
|
162
|
-
- Built completely from scratch with [Svelte](https://svelte.dev/) instead of forking React-based Netlify/Decap CMS. The app starts fast and stays fast with [no virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead).
|
|
162
|
+
- Built completely from scratch with [Svelte](https://svelte.dev/) instead of forking React-based Netlify/Decap CMS. The app starts fast and stays fast with [no virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead). Note that Sveltia CMS is framework-agnostic; it’s served as a vanilla JavaScript bundle.
|
|
163
163
|
- Small footprint: The bundle size is less than 500 KB when minified and [brotlied](https://en.wikipedia.org/wiki/Brotli), which is much lighter than Netlify CMS (1.5 MB), Decap CMS (1.5 MB) and Static CMS (2.6 MB).[^57][^64] This number is remarkable because even though some Netlify/Decap CMS features are [omitted](#features-not-to-be-implemented) or [unimplemented](#current-limitations) in Sveltia CMS, we have added a lot of new features. That’s the power of [Svelte 5](https://svelte.dev/blog/svelte-5-is-alive) + [Vite](https://vite.dev/).
|
|
164
164
|
- 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] (the useless `search` configuration option is therefore ignored). It also avoids the slowness and potential API rate limit violations caused by hundreds of requests with Relation widgets.[^14]
|
|
165
165
|
- 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/).
|
|
166
166
|
- Our [local repository workflow](#working-with-a-local-git-repository) utilizes the modern [File System Access API](https://developer.chrome.com/docs/capabilities/web-apis/file-system-access) to read and write files natively through the web browser, rather than using a slow, ad hoc REST API through a proxy server.
|
|
167
167
|
- Sorting, filtering and grouping of entries is done instantly without reloading the entire content.
|
|
168
168
|
- Uses caching, lazy loading and infinite scrolling techniques. A list of repository files is stored locally for faster startup and bandwidth savings.
|
|
169
|
-
- 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]
|
|
169
|
+
- 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][^38]
|
|
170
170
|
- No typing lag on input widgets, especially within nested lists and objects.[^77]
|
|
171
171
|
|
|
172
172
|
### Better productivity
|
|
@@ -482,7 +482,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
482
482
|
- View asset details, including size, dimensions, commit author/date and a list of entries that use the selected asset.
|
|
483
483
|
- Enhancements to media libraries:
|
|
484
484
|
- Supports multiple media libraries with the [new `media_libraries` option](#configuring-multiple-media-libraries).[^195]
|
|
485
|
-
- Integrates stock photo providers, including Pexels, Pixabay and Unsplash.
|
|
485
|
+
- Integrates stock photo providers, including Pexels, Pixabay and Unsplash.[^8]
|
|
486
486
|
- Default media library
|
|
487
487
|
- It comes with a [built-in image optimizer](#optimizing-images-for-upload). With a few lines of configuration, images selected by users for upload are automatically converted to WebP format for reduced size,[^199] and it’s also possible to specify a maximum width and/or height.[^200] SVG images can also be optimized.
|
|
488
488
|
- The `max_file_size` option for the File/Image widget can be defined within the global `media_library` option, using `default` as the library name. It applies to all File/Image entry fields, as well as direct uploads to the Asset Library. The option can also be part of the [new `media_libraries` option](#configuring-multiple-media-libraries).
|