@sveltia/cms 0.121.4 → 0.122.0
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 +12 -6
- package/dist/sveltia-cms.js +295 -271
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +295 -271
- package/dist/sveltia-cms.mjs.map +1 -1
- package/main.d.ts +7 -1
- package/package.json +3 -2
- package/schema/sveltia-cms.json +1 -1
- package/types/public.d.ts +121 -8
package/README.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Sveltia CMS is a Git-based lightweight headless CMS under active development as a modern, powerful, direct replacement for Netlify CMS (now Decap CMS). We have picked up where they left off and have already solved over 270 issues reported in the predecessor’s repository, ranging from critical bugs to top feature requests.
|
|
4
4
|
|
|
5
|
-
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.
|
|
5
|
+
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.
|
|
6
6
|
|
|
7
7
|
This free, open source successor to Netlify/Decap CMS is currently in public beta, with version 1.0 expected in early 2026.
|
|
8
8
|
|
|
@@ -188,7 +188,7 @@ While we fix reported bugs as quickly as possible, usually within 24 hours, our
|
|
|
188
188
|
- The remaining bugs are mostly related to [unimplemented features](#current-limitations)
|
|
189
189
|
- Many of their [top-voted features](https://github.com/decaporg/decap-cms/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc) are [on our table](#roadmap) or already implemented in Sveltia CMS
|
|
190
190
|
- Solving [our own issues](https://github.com/sveltia/sveltia-cms/issues)
|
|
191
|
-
- Preparing comprehensive, up-to-date, easy-to-understand documentation
|
|
191
|
+
- Preparing comprehensive, up-to-date, easy-to-understand [documentation](https://github.com/sveltia/sveltia-cms/issues/485)
|
|
192
192
|
- Implementing our own enhancement ideas for every part of the product
|
|
193
193
|
- Responding to requests from the maintainer’s clients
|
|
194
194
|
- Making the code clean and maintainable
|
|
@@ -203,14 +203,14 @@ Note: This lengthy section compares Sveltia CMS with both Netlify CMS and Decap
|
|
|
203
203
|
|
|
204
204
|
### Better UX
|
|
205
205
|
|
|
206
|
-
- Created and actively maintained by an [experienced UX engineer](https://github.com/kyoshino) who loves code, design, marketing, localization and everything in between. You can expect constant improvements to the user experience (UX) and developer experience (DX) across the platform.
|
|
206
|
+
- Created and actively maintained by an [experienced UX engineer](https://github.com/kyoshino) who loves code, design, marketing, localization, documentation and everything in between. You can expect constant improvements to the user experience (UX) and developer experience (DX) across the platform.
|
|
207
207
|
- The maintainer tries to respond to bug reports as quickly as possible. While there are no guarantees, the typical turnaround time for a bug fix is less than 24 hours.
|
|
208
208
|
- Frequent releases deliver new features and enhancements to users more quickly. Meanwhile, the release interval of Decap CMS has been irregular and often long, sometimes exceeding 2 months.
|
|
209
209
|
- Many of our minor [releases](https://github.com/sveltia/sveltia-cms/releases) address one or more Netlify/Decap CMS issues, giving you even more reasons to switch from the legacy predecessor.
|
|
210
210
|
- Offers a modern, intuitive user interface that utilizes the full viewport,[^178] inspired in part by the Netlify CMS v3 prototype.[^1][^211][^212][^213][^214]
|
|
211
211
|
- Provides immersive dark mode.[^2] The UI theme follows the user’s system preference by default and can be changed in the application settings.
|
|
212
212
|
- Users can easily manage content on-the-go with mobile and tablet support.[^18][^215]
|
|
213
|
-
- For a smoother experience, we even go beyond responsive design with optimized navigation, floating action buttons,
|
|
213
|
+
- For a smoother experience, we even go beyond responsive design with optimized navigation, floating action buttons, [view transitions](https://developer.chrome.com/docs/web-platform/view-transitions), larger buttons, and other tweaks. We’ll continue to fully optimize the app for small screens and touch devices.
|
|
214
214
|
- 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.
|
|
215
215
|
- 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.
|
|
216
216
|
- Other crashes in Netlify/Decap CMS are also irrelevant to us, making Sveltia CMS much more stable.[^112][^203][^204][^260] Netlify/Decap CMS continues to receive crash reports on a daily basis, with no effective solution in sight.
|
|
@@ -678,6 +678,9 @@ Sveltia CMS supports all the [built-in widgets](https://decapcms.org/docs/widget
|
|
|
678
678
|
- Inline components are supported.[^267]
|
|
679
679
|
- Field validation works as expected.[^279]
|
|
680
680
|
- No error is raised in the browser console saying `Sent invalid data to remark`[^280] or `onValidate is not a function`.[^281]
|
|
681
|
+
- Enhancements to [event hooks](https://decapcms.org/docs/registering-events/):
|
|
682
|
+
- Missing `identifier_field` won’t cause an error when the `preSave` hook is triggered.[^306]
|
|
683
|
+
- Content can be modified in the `prePublish` hook (once we support editorial workflow).[^307]
|
|
681
684
|
- Async functions can be used for [custom parsers/formatters](https://decapcms.org/docs/custom-formatters/).[^149]
|
|
682
685
|
- The application renders within the dimensions of a [custom mount element](https://decapcms.org/docs/custom-mounting/), if exists.[^109]
|
|
683
686
|
|
|
@@ -698,11 +701,10 @@ However, 100% feature parity is never planned, and some features are still missi
|
|
|
698
701
|
|
|
699
702
|
We are working hard to implement several missing features from Netlify/Decap CMS. Check our [release notes](https://github.com/sveltia/sveltia-cms/releases) and [Bluesky](https://bsky.app/profile/sveltiacms.app) for updates.
|
|
700
703
|
|
|
701
|
-
- The following
|
|
704
|
+
- The following API features are not yet implemented and will be added before the 1.0 release:
|
|
702
705
|
- Preview for [custom editor components](https://decapcms.org/docs/custom-widgets/#registereditorcomponent) (`CMS.registerEditorComponent`)
|
|
703
706
|
- [Custom widgets](https://decapcms.org/docs/custom-widgets/) (`CMS.registerWidget`)
|
|
704
707
|
- [Custom preview templates](https://decapcms.org/docs/customization/#registerpreviewtemplate) (`CMS.registerPreviewTemplate`) ([#51](https://github.com/sveltia/sveltia-cms/issues/51))
|
|
705
|
-
- [Event hooks](https://decapcms.org/docs/registering-events/) (`CMS.registerEventListener`) ([#167](https://github.com/sveltia/sveltia-cms/issues/167))
|
|
706
708
|
- [Documentation](https://github.com/sveltia/sveltia-cms/issues/485) and site config validation are under development.
|
|
707
709
|
- [Localization](https://github.com/sveltia/sveltia-cms/blob/main/src/lib/locales/README.md) and a [demo site](https://github.com/sveltia/sveltia-cms/issues/1) will follow soon.
|
|
708
710
|
- Due to the complexity, we have decided to **defer the following features to the 1.x or 2.0 release** due mid-2026. Netlify/Decap CMS has dozens of open issues with these collaboration and beta features — we want to implement them the right way.
|
|
@@ -2735,3 +2737,7 @@ This project would not have been possible without the open source Netlify CMS pr
|
|
|
2735
2737
|
[^304]: Netlify/Decap CMS [#4538](https://github.com/decaporg/decap-cms/issues/4538), [#6371](https://github.com/decaporg/decap-cms/issues/6371)
|
|
2736
2738
|
|
|
2737
2739
|
[^305]: Netlify/Decap CMS [#1483](https://github.com/decaporg/decap-cms/issues/1483)
|
|
2740
|
+
|
|
2741
|
+
[^306]: Netlify/Decap CMS [#6775](https://github.com/decaporg/decap-cms/issues/6775)
|
|
2742
|
+
|
|
2743
|
+
[^307]: Netlify/Decap CMS [#7133](https://github.com/decaporg/decap-cms/issues/7133)
|