@sveltia/cms 0.60.1 → 0.60.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.
- package/README.md +5 -5
- package/dist/sveltia-cms.js +72 -82
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +77 -87
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -328,9 +328,9 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
328
328
|
- The Preview Pane comes with a minimal default style.[^168] It looks nice without a custom preview style or template.
|
|
329
329
|
- For better performance, the Preview Pane doesn’t use an `<iframe>`.[^179]
|
|
330
330
|
- The Preview Pane displays all fields, including each label, making it easier to see which fields are populated.
|
|
331
|
-
-
|
|
331
|
+
- Clicking a field in the Preview Pane focuses the corresponding field in the Edit Pane.[^41] It automatically expands when collapsed. This is equivalent to the misleading visual editing feature introduced in [Decap 3.6.0](https://github.com/decaporg/decap-cms/releases/tag/decap-cms%403.6.0), but it’s enabled by default; you don’t need to opt in with the `editor.visualEditing` collection option.
|
|
332
332
|
- The Preview Pane doesn’t cause a scrolling issue.[^136]
|
|
333
|
-
- The Preview Pane doesn’t
|
|
333
|
+
- The Preview Pane doesn’t crash with a Minified React error.[^186]
|
|
334
334
|
- Provides better scroll synchronization between the panes when editing or previewing an entry.[^92]
|
|
335
335
|
- Developers can hide the preview of a specific field using a new field option: `preview: false`.[^126]
|
|
336
336
|
- [See below](#better-widgets) for widget-specific enhancements, including support for variable types[^42] and YouTube videos.
|
|
@@ -493,7 +493,7 @@ However, 100% feature parity is not planned, and some features are still missing
|
|
|
493
493
|
### Features not to be implemented
|
|
494
494
|
|
|
495
495
|
- **The Bitbucket, Gitea/Forgejo and Git Gateway backends will not be supported** for performance reasons. [Git Gateway](https://github.com/netlify/git-gateway) has not been actively maintained since Netlify CMS was abandoned, and it’s known to be slow and prone to rate limit violations. We plan to develop a GraphQL-based high-performance alternative in the future. We may also support the other platforms if their APIs improve to allow the CMS to fetch multiple entries at once.
|
|
496
|
-
- **Netlify Identity Widget will not be supported**, as it’s not useful without Git Gateway
|
|
496
|
+
- **Netlify Identity Widget will not be supported**, as it’s not useful without Git Gateway, and Netlify Identity itself is now [officially deprecated](https://www.netlify.com/changelog/deprecation-netlify-identity/). We plan to develop an alternative solution with role support in the future, most likely using [Cloudflare Workers](https://workers.cloudflare.com/) and [Auth.js](https://authjs.dev/).
|
|
497
497
|
- The deprecated client-side implicit grant for the GitLab backend will not be supported, as it has already been [removed from GitLab 15.0](https://gitlab.com/gitlab-org/gitlab/-/issues/344609). Use the client-side PKCE authorization instead.
|
|
498
498
|
- The deprecated Netlify Large Media service will not be supported. Consider other storage providers.
|
|
499
499
|
- The deprecated Date widget will not be supported, as it has already been removed from Decap CMS 3.0. Use the DateTime widget with the `time_format: false` option instead.
|
|
@@ -606,7 +606,7 @@ Sveltia CMS does not support the Git Gateway backend due to performance limitati
|
|
|
606
606
|
|
|
607
607
|
To allow multiple users to edit content, simply invite people to your GitHub repository with the write role assigned.
|
|
608
608
|
|
|
609
|
-
Once you have migrated from the Git Gateway and Netlify Identity combo, you can remove the Netlify Identity
|
|
609
|
+
Once you have migrated from the Git Gateway and Netlify Identity combo, you can remove the Netlify Identity Widget script tag from your HTML:
|
|
610
610
|
|
|
611
611
|
```diff
|
|
612
612
|
-<script src="https://identity.netlify.com/v1/netlify-identity-widget.js"></script>
|
|
@@ -1355,7 +1355,7 @@ This software is provided “as is” without any express or implied warranty. W
|
|
|
1355
1355
|
|
|
1356
1356
|
[^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)
|
|
1357
1357
|
|
|
1358
|
-
[^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), [#7342](https://github.com/decaporg/decap-cms/issues/7342), [#7348](https://github.com/decaporg/decap-cms/issues/7348), [#7354](https://github.com/decaporg/decap-cms/issues/7354), [#7376](https://github.com/decaporg/decap-cms/issues/7376), [#7408](https://github.com/decaporg/decap-cms/issues/7408) — These `removeChild` crashes are common in React apps, likely caused by a [browser extension](https://github.com/facebook/react/issues/17256) or [Google Translate](https://github.com/facebook/react/issues/11538).
|
|
1358
|
+
[^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), [#7342](https://github.com/decaporg/decap-cms/issues/7342), [#7348](https://github.com/decaporg/decap-cms/issues/7348), [#7354](https://github.com/decaporg/decap-cms/issues/7354), [#7376](https://github.com/decaporg/decap-cms/issues/7376), [#7408](https://github.com/decaporg/decap-cms/issues/7408), [#7422](https://github.com/decaporg/decap-cms/issues/7422) — These `removeChild` crashes are common in React apps, likely caused by a [browser extension](https://github.com/facebook/react/issues/17256) or [Google Translate](https://github.com/facebook/react/issues/11538).
|
|
1359
1359
|
|
|
1360
1360
|
[^114]: Netlify/Decap CMS [#5029](https://github.com/decaporg/decap-cms/issues/5029), [#5048](https://github.com/decaporg/decap-cms/issues/5048)
|
|
1361
1361
|
|