@sveltia/cms 0.106.2 → 0.106.3

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.
Files changed (6) hide show
  1. package/README.md +7 -4
  2. package/dist/sveltia-cms.js +179 -179
  3. package/dist/sveltia-cms.js.map +1 -1
  4. package/dist/sveltia-cms.mjs +178 -178
  5. package/dist/sveltia-cms.mjs.map +1 -1
  6. package/package.json +1 -1
package/README.md CHANGED
@@ -2,7 +2,7 @@
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. While some features are still missing, we’ve already solved over 250 issues reported in the predecessor’s repository, from critical bugs to top feature requests.
4
4
 
5
- Built from the ground up, Sveltia CMS offers an excellent UX, DX, performance, security and internationalization (i18n) support. Our numerous enhancements across the board ensure smooth daily workflows. This free, open source alternative to Netlify/Decap CMS is now in public beta, with version 1.0 expected in late 2025.
5
+ Built from the ground up, Sveltia CMS offers excellent UX, DX, performance, security and internationalization (i18n) support. Our numerous enhancements across the board ensure smooth daily workflows. This free, open source alternative to Netlify/Decap CMS is now in public beta, with version 1.0 expected in late 2025.
6
6
 
7
7
  ![Git-based headless CMS made right](https://raw.githubusercontent.com/sveltia/sveltia-cms/main/docs/screenshot-1.webp?20250405)<br>
8
8
 
@@ -125,7 +125,7 @@ Due to its unfortunate abandonment in early 2022, Netlify CMS spawned 3 successo
125
125
  - Actively developed with frequent releases and numerous improvements
126
126
  - Solved more than 250 issues reported in the Netlify/Decap CMS repository
127
127
  - [Decap CMS](https://github.com/decaporg/decap-cms): a rebranded version
128
- - [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
128
+ - [Announced in February 2023](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/) as an official continuation with a Netlify agency partner taking ownership
129
129
  - Mostly low activity with occasional releases and a few minor improvements
130
130
  - A [XSS vulnerability](https://github.com/advisories/GHSA-xp8g-32qh-mv28), high severity dependency vulnerabilities, fatal crashes and many other bugs remain unaddressed
131
131
 
@@ -135,9 +135,9 @@ Sveltia CMS is the only project that doesn’t inherit the complexity, technical
135
135
  - We don’t reuse any part of the predecessor’s codebase
136
136
  - We incorporate i18n support into the core instead of adding it as an afterthought
137
137
  - We closely monitor and analyze the predecessor’s issue tracker
138
- - We have rethought and redesigned the entire user experience (UX) and developer experience (DX)
138
+ - We have rearchitected the entire user experience (UX) and developer experience (DX)
139
139
 
140
- This “total reboot” allows us to make [hundreds of improvements](#differentiators) without getting stuck in a legacy system, establishing Sveltia CMS as a **unparalleled successor** to Netlify CMS.
140
+ This “total reboot” allows us to implement [hundreds of improvements](#differentiators) without getting stuck in a legacy system, establishing Sveltia CMS as a **unparalleled successor** to Netlify CMS.
141
141
 
142
142
  As we continue to add more features, we hope that our product will eventually become an appearing headless CMS option for everyone, not just for existing Netlify/Decap CMS users.
143
143
 
@@ -284,6 +284,7 @@ The [GitHub](https://decapcms.org/docs/github-backend/), [GitLab](https://decapc
284
284
  - The Git branch name is automatically set to the repository’s default branch (`main`, `master` or whatever) if not specified in the configuration file, preventing data loading errors due to a hardcoded fallback to `master`.[^95][^27] If a branch name is specified, it works as expected.[^232]
285
285
  - It’s possible to [disable automatic deployments](#disabling-automatic-deployments) by default or on demand to save costs and resources associated with CI/CD and to publish multiple changes at once.[^24]
286
286
  - The GitLab backend support comes with background [service status](https://status.gitlab.com/) checking, just like GitHub.
287
+ - The GitLab backend properly supports authorization via the GraphQL API.[^290]
287
288
  - Service status checks are performed frequently and an incident notification is displayed prominently.
288
289
  - Users can quickly open the source file of an entry or asset in your repository via the 3-dot menu when Developer Mode is enabled.
289
290
  - We provide [our own OAuth client](https://github.com/sveltia/sveltia-cms-auth) for GitHub and GitLab.
@@ -2579,3 +2580,5 @@ This project would not have been possible without the open source Netlify CMS pr
2579
2580
  [^288]: Netlify/Decap CMS [#7015](https://github.com/decaporg/decap-cms/issues/7015)
2580
2581
 
2581
2582
  [^289]: Netlify/Decap CMS [#2183](https://github.com/decaporg/decap-cms/issues/2183)
2583
+
2584
+ [^290]: Netlify/Decap CMS [#7611](https://github.com/decaporg/decap-cms/issues/7611)