@sveltia/cms 0.2.0 → 0.2.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 CHANGED
@@ -16,8 +16,8 @@ Sveltia CMS is a Git-based lightweight headless CMS partially compatible with [N
16
16
 
17
17
  Sveltia CMS is a Git-based lightweight headless CMS, which means:
18
18
 
19
- - Git-based: Your content is saved as static JSON, YAML or TOML files on a Git repository. No database or API is involved.
20
- - Lightweight: The app is compiled as a single small JavaScript file served via a CDN. You don’t have to sign up for a service or install the software.
19
+ - Git-based: Your content is saved as static JSON, YAML or TOML files on your Git repository. No database or API is involved. Your data is yours.
20
+ - Lightweight: The app is compiled as a single small JavaScript file served via a CDN. You don’t have to sign up for a service or install additional software.
21
21
  - Headless: The CMS only takes care of raw data. You can read it and render the final content with your favourite framework.
22
22
 
23
23
  Here are some highlights mainly compared to Netlify/Decap CMS:
@@ -36,7 +36,7 @@ Here are some highlights mainly compared to Netlify/Decap CMS:
36
36
 
37
37
  ### Better performance
38
38
 
39
- - Built completely from scratch with [Svelte](https://svelte.dev/) rather than forking React-based Netlify/Decap CMS. The app starts fast and stays fast.
39
+ - Built completely from scratch with [Svelte](https://svelte.dev/) rather than forking React-based Netlify/Decap CMS. The app starts fast and stays fast. The compiled code is vanilla JavaScript; you can use it with any framework.
40
40
  - Using the GraphQL API for GitHub by default to fetch contents quickly at once, so showing and searching entries and media are now instant. Saving entries and media is also much faster.
41
41
  - Small footprint: less than 250 KB when minified and gzipped, compared to 1.5 MB of Netlify/Decap CMS.
42
42
 
@@ -73,7 +73,7 @@ While we’re not recreating all the features found in Netlify/Decap CMS, our pl
73
73
  | Feature | Status in Sveltia CMS |
74
74
  | --- | --- |
75
75
  | UI locales | Only English and Japanese are available at this time. No registration is needed. It can be changed in Preferences. |
76
- | Account | Only the 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 OAuth client](https://github.com/sveltia/sveltia-cms-auth)) to sign in with GitHub, just like Netlify/Decap CMS. GitLab could be supported later, but other backends are unlikely to be added, mainly due to the lack of an API method fetching contents in bulk. We’ll support the `test-repo` backend for a demo site. |
76
+ | 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 client](https://github.com/sveltia/sveltia-cms-auth)) to sign in with GitHub, just like Netlify/Decap CMS. GitLab could also be supported, but the Azure, Bitbucket and Git Gateway backends are unlikely to be added, mainly due to the lack of an API method fetching contents in bulk. We plan to add support for the [Test backend](https://decapcms.org/docs/test-backend/) for our demo site and perhaps implement a performant Git Gateway alternative using GraphQL. |
77
77
  | Configuration | Supported. |
78
78
  | Media | External media storage services are not yet supported. |
79
79
  | Editorial Workflow | Coming soon. |
@@ -102,7 +102,7 @@ While we’re not recreating all the features found in Netlify/Decap CMS, our pl
102
102
  | Working with a Local Git Repository | Supported. [See below](#work-with-a-local-git-repository) for details. |
103
103
  | GitLab and BitBucket Editorial Workflow Support | The GitLab backend is not yet supported. No plan to support BitBucket. |
104
104
  | i18n Support | Supported. In fact, i18n is at the core of Sveltia CMS! |
105
- | GitHub GraphQL API | Sveltia CMS uses GraphQL with no configuration. It cannot be disabled. |
105
+ | GitHub GraphQL API | Sveltia CMS uses GraphQL with no configuration for a better performance. It cannot be disabled. |
106
106
  | GitLab GraphQL API | The GitLab backend is not yet supported. |
107
107
  | Open Authoring | Not yet supported. |
108
108
  | Folder Collections Path | Not yet supported. |