@sveltia/cms 0.34.8 → 0.35.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 CHANGED
@@ -23,12 +23,12 @@ To achieve radical improvements in UX, performance, i18n and other areas, it was
23
23
  Due to its unfortunate abandonment, Netlify CMS spawned 3 successors:
24
24
 
25
25
  - [Static CMS](https://github.com/StaticJsCMS/static-cms): a community maintenance fork, first appeared on GitHub in September 2022
26
- - Sveltia CMS: a total reboot, started in November 2022, first appeared on GitHub in March 2023
26
+ - **Sveltia CMS**: a total reboot, started in November 2022, first appeared on GitHub in March 2023
27
27
  - [Decap CMS](https://github.com/decaporg/decap-cms): a rebranded version, owned by a Netlify agency partner, [announced in February 2023](https://www.netlify.com/blog/netlify-cms-to-become-decap-cms/) as the official successor
28
28
 
29
29
  Sveltia CMS is the only project that doesn’t inherit the complexity, technical debt and miscellaneous bugs of Netlify CMS, which was launched back in 2016. We are confident that our decision to rebuild the application from scratch was the right one, as proven by the hundreds of improvements we have already made.
30
30
 
31
- While Sveltia CMS is specifically designed to replace Netlify CMS, it also aims to serve as a substitute for the other products that are not receiving active development. (Note: Static CMS compatibility will be worked on after the Sveltia CMS 1.0 release)
31
+ While Sveltia CMS is specifically designed to replace legacy Netlify CMS instances, it also aims to serve as a substitute for the other products that are not receiving substantial updates. (Note: Static CMS compatibility will be worked on after the Sveltia CMS 1.0 release)
32
32
 
33
33
  ### Our goals
34
34
 
@@ -42,19 +42,19 @@ While Sveltia CMS is specifically designed to replace Netlify CMS, it also aims
42
42
 
43
43
  Sveltia CMS is **still in beta**, so please be careful when trying it out.
44
44
 
45
- While we are fixing reported bugs as fast as we can, usually within 24 hours, the 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 involves different kinds of activities:
45
+ While we are fixing reported bugs as fast as we can, the 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 involves different kinds of activities:
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, 100+ of them (or 180+ including duplicates) have been effectively solved in Sveltia CMS
50
- - Target: 150 issues by GA, 250 in a later release
49
+ - So far, 110+ of them (or 180+ including duplicates) have been effectively solved in Sveltia CMS
50
+ - Target: 150 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
53
53
  - Implementing our own UX enhancement ideas
54
54
 
55
55
  Sveltia CMS **version 1.0 is expected to ship in Q3 2024**. Check our [release notes](https://github.com/sveltia/sveltia-cms/releases) for updates. See also our [roadmap](#roadmap).
56
56
 
57
- ![100+ Netlify/Decap CMS Issues Solved in Sveltia CMS](docs/headline-1-20240527.webp)<br>
57
+ ![110+ Netlify/Decap CMS Issues Solved in Sveltia CMS](docs/headline-1-20240623.webp)<br>
58
58
 
59
59
  ## Features
60
60
 
@@ -132,6 +132,8 @@ We are working hard to create a **significantly better alternative to Netlify CM
132
132
  - The GitLab backend support comes with background [service status](https://status.gitlab.com/) checking, just like GitHub.
133
133
  - Service status checks are performed frequently and an incident notification is displayed prominently.
134
134
  - 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.
135
+ - You won’t get a 404 Not Found error when you sign in to the GitLab backend[^115].
136
+ - You can select the local and remote backends while working on a local server.
135
137
 
136
138
  ### Better i18n support
137
139
 
@@ -253,7 +255,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
253
255
  - Integration with Pexels, Pixabay and Unsplash makes it easy to select and insert a free stock photo[^8]. More stock photo providers will be added in the future.
254
256
  - Large images automatically fit in the preview pane instead of being displayed at their original size, which can easily exceed the width of the pane.
255
257
  - List and Object
256
- - The `summary` is displayed correctly when it refers to a Relation field[^36].
258
+ - The `summary` is displayed correctly when it refers to a Relation field[^36] or a simple List field.
257
259
  - Markdown, String and Text
258
260
  - A required field containing only spaces or line breaks will result in a validation error, as if no characters were entered.
259
261
  - Relation and Select
@@ -266,6 +268,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
266
268
 
267
269
  - Compute
268
270
  - The experimental `compute` widget allows to reference the value of other fields in the same collection, similar to the `summary` property for the List and Object widgets[^104]. Use the `value` property to define the value template, e.g. `posts-{{fields.slug}}` ([example](https://github.com/sveltia/sveltia-cms/issues/111)).
271
+ - The `value` property also supports `{{index}}`, which can hold the index of a list item ([example](https://github.com/sveltia/sveltia-cms/issues/172)).
269
272
  - UUID
270
273
  - In addition to [generating UUIDs for entry slugs](#using-a-random-id-for-an-entry-slug), Sveltia CMS also supports the proposed `uuid` widget with the following properties[^12]:
271
274
  - `prefix`: A string to be prepended to the value. Default: an empty string.
@@ -329,7 +332,7 @@ Missing any other features? Let us know by [filing an issue](https://github.com/
329
332
  - The deprecated Netlify Large Media service will not be supported. Consider other storage providers.
330
333
  - Sveltia CMS has dropped the support for the deprecated Date widget following Decap CMS 3.0. Use the DateTime widget instead.
331
334
  - Remark plugins will not be supported, as they are not compatible with our Lexical-based rich text editor.
332
- - Undocumented [methods available on the `window.CMS` object](https://github.com/sveltia/sveltia-cms/blob/b7f62741e02dc390c63c03291f95b2ca315d811b/src/main.js#L3-L33) will not be implemented. This includes custom backends and custom media libraries, if any.
335
+ - [Undocumented methods](https://github.com/sveltia/sveltia-cms/blob/6b8a86174f9beb4acc4bddcaa3848f773c1b2e52/src/main.js#L13-L36) exposed on the `window.CMS` object will not be implemented. This includes custom backends and custom media libraries, if any.
333
336
 
334
337
  ## Roadmap
335
338
 
@@ -367,6 +370,7 @@ Here are some starter kits for popular frameworks created by community members.
367
370
 
368
371
  - [Eleventy starter template](https://github.com/danurbanowicz/eleventy-sveltia-cms-starter) by [@danurbanowicz](https://github.com/danurbanowicz)
369
372
  - [Hugo module](https://github.com/privatemaker/headless-cms) by [@privatemaker](https://github.com/privatemaker)
373
+ - [hugolify-sveltia-cms](https://github.com/Hugolify/hugolify-sveltia-cms/) by [@sebousan](https://github.com/sebousan)
370
374
  - Astro: [astro-sveltia-cms](https://github.com/majesticostudio/astro-sveltia-cms), [astro-starter](https://github.com/zankhq/astro-starter) and [astros](https://github.com/zankhq/astros) by [@zanhk](https://github.com/zanhk)
371
375
 
372
376
  Alternatively, you can probably use one of the [Netlify/Decap CMS templates](https://decapcms.org/docs/start-with-a-template/) and make a quick migration to Sveltia CMS.
@@ -926,7 +930,7 @@ This software is provided “as is” without any express or implied warranty. W
926
930
 
927
931
  [^72]: Netlify/Decap CMS [#7047](https://github.com/decaporg/decap-cms/issues/7047)
928
932
 
929
- [^73]: Netlify/Decap CMS [#6993](https://github.com/decaporg/decap-cms/issues/6993), [#7123](https://github.com/decaporg/decap-cms/issues/7123), [#7127](https://github.com/decaporg/decap-cms/issues/7127), [#7128](https://github.com/decaporg/decap-cms/issues/7128)
933
+ [^73]: Netlify/Decap CMS [#6993](https://github.com/decaporg/decap-cms/issues/6993), [#7123](https://github.com/decaporg/decap-cms/issues/7123), [#7127](https://github.com/decaporg/decap-cms/issues/7127), [#7128](https://github.com/decaporg/decap-cms/issues/7128), [#7237](https://github.com/decaporg/decap-cms/issues/7237)
930
934
 
931
935
  [^74]: Netlify/Decap CMS [#4209](https://github.com/decaporg/decap-cms/issues/4209)
932
936
 
@@ -1006,6 +1010,8 @@ This software is provided “as is” without any express or implied warranty. W
1006
1010
 
1007
1011
  [^112]: Netlify/Decap CMS [#5815](https://github.com/decaporg/decap-cms/issues/5815), [#6522](https://github.com/decaporg/decap-cms/issues/6522), [#6532](https://github.com/decaporg/decap-cms/issues/6532), [#6588](https://github.com/decaporg/decap-cms/issues/6588), [#6617](https://github.com/decaporg/decap-cms/issues/6617), [#6640](https://github.com/decaporg/decap-cms/issues/6640), [#6663](https://github.com/decaporg/decap-cms/issues/6663), [#6695](https://github.com/decaporg/decap-cms/issues/6695), [#6697](https://github.com/decaporg/decap-cms/issues/6697), [#6764](https://github.com/decaporg/decap-cms/issues/6764), [#6765](https://github.com/decaporg/decap-cms/issues/6765), [#6835](https://github.com/decaporg/decap-cms/issues/6835), [#6983](https://github.com/decaporg/decap-cms/issues/6983), [#7205](https://github.com/decaporg/decap-cms/issues/7205)
1008
1012
 
1009
- [^113]: Netlify/Decap CMS [#5656](https://github.com/decaporg/decap-cms/issues/5656), [#5837](https://github.com/decaporg/decap-cms/issues/5837), [#5972](https://github.com/decaporg/decap-cms/issues/5972), [#6476](https://github.com/decaporg/decap-cms/issues/6476), [#6516](https://github.com/decaporg/decap-cms/issues/6516), [#6930](https://github.com/decaporg/decap-cms/issues/6930), [#6965](https://github.com/decaporg/decap-cms/issues/6965), [#7080](https://github.com/decaporg/decap-cms/issues/7080), [#7105](https://github.com/decaporg/decap-cms/issues/7105), [#7106](https://github.com/decaporg/decap-cms/issues/7106), [#7119](https://github.com/decaporg/decap-cms/issues/7119), [#7176](https://github.com/decaporg/decap-cms/issues/7176), [#7194](https://github.com/decaporg/decap-cms/issues/7194) — These `removeChild` crashes are common in React apps and seem to be caused by a [browser extension](https://github.com/facebook/react/issues/17256) or [Google Translate](https://github.com/facebook/react/issues/11538).
1013
+ [^113]: Netlify/Decap CMS [#5656](https://github.com/decaporg/decap-cms/issues/5656), [#5837](https://github.com/decaporg/decap-cms/issues/5837), [#5972](https://github.com/decaporg/decap-cms/issues/5972), [#6476](https://github.com/decaporg/decap-cms/issues/6476), [#6516](https://github.com/decaporg/decap-cms/issues/6516), [#6930](https://github.com/decaporg/decap-cms/issues/6930), [#6965](https://github.com/decaporg/decap-cms/issues/6965), [#7080](https://github.com/decaporg/decap-cms/issues/7080), [#7105](https://github.com/decaporg/decap-cms/issues/7105), [#7106](https://github.com/decaporg/decap-cms/issues/7106), [#7119](https://github.com/decaporg/decap-cms/issues/7119), [#7176](https://github.com/decaporg/decap-cms/issues/7176), [#7194](https://github.com/decaporg/decap-cms/issues/7194), [#7244](https://github.com/decaporg/decap-cms/issues/7244) — These `removeChild` crashes are common in React apps and seem to be caused by a [browser extension](https://github.com/facebook/react/issues/17256) or [Google Translate](https://github.com/facebook/react/issues/11538).
1010
1014
 
1011
1015
  [^114]: Netlify/Decap CMS [#5029](https://github.com/decaporg/decap-cms/issues/5029), [#5048](https://github.com/decaporg/decap-cms/issues/5048)
1016
+
1017
+ [^115]: Netlify/Decap CMS [#7172](https://github.com/decaporg/decap-cms/issues/7172)