@sveltia/cms 0.38.1 → 0.38.2
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 -1
- package/dist/sveltia-cms.js +102 -102
- package/dist/sveltia-cms.mjs +110 -110
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -454,7 +454,7 @@ You can use Sveltia CMS with a local Git repository like Netlify/Decap CMS, but
|
|
|
454
454
|
- You can remove `local_backend` from your configuration, as it will be ignored by Sveltia CMS.
|
|
455
455
|
1. Launch the local development server for your frontend framework, typically with `npm run dev` or `pnpm dev`.
|
|
456
456
|
1. Visit `http://localhost:[port]/admin/index.html` with Chrome or Edge. The port number varies by framework.
|
|
457
|
-
- Other Chromium-based browsers may also work.
|
|
457
|
+
- Other Chromium-based browsers may also work. Brave user? [See below](#enable-local-development-in-brave).
|
|
458
458
|
1. Click “Work with Local Repository” and select the project’s root directory once prompted.
|
|
459
459
|
- If you get an error saying “not a repository root directory”, make sure you’ve turned the folder into a repository with either a CUI ([`git init`](https://github.com/git-guides/git-init)) or GUI, and the hidden `.git` folder exists.
|
|
460
460
|
- If you’re using Windows Subsystem for Linux (WSL), you may get an error saying “Can’t open this folder because it contains system files.” This is due to a limitation in the browser, and you can try some workarounds mentioned in [this issue](https://github.com/coder/code-server/issues/4646) and [this thread](https://github.com/sveltia/sveltia-cms/discussions/101).
|
|
@@ -467,6 +467,14 @@ Keep in mind that the local repository support doesn’t perform any Git operati
|
|
|
467
467
|
|
|
468
468
|
Also, at this point, you have to reload the CMS to see the latest content after retrieving remote updates. This manual work will be unnecessary once the proposed `FileSystemObserver` API, which is being [implemented in Chromium](https://issues.chromium.org/issues/40105284) behind a flag, becomes available.
|
|
469
469
|
|
|
470
|
+
#### Enable local development in Brave
|
|
471
|
+
|
|
472
|
+
In the Brave browser, you must enable the File System Access API with an experiment flag to take advantage of local development.
|
|
473
|
+
|
|
474
|
+
1. Open `brave://flags/#file-system-access-api` in a new browser tab.
|
|
475
|
+
1. Click Default (Disabled) next to File System Access API and select Enabled.
|
|
476
|
+
1. Relaunch the browser.
|
|
477
|
+
|
|
470
478
|
### Using a custom icon for a collection
|
|
471
479
|
|
|
472
480
|
You can specify an icon for each collection for easy identification in the collection list. You don’t need to install a custom icon set because the Material Symbols font file is already loaded for the application UI. Just pick one of the 2,500+ icons:
|