@sveltia/cms 0.92.5 → 0.93.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 +1 -0
- package/dist/sveltia-cms.js +187 -187
- package/dist/sveltia-cms.js.map +1 -1
- package/dist/sveltia-cms.mjs +202 -202
- package/dist/sveltia-cms.mjs.map +1 -1
- package/package.json +1 -1
- package/schema/sveltia-cms.json +5 -0
- package/types/public.d.ts +5 -0
package/README.md
CHANGED
|
@@ -339,6 +339,7 @@ Sveltia CMS has been built with a multilingual architecture from the very beginn
|
|
|
339
339
|
- If a collection only has the Markdown `body` field, an entry slug will be generated from a header in the `body`, if exists. This supports a typical VitePress setup.
|
|
340
340
|
- Entry slug template tags support [transformations](https://decapcms.org/docs/summary-strings/) just like summary string template tags.[^29]
|
|
341
341
|
- Single quotes (apostrophes) in a slug will be replaced with `sanitize_replacement` (default: hyphen) rather than being removed.[^52]
|
|
342
|
+
- The [global `slug` option](https://decapcms.org/docs/configuration-options/#slug-type) accepts the `trim` option to remove leading and trailing replacement characters, such as hyphens, from an entry slug. The default value is `true`. Set to `false` to keep them.
|
|
342
343
|
- The maximum number of characters for an entry slug can be set with the new `slug_length` collection option to avoid deployment errors with Netlify or other platforms.[^25]
|
|
343
344
|
- Setting the collection `path` doesn’t affect the entry slugs stored with the Relation widget.[^137]
|
|
344
345
|
- Entry slugs are [localizable](#localizing-entry-slugs).[^80]
|