You are currently viewing the BETA version of Front Matter documentation. Click on the banner to go to the main release documentation.

Version 10.5.0 release notes

Discover the key features and enhancements in Version 10.5.0, including new options for content management and improved language file handling.

Published: Oct 21, 2024

New exclude paths option for the content folder settings

You can now exclude specific path(s) from the content folder by specifying a list of paths in the excludePaths option. You can make use of wildcards to exclude folders.

Example of the excludePaths option

{
  "frontMatter.content.pageFolders": [
    {
      "title": "Documentation",
      "path": "[[workspace]]/docs",
      "excludePaths": [
        "api", // Exclude the api folder
        "_*.*" // Exclude all files starting with an underscore
      ]
    },
}

Info

You can find more information about the content folder settings in the content folders documentation.

Extended i18n/language button to open or create new language files

You can now open or create new language files directly from the i18n/language button. This feature allows you to manage your language files more efficiently.

i18n language selection experience

Thanks to Dennis Zoma for contributing to this enhancement.

Info

You can find more information in the multilingual documentation.

New same content locale option for the contentRelationship field

You can now specify to use the same content's locale for the contentRelationship field by using the sameContentLocale option. The default behavior is to use the current content's locale.

Example of the sameContentLocale option

{
  "title": "Session",
  "name": "session",
  "type": "contentRelationship",
  "contentTypeName": "session",
  "contentTypeValue": "slug",
  "sameContentLocale": false // Default behavior is set to `true`
}

Thanks to Dennis Zoma for contributing to this enhancement.

Info

You can find more information about the contentRelationship field in the fields documentation.

Support Markdown in the WYSIWYG string field

You can now use Markdown in the WYSIWYG string field. By default the WYSIWYG option is returning HTML, but you can now switch to Markdown.

Example of the WYSIWYG string field with Markdown support

{
  "title": "Markdown field",
  "name": "markdownField",
  "type": "string",
  "wysiwyg": "markdown"
}

Info

You can find more information about the string field in the fields documentation.

🎨 Enhancements

#840: Added the excludePaths option for the content folder settings
#850: Extended the i18n/language button to open or create new language files
#851: Added sameContentLocale option to contentRelationship field
#866: Support Markdown in the WYSIWYG string field

🐞 Fixes

#858: Fix button styling on the data screen
#860: Fix typo on the data screen
#870: Fix data number field styling