@sveltia/cms 0.50.0 → 0.50.1
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 +9 -9
- package/dist/sveltia-cms.js +28 -28
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +38 -38
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -109,7 +109,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
|
|
|
109
109
|
- Ensuring substantial [compatibility with Netlify/Decap CMS](#compatibility)
|
|
110
110
|
- Tackling as many [Netlify/Decap CMS issues](https://github.com/decaporg/decap-cms/issues) as possible
|
|
111
111
|
- So far, 145+ of them, or 255+ including duplicates, have been effectively solved in Sveltia CMS
|
|
112
|
-
- Target: 250 or all relevant and fixable issues in a future release
|
|
112
|
+
- Target: 250 or all relevant and fixable issues in a future release (Yes, you read it right)
|
|
113
113
|
- Note: Issues include both feature requests and bug reports; we also track their [stale issues](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+%22Closing+as+stale%22) and [discussions](https://github.com/decaporg/decap-cms/discussions)
|
|
114
114
|
- [Let us know](https://github.com/sveltia/sveltia-cms/issues/new?labels=enhancement) if you have any specific issues you’d like to see solved!
|
|
115
115
|
- Responding to feedback from [@kyoshino](https://github.com/kyoshino)’s clients and regular users
|
|
@@ -120,7 +120,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
|
|
|
120
120
|
|
|
121
121
|
## Differentiators
|
|
122
122
|
|
|
123
|
-
We are working hard to create a **tremendously better alternative to Netlify CMS and Decap CMS** by improving everything. Here’s what makes Sveltia CMS different. Look how serious we are!
|
|
123
|
+
We are working hard to create a **tremendously better alternative to Netlify CMS and Decap CMS** by improving everything. Here’s what makes Sveltia CMS different. Look how damn serious we are!
|
|
124
124
|
|
|
125
125
|
### Better UX
|
|
126
126
|
|
|
@@ -210,7 +210,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
210
210
|
- The [i18n limitations](https://decapcms.org/docs/i18n/#limitations) in Netlify/Decap CMS do not apply to Sveltia CMS:
|
|
211
211
|
- File collections support multiple files/folders i18n structures[^87]. To enable it, simply use the `{{locale}}` template tag in the `file` path option, e.g. `content/pages/about.{{locale}}.json` or `content/pages/{{locale}}/about.json`. For backward compatibility, the global `structure` option only applies to folder collections, and the default i18n structure for file collections remains single file.
|
|
212
212
|
- The List and Object widgets support the `i18n: duplicate` field configuration so that changes made with these widgets are duplicated between locales[^7][^68]. The `i18n` configuration can normally be used for the subfields.
|
|
213
|
-
- The `required` field option accepts an array of locale names in addition to a boolean, making the field required for a subset of locales when i18n support is enabled. For example, if only English is required, you
|
|
213
|
+
- The `required` field option accepts an array of locale names in addition to a boolean, making the field required for a subset of locales when i18n support is enabled. For example, if only English is required, you could write `required: [en]`. An empty array is equivalent to `required: false`.
|
|
214
214
|
- [Entry-relative media folders](https://decapcms.org/docs/collection-folder/#media-and-public-folder) can be used in conjunction with the `multiple_folders` i18n structure[^21].
|
|
215
215
|
- The `{{locale}}` template tag can be used in the [`preview_path`](https://decapcms.org/docs/configuration-options/#preview_path) collection option to provide site preview links for each language[^63].
|
|
216
216
|
- It’s possible to [use a random UUID for an entry slug](#using-a-random-id-for-an-entry-slug), which is a good option for locales that write in non-Latin characters.
|
|
@@ -379,9 +379,9 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
379
379
|
- Compute
|
|
380
380
|
- The experimental `compute` widget allows to reference the value of other fields in the same collection, similar to the `summary` property for the List and Object widgets[^104]. Use the `value` property to define the value template, e.g. `posts-{{fields.slug}}` ([example](https://github.com/sveltia/sveltia-cms/issues/111)).
|
|
381
381
|
- The `value` property also supports a value of `{{index}}`, which can hold the index of a list item ([example](https://github.com/sveltia/sveltia-cms/issues/172)).
|
|
382
|
-
- KeyValue
|
|
383
|
-
- The new `keyvalue`
|
|
384
|
-
- The implementation is compatible with [Static CMS](https://staticjscms.netlify.app/docs/widget-keyvalue), a
|
|
382
|
+
- KeyValue (Dictionary)
|
|
383
|
+
- The new `keyvalue` widget allows users to add arbitrary key-value pairs to a field[^123].
|
|
384
|
+
- The implementation is compatible with [Static CMS](https://staticjscms.netlify.app/docs/widget-keyvalue), but we provide a more intuitive UI. You can press Enter to move focus or add a new row, and the preview is displayed in a clean table.
|
|
385
385
|
- UUID
|
|
386
386
|
- In addition to [generating UUIDs for entry slugs](#using-a-random-id-for-an-entry-slug), Sveltia CMS also supports the proposed `uuid` widget with the following properties[^12]:
|
|
387
387
|
- `prefix`: A string to be prepended to the value. Default: an empty string.
|
|
@@ -964,10 +964,10 @@ See [Contributing to Sveltia CMS](https://github.com/sveltia/sveltia-cms/blob/ma
|
|
|
964
964
|
|
|
965
965
|
- Implementing the remaining Netlify/Decap CMS features: Editorial Workflow, Open Authoring and nested collections
|
|
966
966
|
- Tackling more Netlify/Decap CMS issues, including MDX support[^122], manual entry sorting[^125], roles[^23], mobile optimization[^18] and config editor[^10] — Some [top-voted features](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) are already implemented in Sveltia CMS
|
|
967
|
-
- Exploring compatibility with Static CMS
|
|
968
|
-
- More integration options: stock photos, cloud storage providers,
|
|
969
|
-
- Advanced digital asset management (DAM) features, including image editing and tagging[^114]
|
|
967
|
+
- Exploring further compatibility with Static CMS
|
|
968
|
+
- More integration options: stock photos, stock videos, cloud storage providers, translation services, maps, analytics tools
|
|
970
969
|
- AI integrations for image generation and content writing
|
|
970
|
+
- Advanced digital asset management (DAM) features, including image editing and tagging[^114]
|
|
971
971
|
- End-user documentation
|
|
972
972
|
- Contributor documentation
|
|
973
973
|
- Marketplace for custom widgets, etc.
|