@sveltia/cms 0.112.3 → 0.112.5

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
@@ -205,6 +205,7 @@ Note: This lengthy section compares Sveltia CMS with both Netlify CMS and Decap
205
205
  - Built completely from scratch with [Svelte](https://svelte.dev/) instead of forking React-based Netlify/Decap CMS. The app starts fast and stays fast with [no virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead). Note that Svelte is a compiler and Sveltia CMS is framework-agnostic; it’s served as a vanilla JavaScript bundle.
206
206
  - Small footprint: The bundle size is less than 500 KB when minified and [brotlied](https://en.wikipedia.org/wiki/Brotli), which is much lighter than Netlify CMS (1.5 MB), Decap CMS (1.5 MB) and Static CMS (2.6 MB).[^57][^64] This significant reduction in size is thanks to the combination of [Svelte 5](https://svelte.dev/blog/svelte-5-is-alive) and [Vite](https://vite.dev/). Sveltia CMS also dynamically loads certain dependencies only when needed, further reducing the initial load time.
207
207
  - 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] (the useless `search` configuration option is therefore ignored). It also avoids the slowness and potential API rate limit violations caused by hundreds of requests with Relation fields.[^14]
208
+ - Note: Loading files from GitLab is currently slower than usual because we have implemented a workaround for a [GraphQL complexity limit issue](https://github.com/sveltia/sveltia-cms/issues/525) in GitLab 18.4.2. This workaround will be removed in the future once GitLab has fixed the issue.
208
209
  - Saving entries and assets to GitHub is also much faster thanks to the [GraphQL mutation](https://github.blog/changelog/2021-09-13-a-simpler-api-for-authoring-commits/).
209
210
  - The Gitea/Forgejo backend is also faster because it utilizes an efficient API method introduced in Gitea 1.24 and Forgejo 12.0.
210
211
  - Our [local repository workflow](#working-with-a-local-git-repository) utilizes the modern [File System Access API](https://developer.chrome.com/docs/capabilities/web-apis/file-system-access) to read and write files natively through the web browser, rather than using a slow, ad hoc REST API through a proxy server.
@@ -504,6 +505,7 @@ Sveltia CMS supports all the [built-in widgets](https://decapcms.org/docs/widget
504
505
  - For [better security](#better-security), the `sanitize_preview` option defaults to `true` since [Sveltia CMS 0.105.0](https://github.com/sveltia/sveltia-cms/releases/tag/v0.105.0).
505
506
  - The default editor mode can be set 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.
506
507
  - A Markdown field plays well with a variable type List field.[^202]
508
+ - The bullet list marker is a hyphen (`-`) rather than an asterisk (`*`), which is the comment form’s default behaviour on GitHub and GitLab.[^296]
507
509
  - A combination of bold and italic doesn’t create a confusing 3-asterisk markup.[^160] In our editor, bold is 2 asterisks and italic is an underscore.
508
510
  - The built-in `image` component can be inserted with a single click.
509
511
  - The built-in `image` component allows users to add, edit or remove a link on an image.[^171] To disable this feature, add `linked_images: false` to the Markdown field options.
@@ -1195,7 +1197,7 @@ The configuration for a [file collection](https://decapcms.org/docs/collection-f
1195
1197
  Sveltia CMS comes with a handy translation API integration so that you can translate any text field from another locale without leaving the Content Editor. Currently, the following services are supported:
1196
1198
 
1197
1199
  - Google’s [Cloud Translation](https://cloud.google.com/translate)
1198
- - Anthropic’s [Claude Haiku 3.5](https://www.anthropic.com/claude/haiku)
1200
+ - Anthropic’s [Claude Haiku 4.5](https://www.anthropic.com/claude/haiku)
1199
1201
  - OpenAI’s [GPT-4o mini](https://platform.openai.com/docs/models/gpt-4o-mini)
1200
1202
 
1201
1203
  Google’s API is very fast and offers a free tier. Other LLMs may produce more natural translations, but they are slower and require a paid plan. Choose the one that best fits your needs.
@@ -1225,11 +1227,16 @@ Note that the Translation button on the pane header only translates empty fields
1225
1227
 
1226
1228
  You can also provide your API keys in the Settings dialog or change the default translation service. API keys are stored in the browser’s local storage, so you don’t need to enter them every time.
1227
1229
 
1228
- If you don’t want some text to be translated, use the HTML [`translate`](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/translate) attribute or [`notranslate`](https://developers.google.com/search/blog/2008/10/helping-you-break-language-barrier) class. For Anthropic and OpenAI, you can also use the `notranslate` comment to exclude specific parts of Markdown content from translation:
1230
+ If you don’t want some text to be translated, use the HTML [`translate`](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Global_attributes/translate) attribute or [`notranslate`](https://developers.google.com/search/blog/2008/10/helping-you-break-language-barrier) class:
1229
1231
 
1230
1232
  ```html
1231
1233
  <div translate="no">...</div>
1232
1234
  <span class="notranslate">...</span>
1235
+ ```
1236
+
1237
+ For Anthropic and OpenAI, you can also use the `notranslate` comment to exclude specific parts of Markdown content from translation:
1238
+
1239
+ ```html
1233
1240
  <!-- notranslate -->...<!-- /notranslate -->
1234
1241
  {/* notranslate */}...{/* /notranslate */}
1235
1242
  ```
@@ -2619,10 +2626,12 @@ This project would not have been possible without the open source Netlify CMS pr
2619
2626
 
2620
2627
  [^291]: Netlify/Decap CMS [#7612](https://github.com/decaporg/decap-cms/pull/7612)
2621
2628
 
2622
- [^292]: Netlify/Decap CMS [7518](https://github.com/decaporg/decap-cms/issues/7518)
2629
+ [^292]: Netlify/Decap CMS [#7518](https://github.com/decaporg/decap-cms/issues/7518)
2623
2630
 
2624
- [^293]: Netlify/Decap CMS [7616](https://github.com/decaporg/decap-cms/issues/7616)
2631
+ [^293]: Netlify/Decap CMS [#7616](https://github.com/decaporg/decap-cms/issues/7616)
2625
2632
 
2626
2633
  [^294]: Netlify/Decap CMS [#7576](https://github.com/decaporg/decap-cms/issues/7576), [#7587](https://github.com/decaporg/decap-cms/issues/7587)
2627
2634
 
2628
- [^295]: Netlify/Decap CMS [6243](https://github.com/decaporg/decap-cms/issues/6243)
2635
+ [^295]: Netlify/Decap CMS [#6243](https://github.com/decaporg/decap-cms/issues/6243)
2636
+
2637
+ [^296]: Netlify/Decap CMS [#7638](https://github.com/decaporg/decap-cms/discussions/7638)