Version 10.11.0 release notes

This release adds a new Content Health section in the editor panel, more control over the contents dashboard, richer data file fields, a configurable slug separator, and freeform taxonomy validation.

Highlights

• New Content Health section in the panel with readability scoring, link checks, and freshness warnings.
• Configure the default sorting, grouping, and filters for the contents dashboard.
• Output multiple properties from a data file in the dataFile field type.
• Customize the slug separator with the new frontMatter.file.slugSeparator setting.
• Freeform tags and categories are no longer flagged by front matter validation.

Content Health section in the editor panel

This release adds a new Content Health section to the Front Matter panel for supported content files.

The section provides:

• A readability score (Flesch Reading Ease)
• Internal link validation
• Optional external link validation
• A freshness warning when content is older than your threshold

The feature can be configured with the new settings:

• frontMatter.contentHealth.enabled (default: true)
• frontMatter.contentHealth.checkExternalLinks (default: false)
• frontMatter.contentHealth.freshnessThreshold (default: 180 days)
• frontMatter.contentHealth.minReadability (default: 0, disabled)

{
  "frontMatter.contentHealth.enabled": true,
  "frontMatter.contentHealth.checkExternalLinks": false,
  "frontMatter.contentHealth.freshnessThreshold": 180,
  "frontMatter.contentHealth.minReadability": 45
}

Info

Check the panel documentation for more information.

Configure the default contents dashboard state

Issue #1036 adds the frontMatter.dashboard.content.defaults setting.

With this setting, you can preconfigure:

• The default sorting option
• The default grouping mode
• The default filter values

{
  "frontMatter.dashboard.content.defaults": {
    "sorting": "LastModifiedDesc",
    "grouping": "Year",
    "filters": {
      "contentFolders": "docs",
      "tags": "release",
      "categories": "guides"
    }
  }
}

This is useful when you want the contents dashboard to always open in a project-specific view instead of starting from the unfiltered default state.

Output multiple properties from a data file

Issue #409 adds the dataFileAdditionalFields property to the dataFile field type.

By default, only the dataFileKey value (for example the slug) is stored in the front matter. With dataFileAdditionalFields, you can store additional fields from the selected data record as an object.

{
  "title": "Authors",
  "name": "authors",
  "type": "dataFile",
  "dataFileId": "authors",
  "dataFileKey": "name",
  "dataFileValue": "name",
  "dataFileAdditionalFields": ["slug"]
}

Info

Check the dataFile field documentation for more information.

Configurable slug separator

Pull request #1030 adds the frontMatter.file.slugSeparator setting, which lets you customize the separator character used when generating slugs from titles. By default, hyphens (-) are used.

{
  "frontMatter.file.slugSeparator": "_"
}

Info

Check the slug documentation for more information.

Freeform tags and categories validation

Issue #1033 aligns front matter validation with the frontMatter.panel.freeform setting. When freeform is enabled (the default), tags and categories that are not part of your known taxonomy are allowed and no longer flagged as validation errors. When freeform is disabled, the generated schema restricts these fields to the known taxonomy values.

Related issues/enhancements

🎨 Enhancements

• Support fieldGroup as a single value on fields fields
• Added the new content health feature to the Front Matter panel with readability scoring, link checks, and freshness warnings (frontMatter.contentHealth.enabled, frontMatter.contentHealth.checkExternalLinks, frontMatter.contentHealth.freshnessThreshold, frontMatter.contentHealth.minReadability)
• #409: Added the ability to output multiple properties from a data file in the dataFile field type
• #1030: Add frontMatter.file.slugSeparator setting
• #1033: Support freeform tags and categories in the front matter validation
• #1036: Default filter, sorting, and grouping configuration for the contents dashboard

🐞 Fixes

• #905: Fix Hugo framework detection for sites using hugo.toml, hugo.yaml, hugo.yml, or hugo.json (the default config filename since Hugo v0.110)
• Fix number fields not being saved to front matter when used inside block field groups
• #920: Fix metadata.fmRelFilePath returning an absolute path on Windows by normalizing the workspace folder path before stripping it
• #963: Prevent infinite update loops for fields when using Hugo partials as values in the front matter
• #1041: Fix in image page when using page bundles