@sveltia/cms 0.91.6 → 0.91.8

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
@@ -134,7 +134,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
134
134
 
135
135
  - Ensuring substantial [compatibility with Netlify/Decap CMS](#compatibility)
136
136
  - Tackling as many [Netlify/Decap CMS issues](https://github.com/decaporg/decap-cms/issues) as possible
137
- - So far, 235+ issues, or 485+ if including duplicates, have been effectively solved in Sveltia CMS (Yes, you read it right)
137
+ - So far, 235+ issues, or 4905 if including duplicates, have been effectively solved in Sveltia CMS (Yes, you read it right)
138
138
  - Target:
139
139
  - 250 issues, or 500 if including duplicates, by GA — Almost there!
140
140
  - 400 issues, or 800 if including duplicates, in the future 💪
@@ -167,7 +167,7 @@ Note: This lengthy section compares Sveltia CMS with both Netlify CMS and Decap
167
167
  - For a smoother experience, we even go beyond responsive design with optimized navigation, [view transitions](https://developer.chrome.com/docs/web-platform/view-transitions), larger buttons, and other tweaks. However, there are still rough edges, and we are working to fully optimize the app for small screens and touch devices.
168
168
  - If you’re already signed in on your desktop, open the Account menu in the top right corner of the CMS, click Sign In with Mobile, and scan the QR code for passwordless sign-in. Your settings will be automatically copied.
169
169
  - 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.
170
- - Other crashes in Netlify/Decap CMS are also irrelevant to us, making Sveltia CMS much more stable.[^112][^203][^204]
170
+ - Other crashes in Netlify/Decap CMS are also irrelevant to us, making Sveltia CMS much more stable.[^112][^203][^204][^260]
171
171
  - We build [our own UI component library](https://github.com/sveltia/sveltia-ui), including custom dialogs, to ensure optimal usability without compromising accessibility.[^196][^205][^206][^207][^208][^209][^210]
172
172
  - Users can personalize the application with various settings, including appearance and language. Developer Mode can also be enabled.
173
173
  - 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]
@@ -218,6 +218,7 @@ Note: This lengthy section compares Sveltia CMS with both Netlify CMS and Decap
218
218
 
219
219
  - Avoids vulnerabilities in dependencies through constant updates, Dependabot alerts, [`pnpm audit`](https://pnpm.io/cli/audit), and frequent releases, unlike Netlify/Decap CMS where a number of high severity vulnerabilities remain unpatched for a long time.[^33]
220
220
  - Our [local repository workflow](#working-with-a-local-git-repository) doesn’t require a proxy server, reducing an attack surface.[^158]
221
+ - Thanks to pnpm, Svelte, Vite and GitHub Actions, our release process is fast, reliable and transparent. It makes it easy to verify the integrity of published code and assets while avoiding errors that can occur with manual build steps.[^264]
221
222
  - We have enabled [npm package provenance](https://github.blog/security/supply-chain-security/introducing-npm-package-provenance/).
222
223
  - We have documented how to [set up a Content Security Policy](#setting-up-content-security-policy) for the CMS to prevent any unexpected errors or otherwise insecure configuration.[^108]
223
224
  - The `unsafe-eval` and `unsafe-inline` keywords are not needed in the `script-src` CSP directive.[^34]
@@ -1376,6 +1377,12 @@ body: This is the body of my post.
1376
1377
  ---
1377
1378
  ```
1378
1379
 
1380
+ If there is only the `body` field, the front matter block is omitted altogether:
1381
+
1382
+ ```yaml
1383
+ This is the body of my post.
1384
+ ```
1385
+
1379
1386
  However, this doesn’t apply when i18n is enabled with the `single_file` structure. In this case, the `body` field is saved part of key-value pairs under each locale in the front matter block:
1380
1387
 
1381
1388
  ```yaml
@@ -1615,14 +1622,13 @@ Due late 2025
1615
1622
  - Tackling some more Netlify/Decap CMS issues:
1616
1623
  - [Directory navigation in the Asset Library](https://github.com/sveltia/sveltia-cms/issues/420)[^240]
1617
1624
  - [Multiple file selection with the File and Image widgets](https://github.com/sveltia/sveltia-cms/issues/10)[^239]
1618
- - [Git LFS support for the GitHub backend](https://github.com/sveltia/sveltia-cms/discussions/353)[^244]
1619
- - Advanced Relation fields[^242], including cascade updates/deletes[^243] and [reverse reference lists](https://github.com/sveltia/sveltia-cms/discussions/416)
1625
+ - Advanced Relation fields[^242], including cascade updates/deletes[^243]
1626
+ - We’ll also implement [reverse reference lists](https://github.com/sveltia/sveltia-cms/discussions/416)
1620
1627
  - Several Cloudinary and Uploadcare media library issues, including selection of existing files[^247]
1621
1628
  - [Automatic asset file renaming with templates](https://github.com/sveltia/sveltia-cms/issues/422)[^241]
1622
1629
  - [RTL localization support](https://github.com/sveltia/sveltia-cms/issues/385)[^245]
1623
1630
  - Thorough site config validation[^246]
1624
1631
  - [Entry pre-validation/normalization](https://github.com/sveltia/sveltia-cms/issues/395)[^248]
1625
- - and a few more bugs
1626
1632
  - Migration from Moment.js to Day.js
1627
1633
  - Accessibility audit
1628
1634
  - [Localization](https://github.com/sveltia/sveltia-cms/blob/main/src/lib/locales/README.md)
@@ -1642,8 +1648,11 @@ Due early 2026
1642
1648
  - Tackling many of the remaining Netlify/Decap CMS issues, including:
1643
1649
  - MDX support[^122]
1644
1650
  - [Manual entry sorting](https://github.com/sveltia/sveltia-cms/issues/214)[^125]
1651
+ - [Saving drafts without editorial workflow](https://github.com/sveltia/sveltia-cms/discussions/440)[^261]
1645
1652
  - [Tables in Markdown](https://github.com/sveltia/sveltia-cms/issues/455)[^256]
1646
1653
  - [Config editor](https://github.com/sveltia/sveltia-cms/discussions/452)[^10]
1654
+ - [Theming](https://github.com/sveltia/sveltia-cms/issues/29)[^262]
1655
+ - [Reusable field groups](https://github.com/sveltia/sveltia-cms/discussions/463)[^263]
1647
1656
  - Offline support[^238]
1648
1657
  - and other [top-voted features](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc)
1649
1658
  - (some of them may be included in v2.0)
@@ -1653,6 +1662,7 @@ Due early 2026
1653
1662
  - Post locking (like [WordPress](https://codex.wordpress.org/Post_Locking))[^166]
1654
1663
  - Scheduled posts[^167]
1655
1664
  - Credential management for service API keys, deploy hook URL, etc.
1665
+ - [Git LFS support for GitHub](https://github.com/sveltia/sveltia-cms/discussions/353)[^244] (due to a [CORS issue](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS/Errors))
1656
1666
  - [Preact+HTM support](https://github.com/sveltia/sveltia-cms/discussions/153) for custom widgets, editor components and preview templates
1657
1667
  - View, compare and restore revisions (like [WordPress](https://wordpress.com/support/page-post-revisions/))
1658
1668
  - More integration options: stock photos, stock videos, cloud storage providers, translation services, maps, analytics tools, etc.
@@ -2199,3 +2209,13 @@ This software is provided “as is” without any express or implied warranty. W
2199
2209
  [^258]: Netlify/Decap CMS [#663](https://github.com/decaporg/decap-cms/issues/663), [#6729](https://github.com/decaporg/decap-cms/discussions/6729), [#7466](https://github.com/decaporg/decap-cms/discussions/7466), [#7545](https://github.com/decaporg/decap-cms/issues/7545)
2200
2210
 
2201
2211
  [^259]: Netlify/Decap CMS [#7546](https://github.com/decaporg/decap-cms/issues/7546)
2212
+
2213
+ [^260]: Netlify/Decap CMS [#5867](https://github.com/decaporg/decap-cms/issues/5867), [#6159](https://github.com/decaporg/decap-cms/issues/6159), [#7016](https://github.com/decaporg/decap-cms/issues/7016), [#7306](https://github.com/decaporg/decap-cms/issues/7306), [#7554](https://github.com/decaporg/decap-cms/issues/7554)
2214
+
2215
+ [^261]: Netlify/Decap CMS [#942](https://github.com/decaporg/decap-cms/issues/942)
2216
+
2217
+ [^262]: Netlify/Decap CMS [#1727](https://github.com/decaporg/decap-cms/issues/1727)
2218
+
2219
+ [^263]: Netlify/Decap CMS [#1342](https://github.com/decaporg/decap-cms/issues/1342)
2220
+
2221
+ [^264]: Netlify/Decap CMS [#7557](https://github.com/decaporg/decap-cms/issues/7557)