@sveltia/cms 0.8.1 → 0.8.3

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.
Files changed (3) hide show
  1. package/README.md +22 -21
  2. package/dist/sveltia-cms.js +104 -104
  3. package/package.json +2 -2
package/README.md CHANGED
@@ -1,20 +1,20 @@
1
1
  # Sveltia CMS
2
2
 
3
- Sveltia CMS is a Git-based lightweight headless CMS under active development as a drop-in replacement for [Netlify/Decap CMS](https://decapcms.org/). You can use it with your favourite static site generator like SvelteKit, Eleventy, Next.js and Hugo to manage content as static files in a Git repository. The open source alternative to Netlify/Decap CMS is now in public beta — with more features to come.
3
+ Sveltia CMS is a Git-based lightweight headless CMS under active development as a modern, quick replacement for [Netlify/Decap CMS](https://decapcms.org/). You can use it with your favourite static site generator like SvelteKit, Eleventy, Next.js and Hugo to manage content as static files in a Git repository. The free open source alternative to Netlify/Decap CMS is now in public beta — with more features to come.
4
4
 
5
5
  ![Screenshot: Git-based Headless CMS with Dark Mode](docs/screenshot-20231120-1.webp)<br>
6
6
 
7
7
  ![Screenshot: Instant Entry Listing, Searching and Saving](docs/screenshot-20231120-2.webp)<br>
8
8
 
9
- ![Screenshot: Stock Photo Integration](docs/screenshot-20231120-3.webp)<br>
9
+ ![Screenshot: Stock Photo Integration with Pexels, Pixabay and Unsplash](docs/screenshot-20231120-3.webp)<br>
10
10
 
11
- ![Screenshot: All-New Asset Library; Full Internationalization Support](docs/screenshot-20231120-4.webp)<br>
11
+ ![Screenshot: All-New Asset Library; Full Internationalization Support with DeepL](docs/screenshot-20231120-4.webp)<br>
12
12
 
13
- ![Screenshot: Single-Line Migration from Netlify/Decap CMS](docs/screenshot-20231120-5.webp)<br>
13
+ ![Screenshot: Single-Line Migration from Netlify/Decap CMS (depending on your current setup)](docs/screenshot-20231120-5.webp)<br>
14
14
 
15
15
  ## Motivation
16
16
 
17
- Sveltia CMS was born in November 2022, when the progress of Netlify CMS was stalled for more than six months. [@kyoshino](https://github.com/kyoshino)’s clients wanted to replace their Netlify CMS instances without much effort, mainly to get better internationalization support.
17
+ Sveltia CMS was born in November 2022, when the progress of Netlify CMS was stalled for more than six months. [@kyoshino](https://github.com/kyoshino)’s clients wanted to replace their Netlify CMS instances without much effort, mainly to get better internationalization (i18n) support.
18
18
 
19
19
  To achieve radical improvements in UX, performance and i18n, it was decided to build an alternative from the ground up, while ensuring an easy migration path from the other. After proving the concept with a rapid [Svelte](https://svelte.dev/) prototype, development was accelerated to address their primary use cases. The new offering has since been released as open source software to encourage wider adoption.
20
20
 
@@ -27,23 +27,23 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
27
27
  ### Compatible with Netlify/Decap CMS
28
28
 
29
29
  - Ready to replace Netlify/Decap CMS _in some casual use case scenarios_ by updating a single line of code.
30
- - Existing [configuration files](https://decapcms.org/docs/configuration-options/) can be reused as is.
31
- - Various features are still missing though — [see the compatibility chart below](#compatibility) for details.
30
+ - Your existing [configuration file](https://decapcms.org/docs/configuration-options/) can be reused as is.
31
+ - Various features are still missing though — look at the [compatibility chart](#compatibility) below to see if you can migrate.
32
32
 
33
33
  ### Better UX
34
34
 
35
- - Created and maintained by an [experienced UX engineer](https://github.com/kyoshino) who loves code and design. You can expect constant UX improvements.
35
+ - Created and maintained by an [experienced UX engineer](https://github.com/kyoshino) who loves code and design. You can expect constant UX improvements across the platform.
36
36
  - Offers a modern, intuitive user interface, including an immersive dark mode[^2], inspired in part by the Netlify CMS v3 prototype[^1].
37
- - Comes with touch device support. While the UI is not yet optimized for smaller screens, larger tablets like iPad Pro or Pixel Tablet should work well.
37
+ - Comes with touch device support. While the UI is not yet optimized for small screens, large tablets like iPad Pro or Pixel Tablet should work well.
38
38
  - The screenshots above are worth a thousand words!
39
39
 
40
40
  ### Better performance
41
41
 
42
42
  - 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 almost any framework.
43
+ - Small footprint: less than 300 KB when minified and gzipped, compared to 1.5 MB of Netlify/Decap CMS. And [no virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead).
43
44
  - Uses the GraphQL API for GitHub to quickly fetch content at once, so that entries and assets can be listed and searched instantly. This avoids the slowness and potential API rate limit violations caused by hundreds of requests with relation widgets[^14].
44
45
  - Saving entries and assets is also much faster thanks to the [GraphQL mutation](https://github.blog/changelog/2021-09-13-a-simpler-api-for-authoring-commits/).
45
46
  - Caches Git files locally to further speed up startup and reduce bandwidth.
46
- - Small footprint: less than 300 KB when minified and gzipped, compared to 1.5 MB of Netlify/Decap CMS. And [no virtual DOM overhead](https://svelte.dev/blog/virtual-dom-is-pure-overhead).
47
47
 
48
48
  ### Better productivity
49
49
 
@@ -81,12 +81,12 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
81
81
 
82
82
  - Required fields, not optional fields, are clearly marked for efficient data entry.
83
83
  - Integration with Pexels, Pixabay and Unsplash makes it easy to insert free stock photos into image fields[^8].
84
- - Optional object fields (`widget:object` with `required:false`) can be manually added or removed. If removed, the required subfields will no longer trigger validation errors[^16].
84
+ - Optional object fields (`widget: object` with `required: false`) can be manually added or removed. If removed, the required subfields will no longer trigger validation errors[^16].
85
85
  - You can revert changes to all fields or a specific field.
86
86
 
87
87
  ### Asset Library enhancements
88
88
 
89
- - An all-new Asset Library makes it easy to manage all your files, including images and documents.
89
+ - A completely new Asset Library, built separately from the image selection dialog, makes it easy to manage all of your files, including images and documents.
90
90
  - You can sort or filter assets by name or file type and view asset details, including size, dimensions, and a list of entries that use the selected asset.
91
91
  - You can upload multiple assets at once, including files in nested folders, by browsing or dragging & dropping them into the media library[^5].
92
92
  - You can navigate between the global media folder and a per-collection media folder[^6].
@@ -99,9 +99,9 @@ While it’s not our goal to recreate all the features found in Netlify/Decap CM
99
99
  | --- | --- |
100
100
  | Installation | Installing with npm is not supported yet. |
101
101
  | UI locales | Only English and Japanese are available at this time. No registration is needed. While the UI locale is automatically selected depending on the browser’s language settings, it can be changed in Settings. (Click on the Account button in the top right corner of the CMS.) |
102
- | Account | Only the [GitHub backend](https://decapcms.org/docs/github-backend/) is available at this time. You can keep using Netlify or a [3rd party OAuth client](https://decapcms.org/docs/external-oauth-clients/) (or [our own](https://github.com/sveltia/sveltia-cms-auth)) to sign in with GitHub, just like Netlify/Decap CMS. The GitLab backend is coming soon. We plan to add the Test backend as well for our demo site, but Azure and Bitbucket are unlikely to be supported, mainly due to the lack of an API method to fetch content in bulk. Later we may implement a performant Git Gateway alternative using GraphQL. |
102
+ | Account | Only the [GitHub backend](https://decapcms.org/docs/github-backend/) is available at this time. You can keep using Netlify or a [3rd party OAuth client](https://decapcms.org/docs/external-oauth-clients/) (or [our own](https://github.com/sveltia/sveltia-cms-auth)) to sign in with GitHub, just like Netlify/Decap CMS. The GitLab backend is coming soon. We plan to add the Test backend as well for our demo site, but Azure, Bitbucket and Git Gateway will probably not be supported, mainly due to the lack of a method to fetch content in bulk. We have not looked into the relatively new Gitea backend yet. Later we may implement a performant Git Gateway alternative using GraphQL. |
103
103
  | Configuration | Supported. |
104
- | Media | External media storage services are not supported yet. |
104
+ | Media | External media storage services are not supported yet. Deprecated Netlify Large Media won’t be added. |
105
105
  | Editorial Workflow | Not supported yet. |
106
106
  | Collections | Supported. |
107
107
  | Widgets | [See below](#widget-limitations) for the current limitations. |
@@ -113,19 +113,19 @@ While it’s not our goal to recreate all the features found in Netlify/Decap CM
113
113
  | Widget | Status in Sveltia CMS |
114
114
  | --- | --- |
115
115
  | Code | Not supported yet. |
116
- | Color | It’s a native `<input>` element at this time. The `enableAlpha` option is not supported yet. |
117
- | Date/DateTime | These are also native `<input>` elements. The `date_format` and `time_format` options with Moment.js tokens are not supported yet. We may deprecate the Moment.js format support anyway. |
116
+ | Color | The `enableAlpha` option is not supported yet. |
117
+ | Date/DateTime | The `date_format` and `time_format` options with Moment.js tokens are not supported yet. We may deprecate the Moment.js format support anyway. |
118
118
  | File/Image | Field-specific media folders and media library options are not supported yet other than `media_library.config.max_file_size` for the default media library. |
119
119
  | Map | Not supported yet. |
120
120
  | Markdown | It’s a plain text editor at this time. A rich text editor is coming soon. |
121
- | Relation | The `search_fields` options is not supported yet. |
121
+ | Relation | The `search_fields` option is not supported yet. |
122
122
 
123
123
  ### Beta features in Netlify/Decap CMS
124
124
 
125
125
  | Feature | Status in Sveltia CMS |
126
126
  | --- | --- |
127
127
  | Working with a Local Git Repository | Supported. [See below](#work-with-a-local-git-repository) for details. |
128
- | GitLab and BitBucket Editorial Workflow Support | The GitLab backend is not supported yet. No plan to support BitBucket. |
128
+ | GitLab and BitBucket Editorial Workflow Support | Editorial workflow is not supported yet. |
129
129
  | i18n Support | Supported. In fact, i18n is at the core of Sveltia CMS! |
130
130
  | GitHub GraphQL API | Supported. Sveltia CMS uses GraphQL by default for a better performance. It cannot be disabled. |
131
131
  | GitLab GraphQL API | The GitLab backend is not supported yet. |
@@ -168,7 +168,7 @@ While it’s not our goal to recreate all the features found in Netlify/Decap CM
168
168
 
169
169
  ### New users
170
170
 
171
- Currently, Sveltia CMS is aimed at existing Netlify/Decap CMS users. If you don’t have it yet, follow [their documentation](https://decapcms.org/docs/add-to-your-site/) to add it to your site and create a configuration file first. Then migrate to Sveltia CMS as described below.
171
+ Currently, Sveltia CMS is only intended for existing Netlify/Decap CMS users. If you don’t have it yet, follow [their documentation](https://decapcms.org/docs/add-to-your-site/) to add it to your site and create a configuration file first. Then migrate to Sveltia CMS as described below.
172
172
 
173
173
  As the product evolves, we’ll implement a built-in configuration editor and provide comprehensive documentation to make it easier for everyone to get started with Sveltia CMS.
174
174
 
@@ -179,7 +179,7 @@ Here are some starter kits for popular frameworks created by community members.
179
179
 
180
180
  ### Migration
181
181
 
182
- If you’re already using Netlify/Decap CMS with the GitHub backend and don’t have any custom widget, custom preview or plugin, migrating to Sveltia CMS is super easy. Edit `/admin/index.html` to replace the CMS `script` tag, and push the change to your repository:
182
+ Have a look at the [compatibility chart](#compatibility) above first. If you’re already using Netlify/Decap CMS with the GitHub backend and don’t have any custom widget, custom preview or plugin, migrating to Sveltia CMS is super easy. Edit `/admin/index.html` to replace the CMS `script` tag, and push the change to your repository:
183
183
 
184
184
  ```diff
185
185
  -<script src="https://unpkg.com/netlify-cms@^2.0.0/dist/netlify-cms.js"></script>
@@ -205,11 +205,12 @@ You can use Sveltia CMS with a local Git repository, like the [beta feature](htt
205
205
  1. Click “Work with Local Repository” and select the project’s root directory once prompted.
206
206
  1. Make some changes to your content on Sveltia CMS.
207
207
  1. See if the produced changes look good using `git diff` or a GUI like [GitHub Desktop](https://desktop.github.com/).
208
+ 1. Open the dev site at `http://localhost:[port]/` to check the rendered results.
208
209
  1. Commit and push the changes if satisfied, or discard them if you’re just testing.
209
210
 
210
211
  ### Use a custom icon for a collection
211
212
 
212
- As shown in the screenshot above, you can use different icons for collections in Sveltia CMS.
213
+ You can have an icon for each collection for easy identification in the collection list.
213
214
 
214
215
  1. Visit the [Material Symbols](https://fonts.google.com/icons?icon.set=Material+Symbols&icon.platform=android) page on Google Fonts.
215
216
  1. Search and select an icon, and copy the icon name displayed on the right panel.