@sveltia/cms 0.124.2 → 0.126.0

package/README.md

@@ -4,7 +4,7 @@ Sveltia CMS is a Git-based lightweight headless CMS under active development as
 
 Built from the ground up, Sveltia CMS offers excellent UX, DX, performance, security and internationalization (i18n) support. Although some features are still missing, our numerous enhancements across the board ensure smooth daily workflows for content editors and developers alike.
 
-This free, open source successor to Netlify/Decap CMS is currently in public beta, with version 1.0 expected in early 2026.
+This free, open source successor to Netlify/Decap CMS is currently in public beta, with version 1.0 expected in early 2026. Despite being in beta, it’s already [used in production](#showcase) by hundreds of individuals and organizations worldwide.
 
 ![Git-based headless CMS made right](https://raw.githubusercontent.com/sveltia/sveltia-cms/main/docs/screenshot-1.webp?20250405)<br>
 
@@ -95,6 +95,7 @@ This free, open source successor to Netlify/Decap CMS is currently in public bet
   - [Disabling automatic deployments](#disabling-automatic-deployments)
   - [Setting up Content Security Policy](#setting-up-content-security-policy)
   - [Showing the CMS version](#showing-the-cms-version)
+- [Showcase](#showcase)
 - [Support \& Feedback](#support--feedback)
 - [Contributions](#contributions)
 - [Roadmap](#roadmap)
@@ -174,7 +175,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
   - It works as a drop-in replacement for most use cases
   - Some missing features will be implemented before or shortly after GA
 - Tackling as many [Netlify/Decap CMS issues](https://github.com/decaporg/decap-cms/issues) as possible
-  - So far, **275+ issues, or 595+ if including duplicates, have been effectively solved** in Sveltia CMS (Yes, you read it right)
+  - So far, **275+ issues, or 600+ if including duplicates, have been effectively solved** in Sveltia CMS (Yes, you read it right)
   - Target:
     - 300 issues, or 600 if including duplicates, by GA — Almost there! 🚀
     - 450 issues, or 900 if including duplicates, in the future 💪
@@ -363,10 +364,12 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
   - It’s possible to embed the locale code in an entry by using `widget: hidden` along with `default: '{{locale}}'`.[^101]
   - The `value_field` Relation field option can contain a locale prefix like `{{locale}}/{{slug}}`, which will be replaced with the current locale. It’s intended to support i18n in Astro. ([Discussion](https://github.com/sveltia/sveltia-cms/discussions/302))
   - The collection filters are applied correctly regardless of the i18n structure.[^291]
+  - The `summary` collection option supports the `{{locales}}` template tag to show enabled entry locales in the entry list.
 - User interface
   - Eliminates UI confusion: The Preview Pane can be displayed without toggling i18n in the Content Editor. Both panes are scrollable. There is no condition where both panes are edited in the same language at the same time.
   - Users can easily switch between locales while editing by clicking a button instead of a dropdown list when there are less than 5 locales.
   - Language labels appear in human-readable display names instead of ISO 639 language codes because it’s not easy for everyone to recognize `DE` as German, `NL` as Dutch, `ZH` as Chinese, and so on.
+  - It’s possible to set the editor pane locale via a URL query parameter, e.g. `?_locale=fr`.
 - Content editing
   - [Integrates translation services](#translating-entry-fields-with-one-click) to allow translation of text fields from another locale with one click.
   - The Content Editor supports [RTL scripts](https://en.wikipedia.org/wiki/Right-to-left_script) such as Arabic, Hebrew and Persian.[^146]
@@ -412,6 +415,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
     - Sveltia CMS supports [singletons](#using-singletons), a simple form of a file collection.[^233]
     - File collections support files without extensions.[^255] This is useful for [editing site deployment configuration files](#editing-site-deployment-configuration-files), such as `_headers` and `_redirects`.
     - Each file in a file collection has the `format` and `frontmatter_delimiter` options, which can be used to specify the file format, making it possible to have `yaml-frontmatter`, `toml-frontmatter` and `json-frontmatter` side by side.[^218]
+    - The new `raw` format allows you to edit raw files without front matter, such as plain text files, CSV files, JSON files and YAML files.[^316] When using this format, make sure to have only one field named `body` with the `widget` type set to `code`, `markdown`, `richtext` or `text`.
   - The `create` option for folder collections defaults to `true`, providing a better out-of-the-box experience.
   - The collection `label` defaults to the `name` value according to the [Decap CMS document](https://decapcms.org/docs/configuration-options/#collections), while Netlify/Decap CMS actually throws a configuration error if the `label` option is omitted.
   - Nested fields (dot notation) can be used in the `path` option for a folder collection, e.g. `{{fields.state.name}}/{{slug}}`.[^62]
@@ -560,7 +564,8 @@ Sveltia CMS supports all the [built-in widgets](https://decapcms.org/docs/widget
   - Soft line breaks are [rendered as hard line breaks](#rendering-soft-line-breaks-as-hard-line-breaks-in-markdown) in the Preview Pane.
   - Uploaded images will not disappear while editing an entry.[^278][^294]
 - Number
-  - If the `value_type` option is `int` (default) or `float`, the `required` option is `false`, and the value is not entered, the field will be saved as `null` instead of an empty string.[^157] If `value_type` is anything else, the data type will remain a string.
+  - If the `value_type` option is `int` (default) or `float`, the `required` option is `false`, and the value is not entered, the field will be saved as `null` instead of an empty string.[^157]
+  - The `value_type` option accepts `int/string` and `float/string` to save the number as a string instead of a number.
 - Object
   - Sveltia CMS offers two ways to have conditional fields in a collection:[^30]
     - The Object widget supports [variable types](https://decapcms.org/docs/variable-type-widgets/) (the `types` and `typeKey` options) just like the List widget.[^226]
@@ -789,7 +794,7 @@ Sveltia CMS supports the GitHub, GitLab and Gitea/Forgejo [backends](#better-bac
 
 ### Browser support
 
-Sveitia CMS works with all modern browsers, but there are a few limitations because it utilizes some new web technologies:
+Sveltia CMS works with all modern browsers, but there are a few limitations because it utilizes some new web technologies:
 
 - The [local repository workflow](#working-with-a-local-git-repository) requires a Chromium-based browser, including Chrome, Edge and Brave.
 - Safari: The Test backend doesn’t save changes locally; [image optimization](#optimizing-images-for-upload) is slower than in other browsers.
@@ -818,7 +823,7 @@ Static CMS made [some breaking changes](https://staticjscms.netlify.app/docs/dec
   - The `logo_link` global option will not be supported. Use `display_url` or `site_url` instead.
   - The `yaml` global option will not be supported, as Sveltia CMS doesn’t expose the underlying `yaml` library options for forward compatibility reasons. However, we do have some [data output options](#controlling-data-output), including YAML indentation and quotes.
 - I18n support
-  - The `enforce_required_non_default` i18n option will not be supported. Sveitia CMS enforces required fields in all locales by default. However, the `initial_locales` i18n option allows users to [disable non-default locales](#disabling-non-default-locale-content) if needed. Developers can also specify a subset of locales with the `required` field option, e.g. `required: [en]`.
+  - The `enforce_required_non_default` i18n option will not be supported. Sveltia CMS enforces required fields in all locales by default. However, the `initial_locales` i18n option allows users to [disable non-default locales](#disabling-non-default-locale-content) if needed. Developers can also specify a subset of locales with the `required` field option, e.g. `required: [en]`.
 - Widgets
   - The date/time format options for the DateTime widget are **not compatible** since Static CMS [switched to date-fns](https://staticjscms.netlify.app/docs/decap-migration-guide#dates) while Decap CMS and Sveltia CMS have replaced Moment.js with Day.js. Update your formats accordingly.
   - The [KeyValue widget](#new-widgets) is implemented in Sveltia CMS with the same options.
@@ -1994,6 +1999,38 @@ img-src 'self' blob: data: https://*;
 
 A Release Notes link will now appear under the Account menu with the current application version.
 
+## Showcase
+
+Sveltia CMS powers hundreds of websites around the world. Here are some examples of websites using Sveltia CMS. Many of them are switching from Netlify/Decap CMS for a better UX and DX 🎉
+
+<!-- cSpell:disable -->
+
+- [Anil Dash](https://www.anildash.com/): Personal blog of Anil Dash, a prominent tech writer and entrepreneur, who created once-popular CMSs called [Movable Type](https://en.wikipedia.org/wiki/Movable_Type) and [TypePad](https://en.wikipedia.org/wiki/Typepad). Built with Eleventy. ([repository](https://github.com/anildash/anildash-dot-com-netlify)) ([Bluesky post](https://bsky.app/profile/anildash.com/post/3m7osuyipnc22))
+- [Dutch Institute for Vulnerability Disclosure](https://www.divd.nl/): An institute focused on responsible vulnerability disclosure in the Netherlands. Utilizes [i18n support](#better-i18n-support). Built with Hugo. ([repository](https://github.com/DIVD-NL/web-www-v2))
+- [Inclusive Design Research Centre](https://idrc.ocadu.ca/): A research center at OCAD University focused on inclusive design practices. Built with Eleventy. ([repository](https://github.com/inclusive-design/idrc))
+- [FLOE](https://floeproject.org/): An open education project focused on accessibility and inclusive learning technologies. Built with Eleventy. ([repository](https://github.com/fluid-project/floeproject.org)) ([blog post](https://floeproject.org/news/2024-06-24-evaluating-static-content-management-systems/))
+- [SIGPwny](https://sigpwny.com/): A student-run cybersecurity club at the University of Illinois Urbana-Champaign. Built with Astro. ([repository](https://github.com/sigpwny/websites))
+- [Critical Mass Portugal](https://massacritica.pt/en/): The Portuguese chapter of the global Critical Mass movement promoting cycling. Utilizes [i18n support](#better-i18n-support). Built with Astro. ([repository](https://github.com/afonsojramos/critical-mass))
+- [Dylan Beattie](https://dylanbeattie.net/): Personal website of Dylan Beattie, a well-known software developer and speaker. Built with Jekyll. ([repository](https://github.com/dylanbeattie/dylanbeattie.net)) ([blog post](https://dylanbeattie.net/2025/02/13/sveltiacms-jekyll-and-github-pages.html))
+- [The Forgotten Europe Project](https://forgotteneurope.org/): A project dedicated to exploring and documenting lesser-known parts of Europe. Built with SvelteKit. ([repository](https://github.com/refact0r/forgotten-europe-website))
+- [Chris’s Tech ADHD](https://chris-ayers.com/): Personal website of Chris Ayers, a senior software engineer and speaker. Built with Jekyll. ([repository](https://github.com/codebytes/codebytes.github.io)) ([blog post](https://chris-ayers.com/2025/06/26/mobile-cms-on-github-pages/))
+- [Bilgin Dictionary](https://sozluk.ulug.tr/): An etymological dictionary of Turkish. Built with Astro. ([repository](https://github.com/ulughann/sozluk))
+- [Woogles Blog](https://blog.woogles.io/): Blog of a non-profit organization specializing in word games and education. Built with Hugo. ([repository](https://github.com/woogles-io/liwords-static))
+- [The Living Glossary of Digital Narrative](https://glossary.cdn.uib.no/): A collaborative glossary for digital narrative studies. Built with Astro. ([repository](https://github.com/Center-for-Digital-Narrative/Living-Glossary-of-Digital-Narrative))
+- [IA·rbre](https://iarbre.fr/): Collaborative platform for territorial data on urban climate adaptation. Built with MkDocs. ([repository](https://github.com/TelesCoop/iarbre))
+- [Melbourne Disc Golf Club](https://www.melbournediscgolf.com/): A disc golf club in Australia. Built with Astro. ([repository](https://github.com/melbourne-disc-golf/mdgc-website))
+- [ACM Gazi](https://acmgazi.com/): Gazi University Association for Computing Machinery community site. Built with Hugo. ([repository](https://github.com/ACM-Gazi/acm-gazi.github.io))
+- [Volley Club Nogentais](https://volley-club-nogent.fr/): A volleyball club in France. Built with Hugo. ([repository](https://github.com/Volley-Club-Nogentais/vcn-website))
+- [The Scalable Way](https://thescalableway.com/): A consultancy specializing in data platform engineering, analytics, and data science. Built with Eleventy. ([repository](https://github.com/dyvenia/site-thescalableway))
+- [Medieval Scrolls Digital Archive](https://medievalscrolls.fas.harvard.edu/): A comprehensive resource for medieval scrolls at Harvard University. Built with Astro. ([repository](https://github.com/artshumrc/scrolls-astro))
+- [Queer Winnipeg](https://queerwinnipeg.ca/): Blog that shares stories and resources for the local queer community. Built with Astro. ([repository](https://gitlab.com/queerwinnipeg/queerwinnipeg.ca))
+- [Code for Heilbronn](https://codeforheilbronn.de/): A civic tech group in Germany, focused on open data and digital solutions for local issues. Built with Hugo. ([repository](https://github.com/cfhn/codeforheilbronn-website))
+- [Plan B Architecture Studio](https://www.planasb.lt/en/): An architecture studio based in Lithuania. Built with Astro. ([agency case study](https://oaksun.studio/work/architectural-studio/))
+
+<!-- cSpell:enable -->
+
+More projects, including small personal blogs and portfolios, can be found by [searching GitHub](https://github.com/search?q=sveltia/cms&type=pullrequests). Please note that the code search only returns 100 results, and private repositories are not included. We’ll continue to update this list as we discover more projects!
+
 ## Support & Feedback
 
 While we don’t have dedicated developer/user support resources, you can post [quick questions](https://github.com/sveltia/sveltia-cms/discussions/new?category=q-a) on the [Discussions](https://github.com/sveltia/sveltia-cms/discussions) page of our GitHub repository. [Feedback](https://github.com/sveltia/sveltia-cms/discussions/new?category=ideas) is also welcome, but please check the [Compatibility](#compatibility) and [Roadmap](#roadmap) sections of this README before starting a new discussion — your idea may already be covered.
@@ -2024,11 +2061,12 @@ We cannot promise any specific release dates, but here is a rough roadmap for th
 
 ### v1.0
 
-Due early 2026
+Due early 2026. This will be the first stable release of Sveltia CMS, suitable for production use in many scenarios. This release also [solves 300 issues](#project-status) of Netlify/Decap CMS, including many highly requested features and important bug fixes.
 
 - Enhanced [compatibility with Netlify/Decap CMS](#compatibility)
 - Tackling some more Netlify/Decap CMS issues:
   - PKCE for GitHub[^285] — It’s [not yet supported](https://github.com/orgs/community/discussions/15752) by GitHub but is [planned for Q4 2025](https://github.com/github/roadmap/issues/1153)
+  - [Amazon S3 and Cloudflare R2 media library backend](https://github.com/sveltia/sveltia-cms/issues/586)[^315]
   - Thorough config validation[^246]
   - [Entry pre-validation/normalization](https://github.com/sveltia/sveltia-cms/issues/395)[^248]
 - Accessibility audit
@@ -2040,7 +2078,7 @@ See also the [1.0 RC](https://github.com/sveltia/sveltia-cms/milestone/1) and [1
 
 ### v2.0
 
-Due mid-2026
+Due mid-2026. This release completes the core features of Sveltia CMS as a successor to Netlify/Decap CMS.
 
 - Implementing [a few deferred Netlify/Decap CMS features](#current-limitations), including editorial workflow and nested collections, while addressing a number of bugs in their implementations
   - They will probably first be included as beta features in v1.x releases
@@ -2053,7 +2091,7 @@ See also the [2.0](https://github.com/sveltia/sveltia-cms/milestone/3) milestone
 
 ### v3.0
 
-Due late 2026
+Due late 2026. This release provides an alternative to the deprecated Netlify Identity and Git Gateway services used by Netlify/Decap CMS.
 
 - **Sveltia CMS Additions**: Edge functions for Cloudflare Workers and possibly other platforms that provide features that cannot be implemented client-side:
   - User management (Netlify Identity alternative) with roles[^23]
@@ -2084,6 +2122,7 @@ Due late 2026
 - Enhancements to **Sveltia CMS Additions** (some may be included in v3.0):
   - Post locking[^166] (like [WordPress](https://codex.wordpress.org/Post_Locking))
   - Scheduled posts[^167]
+  - [Private configuration](https://github.com/sveltia/sveltia-cms/discussions/576)
   - [Credential management](https://github.com/sveltia/sveltia-cms/issues/444) for service API keys, deploy hook URL, etc.
   - Proxy for services that don’t support [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CORS):
     - [DeepL Translate](https://github.com/sveltia/sveltia-cms/issues/437)
@@ -2372,7 +2411,7 @@ This project would not have been possible without the open source Netlify CMS pr
 
 [^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), [#7450](https://github.com/decaporg/decap-cms/issues/7450), [#7453](https://github.com/decaporg/decap-cms/issues/7453), [#7572](https://github.com/decaporg/decap-cms/issues/7572), [#7602](https://github.com/decaporg/decap-cms/issues/7602), [#7655](https://github.com/decaporg/decap-cms/issues/7655)
 
-[^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), [#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), [#7278](https://github.com/decaporg/decap-cms/issues/7278), [#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), [#7412](https://github.com/decaporg/decap-cms/issues/7412), [#7413](https://github.com/decaporg/decap-cms/issues/7413), [#7422](https://github.com/decaporg/decap-cms/issues/7422), [#7427](https://github.com/decaporg/decap-cms/issues/7427), [#7434](https://github.com/decaporg/decap-cms/issues/7434), [#7438](https://github.com/decaporg/decap-cms/issues/7438), [#7454](https://github.com/decaporg/decap-cms/issues/7454), [#7464](https://github.com/decaporg/decap-cms/issues/7464), [#7471](https://github.com/decaporg/decap-cms/issues/7471), [#7485](https://github.com/decaporg/decap-cms/issues/7485), [#7499](https://github.com/decaporg/decap-cms/issues/7499), [#7515](https://github.com/decaporg/decap-cms/issues/7515), [#7564](https://github.com/decaporg/decap-cms/issues/7564), [#7571](https://github.com/decaporg/decap-cms/issues/7571), [#7574](https://github.com/decaporg/decap-cms/issues/7574), [#7580](https://github.com/decaporg/decap-cms/issues/7580), [#7583](https://github.com/decaporg/decap-cms/issues/7583), [#7589](https://github.com/decaporg/decap-cms/issues/7589), [#7593](https://github.com/decaporg/decap-cms/issues/7593), [#7595](https://github.com/decaporg/decap-cms/issues/7595), [#7601](https://github.com/decaporg/decap-cms/issues/7601), [#7610](https://github.com/decaporg/decap-cms/issues/7610), [#7614](https://github.com/decaporg/decap-cms/issues/7614), [#7620](https://github.com/decaporg/decap-cms/issues/7620), [#7621](https://github.com/decaporg/decap-cms/issues/7621), [#7622](https://github.com/decaporg/decap-cms/issues/7622), [#7631](https://github.com/decaporg/decap-cms/issues/7631), [#7643](https://github.com/decaporg/decap-cms/issues/7643), [#7644](https://github.com/decaporg/decap-cms/issues/7644), [#7648](https://github.com/decaporg/decap-cms/issues/7648), [#7669](https://github.com/decaporg/decap-cms/issues/7669) — 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).
+[^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), [#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), [#7278](https://github.com/decaporg/decap-cms/issues/7278), [#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), [#7412](https://github.com/decaporg/decap-cms/issues/7412), [#7413](https://github.com/decaporg/decap-cms/issues/7413), [#7422](https://github.com/decaporg/decap-cms/issues/7422), [#7427](https://github.com/decaporg/decap-cms/issues/7427), [#7434](https://github.com/decaporg/decap-cms/issues/7434), [#7438](https://github.com/decaporg/decap-cms/issues/7438), [#7454](https://github.com/decaporg/decap-cms/issues/7454), [#7464](https://github.com/decaporg/decap-cms/issues/7464), [#7471](https://github.com/decaporg/decap-cms/issues/7471), [#7485](https://github.com/decaporg/decap-cms/issues/7485), [#7499](https://github.com/decaporg/decap-cms/issues/7499), [#7515](https://github.com/decaporg/decap-cms/issues/7515), [#7564](https://github.com/decaporg/decap-cms/issues/7564), [#7571](https://github.com/decaporg/decap-cms/issues/7571), [#7574](https://github.com/decaporg/decap-cms/issues/7574), [#7580](https://github.com/decaporg/decap-cms/issues/7580), [#7583](https://github.com/decaporg/decap-cms/issues/7583), [#7589](https://github.com/decaporg/decap-cms/issues/7589), [#7593](https://github.com/decaporg/decap-cms/issues/7593), [#7595](https://github.com/decaporg/decap-cms/issues/7595), [#7601](https://github.com/decaporg/decap-cms/issues/7601), [#7610](https://github.com/decaporg/decap-cms/issues/7610), [#7614](https://github.com/decaporg/decap-cms/issues/7614), [#7620](https://github.com/decaporg/decap-cms/issues/7620), [#7621](https://github.com/decaporg/decap-cms/issues/7621), [#7622](https://github.com/decaporg/decap-cms/issues/7622), [#7631](https://github.com/decaporg/decap-cms/issues/7631), [#7643](https://github.com/decaporg/decap-cms/issues/7643), [#7644](https://github.com/decaporg/decap-cms/issues/7644), [#7648](https://github.com/decaporg/decap-cms/issues/7648), [#7669](https://github.com/decaporg/decap-cms/issues/7669), [#7688](https://github.com/decaporg/decap-cms/issues/7688), [#7689](https://github.com/decaporg/decap-cms/issues/7689) — These `removeChild` crashes are common in React apps, likely caused by a [browser extension](https://github.com/facebook/react/issues/17256), [#7690](https://github.com/decaporg/decap-cms/issues/7690) or [Google Translate](https://github.com/facebook/react/issues/11538).
 
 [^114]: Netlify/Decap CMS [#5029](https://github.com/decaporg/decap-cms/issues/5029), [#5048](https://github.com/decaporg/decap-cms/issues/5048)
 
@@ -2767,3 +2806,7 @@ This project would not have been possible without the open source Netlify CMS pr
 [^313]: Netlify/Decap CMS [#542](https://github.com/decaporg/decap-cms/issues/542)
 
 [^314]: Netlify/Decap CMS [#3719](https://github.com/decaporg/decap-cms/issues/3719)
+
+[^315]: Netlify/Decap CMS [#2035](https://github.com/decaporg/decap-cms/issues/2035), [#7362](https://github.com/decaporg/decap-cms/issues/7362), [#7543](https://github.com/decaporg/decap-cms/issues/7543)
+
+[^316]: Netlify/Decap CMS [#1152](https://github.com/decaporg/decap-cms/issues/1152)