@sveltia/cms 0.39.18 → 0.40.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
@@ -12,6 +12,61 @@ Sveltia CMS is a Git-based lightweight headless CMS under active development as
12
12
 
13
13
  ![Screenshot: Works with Remote (GitHub, GitLab) and Local Repositories; Single Line Migration from Netlify/Decap CMS (depending on your current setup); Sveltia CMS](https://raw.githubusercontent.com/sveltia/sveltia-cms/main/docs/screenshot-5-20240507.webp)<br>
14
14
 
15
+ ## Table of contents
16
+
17
+ - [Motivation](#motivation)
18
+ - [Our advantage](#our-advantage)
19
+ - [Our goals](#our-goals)
20
+ - [Development status](#development-status)
21
+ - [Differentiators](#differentiators)
22
+ - [Better UX](#better-ux)
23
+ - [Better performance](#better-performance)
24
+ - [Better productivity](#better-productivity)
25
+ - [Better accessibility](#better-accessibility)
26
+ - [Better security](#better-security)
27
+ - [Better configuration](#better-configuration)
28
+ - [Better backend support](#better-backend-support)
29
+ - [Better i18n support](#better-i18n-support)
30
+ - [Better collections](#better-collections)
31
+ - [Better content editing](#better-content-editing)
32
+ - [Better data output](#better-data-output)
33
+ - [Better widgets](#better-widgets)
34
+ - [New widgets](#new-widgets)
35
+ - [Better asset management](#better-asset-management)
36
+ - [Compatibility](#compatibility)
37
+ - [Features not to be implemented](#features-not-to-be-implemented)
38
+ - [Current limitations](#current-limitations)
39
+ - [Roadmap](#roadmap)
40
+ - [Before the 1.0 release](#before-the-10-release)
41
+ - [After the 1.0 release](#after-the-10-release)
42
+ - [Getting started](#getting-started)
43
+ - [New users](#new-users)
44
+ - [Migration](#migration)
45
+ - [Installing with npm](#installing-with-npm)
46
+ - [Updates](#updates)
47
+ - [Tips \& tricks](#tips--tricks)
48
+ - [Providing a JSON configuration file](#providing-a-json-configuration-file)
49
+ - [Migrating from Git Gateway backend](#migrating-from-git-gateway-backend)
50
+ - [Moving your site from Netlify to another hosting service](#moving-your-site-from-netlify-to-another-hosting-service)
51
+ - [Working around authentication error](#working-around-authentication-error)
52
+ - [Working with a local Git repository](#working-with-a-local-git-repository)
53
+ - [Enabling local development in Brave](#enabling-local-development-in-brave)
54
+ - [Using a custom icon for a collection](#using-a-custom-icon-for-a-collection)
55
+ - [Adding dividers to the collection list](#adding-dividers-to-the-collection-list)
56
+ - [Using a custom media folder for a collection](#using-a-custom-media-folder-for-a-collection)
57
+ - [Using keyboard shortcuts](#using-keyboard-shortcuts)
58
+ - [Using DeepL to translate entry fields](#using-deepl-to-translate-entry-fields)
59
+ - [Localizing entry slugs](#localizing-entry-slugs)
60
+ - [Disabling non-default locale content](#disabling-non-default-locale-content)
61
+ - [Using a random ID for an entry slug](#using-a-random-id-for-an-entry-slug)
62
+ - [Disabling automatic deployments](#disabling-automatic-deployments)
63
+ - [Setting up Content Security Policy](#setting-up-content-security-policy)
64
+ - [Support \& feedback](#support--feedback)
65
+ - [Contributions](#contributions)
66
+ - [Related links](#related-links)
67
+ - [As seen on](#as-seen-on)
68
+ - [Disclaimer](#disclaimer)
69
+
15
70
  ## Motivation
16
71
 
17
72
  Sveltia CMS was born in November 2022, when the progress of Netlify CMS was stalled for more than six months. [@kyoshino](https://github.com/kyoshino)’s clients wanted to replace their Netlify CMS instances without much effort, mainly to get better internationalization (i18n) support.
@@ -56,23 +111,17 @@ Sveltia CMS **version 1.0 is expected to ship by the end of 2024**. Check our [r
56
111
 
57
112
  ![120 Netlify/Decap CMS Issues Solved in Sveltia CMS](https://raw.githubusercontent.com/sveltia/sveltia-cms/main/docs/headline-1-20240928.webp)<br>
58
113
 
59
- ## Features
114
+ ## Differentiators
60
115
 
61
116
  We are working hard to create a **significantly better alternative to Netlify CMS and Decap CMS** by improving everything. Here’s what makes Sveltia CMS different. Look how serious we are!
62
117
 
63
- ### Compatible with Netlify/Decap CMS
64
-
65
- - Ready to be used as a drop-in replacement for Netlify/Decap CMS _in some casual use case scenarios_ with a single line of code update.
66
- - Your existing [configuration file](https://decapcms.org/docs/configuration-options/) can be reused as is.
67
- - However, some features are still missing or will not be added, most notably Git Gateway and Netlify Identity. Look at the [compatibility info](#compatibility) below to see if you can migrate now or soon.
68
-
69
118
  ### Better UX
70
119
 
71
120
  - Created and maintained by an [experienced UX engineer](https://github.com/kyoshino) who loves code, design and marketing. You can expect constant improvements to the user experience (UX) and developer experience (DX) across the platform.
72
121
  - Offers a modern, intuitive user interface, including an immersive dark mode[^2], inspired in part by the Netlify CMS v3 prototype[^1].
73
122
  - Comes with touch device support, such as larger buttons for easier tapping. While the UI is not yet optimized for small screens, it should work well with large tablets like iPad Pro or Pixel Tablet. Mobile support and other optimizations such as swipe navigation are planned after the 1.0 release.
74
123
  - Made with Svelte, not React, means we can spend more time on UX rather than tedious state management. It also allows us to avoid common fatal application crashes[^113][^129]. Best of all, Svelte offers unmatched performance!
75
- - The Account menu contains relevant links, including release notes, feedback and help.
124
+ - The Help menu provides all links to useful resources, including release notes, feedback and support.
76
125
  - Users can customize the application with various settings.
77
126
  - Never miss out on the latest features and bug fixes by being notified when an update to the CMS is available[^31]. Then update to the latest version with a single click[^66].
78
127
  - The screenshots above are worth a thousand words, but read on to learn about many other improvements in detail.
@@ -270,6 +319,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
270
319
  - A new asset can be uploaded by dragging & dropping it into the dialog[^20].
271
320
  - A URL can also be entered in the dialog.
272
321
  - 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.
322
+ - You can also simply drag and drop a file onto a File/Image field to attach it without having to open the Select File dialog.
273
323
  - 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.
274
324
  - List and Object
275
325
  - The `summary` is displayed correctly when it refers to a Relation field[^36] or a simple List field.
@@ -315,7 +365,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
315
365
 
316
366
  ## Compatibility
317
367
 
318
- We are trying to make Sveltia CMS compatible with Netlify/Decap CMS where possible, so that more users can seamlessly switch to our modern, powerful, high performance alternative. However, some features will be omitted due to deprecations and other factors.
368
+ We are trying to make Sveltia CMS compatible with Netlify/Decap CMS where possible, so that more users can seamlessly switch to our modern, powerful, high performance alternative. It’s ready to be used as a drop-in replacement for Netlify/Decap CMS _in some casual use case scenarios_ with a [single line of code update](#migration). However, some features will be omitted due to deprecations and other factors. Look at the compatibility info below to see if you can migrate now or soon.
319
369
 
320
370
  ### Features not to be implemented
321
371
 
@@ -634,7 +684,7 @@ i18n:
634
684
 
635
685
  ### Disabling non-default locale content
636
686
 
637
- You can now disable output of content in selected non-default locales by adding the `save_all_locales` property to the top-level or per-collection `i18n` configuration. Then you’ll find “Disable (locale name)” in the three-dot menu in the top right corner of the content editor. This is useful if the translation isn’t ready yet, but you want to publish the default locale content first.
687
+ You can disable output of content in selected non-default locales by adding the `save_all_locales` property to the top-level or per-collection `i18n` configuration. Then you’ll find “Disable (locale name)” in the three-dot menu in the top right corner of the content editor. This is useful if the translation isn’t ready yet, but you want to publish the default locale content first.
638
688
 
639
689
  With the following configuration, you can disable the French and/or German translation while writing in English.
640
690
 
@@ -1044,7 +1094,7 @@ This software is provided “as is” without any express or implied warranty. W
1044
1094
 
1045
1095
  [^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)
1046
1096
 
1047
- [^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).
1097
+ [^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), [#7301](https://github.com/decaporg/decap-cms/issues/7301) — 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).
1048
1098
 
1049
1099
  [^114]: Netlify/Decap CMS [#5029](https://github.com/decaporg/decap-cms/issues/5029), [#5048](https://github.com/decaporg/decap-cms/issues/5048)
1050
1100