@sveltia/cms 0.38.0 → 0.38.2

package/README.md

@@ -78,7 +78,7 @@ We are working hard to create a **significantly better alternative to Netlify CM
 ### Better performance
 
 - Built completely from scratch with Svelte instead of forking React-based Netlify/Decap CMS. The app starts fast and stays fast. The compiled code is vanilla JavaScript — you can use it with any framework that can load static data files while building your website or application.
-- Small footprint: The bundle size is less than 550 KB when minified and gzipped, which is much lighter than Netlify CMS (1.5 MB), Decap CMS (1.8 MB) and Static CMS (2.6 MB), even though we haven’t implemented some features yet[^57][^64].
+- Small footprint: The bundle size is less than 500 KB when minified and gzipped, which is much lighter than Netlify CMS (1.5 MB), Decap CMS (1.8 MB) and Static CMS (2.6 MB), even though we haven’t implemented some features yet[^57][^64].
 - The ongoing [Svelte 5](https://svelte.dev/blog/svelte-5-release-candidate) upgrade is anticipated to deliver further performance improvements, including accelerated speed and even smaller bundle size (an estimated 100 KB reduction).
 - Sveltia CMS is free of technical debt and [virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead).
 - Uses the GraphQL API for GitHub and GitLab to quickly fetch content at once, so that entries and assets can be listed and searched instantly[^32][^65]. It also avoids the slowness and potential API rate limit violations caused by hundreds of requests with Relation widgets[^14].
@@ -106,6 +106,7 @@ We are working hard to create a **significantly better alternative to Netlify CM
 
 - Improved keyboard handling lets you efficiently navigate through UI elements using the Tab, Space, Enter and arrow keys[^17][^67].
 - Comprehensive [WAI-ARIA](https://w3c.github.io/aria/) support enables users who rely on screen readers such as NVDA and VoiceOver.
+- The rich text editor is built with [Lexical](https://lexical.dev/), which is said to follow accessibility best practices. The [Dragon NaturallySpeaking support](https://lexical.dev/docs/packages/lexical-dragon) is enabled.
 - Ensures sufficient contrast between the foreground text and background colours.
 - Enabled and disabled buttons can be clearly distinguished[^105].
 - Links are underlined by default to make them easier to recognize. This behaviour can be changed in the Accessibility Settings if you prefer.
@@ -182,7 +183,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
   - You can set the maximum number of characters for an entry slug with the new `slug_length` collection option[^25].
 - Entry listing
   - A folder collection filter with a boolean value works as expected[^93].
-  - Hugo’s special `_index.md` files are ignored in a folder collection. You can still manage these files as part of a file collection if necessary[^120].
+  - Hugo’s special `_index.md` files are ignored in folder collections. You can still manage these files as part of a file collection if necessary[^120].
   - If there was an error while parsing an entry file, such as duplicate front matter keys, it won’t show up as a blank entry, and a clear error message will be displayed in the browser console[^121].
   - Sorting entries by a DateTime field works as expected[^110].
   - Assets stored in a [per-collection media folder](#using-a-custom-media-folder-for-a-collection) can be displayed next to the entries.
@@ -232,7 +233,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
   - You can enter spaces in a simple text-based List field[^50].
   - You can preview variable types without having to register a preview template[^42].
 - Markdown
-  - The rich text editor is built with [Lexical](https://github.com/facebook/lexical) instead of [Slate](https://github.com/ianstormtaylor/slate), which solves various problems found in Netlify/Decap CMS, including fatal application crashes[^53][^70][^71][^72][^73][^111].
+  - The rich text editor is built with [Lexical](https://lexical.dev/) instead of [Slate](https://github.com/ianstormtaylor/slate), which solves various problems found in Netlify/Decap CMS, including fatal application crashes[^53][^70][^71][^72][^73][^111].
   - You can set the default editor mode by changing the order of the `modes` option[^58]. If you want to use the plain text editor by default, add `modes: [raw, rich_text]` to the field configuration.
   - Line breaks are rendered as line breaks in the preview pane according to GitHub Flavored Markdown.
 - Object
@@ -347,24 +348,24 @@ Missing any other features? Let us know by [filing an issue](https://github.com/
 
 ### Before the 1.0 release
 
-- Enhanced [compatibility with Netlify/Decap CMS](#compatibility)
-- [Tackling more Netlify/Decap CMS issues](#development-status)
-- Broad automation test coverage (Vitest + Playwright)
 - [Svelte 5](https://svelte.dev/blog/svelte-5-release-candidate) migration
-- Localization with the new, [Fluent](https://projectfluent.org)-powered `sveltia-i18n` library
-- Documentation
+- Enhanced [compatibility with Netlify/Decap CMS](#compatibility)
+- Localization with the new [Fluent](https://projectfluent.org)-powered sveltia-i18n library
+- Accessibility audit
+- Developer documentation (implementation guide)
 - Marketing site
 - Live demo site
 - Official starter templates for the most popular frameworks, including SvelteKit and Next.js
+- Broad automation test coverage (Vitest + Playwright)
 
 ### After the 1.0 release
 
-- Compatibility with Static CMS
-- Roles[^23]
-- Config editor[^10]
-- Mobile support[^18]
-- AI integrations
+- Tackling more Netlify/Decap CMS issues, especially [top voted features](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc), including MDX support[^122], roles[^23], mobile optimization[^18] and config editor[^10] — Some features are already implemented in Sveltia CMS
+- Compatibility with Static CMS, a community fork of Netlify CMS
 - Advanced digital asset management (DAM) features, including image editing and tagging[^114]
+- AI integrations
+- End-user documentation
+- Contributor documentation
 - and more!
 
 ## Getting started
@@ -453,7 +454,7 @@ You can use Sveltia CMS with a local Git repository like Netlify/Decap CMS, but
    - You can remove `local_backend` from your configuration, as it will be ignored by Sveltia CMS.
 1. Launch the local development server for your frontend framework, typically with `npm run dev` or `pnpm dev`.
 1. Visit `http://localhost:[port]/admin/index.html` with Chrome or Edge. The port number varies by framework.
-   - Other Chromium-based browsers may also work. In Brave, you need to enable the File System Access API [with a flag](https://github.com/brave/brave-browser/issues/20563#issuecomment-1021567573).
+   - Other Chromium-based browsers may also work. Brave user? [See below](#enable-local-development-in-brave).
 1. Click “Work with Local Repository” and select the project’s root directory once prompted.
    - If you get an error saying “not a repository root directory”, make sure you’ve turned the folder into a repository with either a CUI ([`git init`](https://github.com/git-guides/git-init)) or GUI, and the hidden `.git` folder exists.
    - If you’re using Windows Subsystem for Linux (WSL), you may get an error saying “Can’t open this folder because it contains system files.” This is due to a limitation in the browser, and you can try some workarounds mentioned in [this issue](https://github.com/coder/code-server/issues/4646) and [this thread](https://github.com/sveltia/sveltia-cms/discussions/101).
@@ -466,6 +467,14 @@ Keep in mind that the local repository support doesn’t perform any Git operati
 
 Also, at this point, you have to reload the CMS to see the latest content after retrieving remote updates. This manual work will be unnecessary once the proposed `FileSystemObserver` API, which is being [implemented in Chromium](https://issues.chromium.org/issues/40105284) behind a flag, becomes available.
 
+#### Enable local development in Brave
+
+In the Brave browser, you must enable the File System Access API with an experiment flag to take advantage of local development.
+
+1. Open `brave://flags/#file-system-access-api` in a new browser tab.
+1. Click Default (Disabled) next to File System Access API and select Enabled.
+1. Relaunch the browser.
+
 ### Using a custom icon for a collection
 
 You can specify an icon for each collection for easy identification in the collection list. You don’t need to install a custom icon set because the Material Symbols font file is already loaded for the application UI. Just pick one of the 2,500+ icons:
@@ -1035,3 +1044,5 @@ This software is provided “as is” without any express or implied warranty. W
 [^120]: Netlify/Decap CMS [#2727](https://github.com/decaporg/decap-cms/issues/2727), [#4884](https://github.com/decaporg/decap-cms/issues/4884)
 
 [^121]: Netlify/Decap CMS [#7262](https://github.com/decaporg/decap-cms/issues/7262)
+
+[^122]: Netlify/Decap CMS [#1776](https://github.com/decaporg/decap-cms/issues/1776), [#2064](https://github.com/decaporg/decap-cms/issues/2064), [#7158](https://github.com/decaporg/decap-cms/issues/7158), [#7259](https://github.com/decaporg/decap-cms/issues/7259)