Version 10.10.0 release notes
Discover the key enhancements and fixes in Front Matter CMS version 10.10.0, including smart file rename, front matter validation, and integrated browser preview support.
Published:
This release focuses on quality improvements across content editing, validation, and previews.
Highlights
- Smart rename support now helps keep filenames in sync with front matter data.
- Front matter schema validation for markdown files is now supported and can be disabled with the
frontMatter.validation.enabledsetting. - Preview support now works with the integrated VS Code browser.
- The chatbot command and related functionality have been removed.
- Sponsor AI setting support via
frontMatter.sponsors.ai.enabledhas been removed.
Front matter schema validation for markdown files
Issue #990 adds schema validation diagnostics for front matter in markdown files.
When validation is enabled, Front Matter validates your front matter against the active content type schema and reports problems directly in VS Code diagnostics.
This helps catch issues such as:
- Missing required fields
- Invalid value types (for example using a string where a number is expected)
- Invalid choice values for select-style fields
- Values outside configured constraints
You can turn this behavior on or off with the frontMatter.validation.enabled setting.
{
"frontMatter.validation.enabled": true
}
InfoThis setting is enabled by default.
Smart rename action for content files
Issue #545 introduces a dedicated Smart rename action that regenerates the filename from front matter data and keeps file naming consistent.
You can use Smart rename from:
- The Front Matter panel action bar
- The content dashboard item actions menu
How it behaves:
- Uses the configured title field as source to generate a clean filename
- Applies the configured file prefix logic when applicable
- Supports both regular files and page bundles (folder rename)
- Skips rename when the filename is already in sync
- Prevents rename when a target file/folder with the same name already exists
InfoThis action is useful when legacy content or manual edits caused filename drift. It complements the
frontMatter.taxonomy.alignFilenamesetting, which keeps filenames synced when generating/updating slugs.
For additional slug and filename sync options, check the slug documentation.
Related issues/enhancements
🎨 Enhancements
- #545: Add smart rename action to sync filename with front matter data
- #937: Dashboard "Structure" view for documentation sites WIP
- #965: Added SEO support for the keyword in the first paragraph
- #973: Support for number fields in the snippets
- #990: Schema and validation for front matter in markdown files. It can be turned off by the
frontMatter.validation.enabledsetting. - #1005: Support the integrated VSCode browser for the preview command
- #1017: Allow adding new values for custom taxonomy fields
🐞 Fixes
- #950: Fix for template is not applied to new content type when created
- #958: Fix variable frontmatter leads to error
- #964: Fix settings page for dark themes
- #969: Fix typo on welcome screen
- #972: Fix content view sorting for Modified Date not working as expected
- #979: Fix unwanted automatic updates in the publishDate field of TOML front matter
- #984: Fix in
frontMatter.global.timezoneis invalid - #1004: Fix for
mediaDB.jsoncontaining full paths on Windows instead of relative paths - #1006: Fix output channel colorizer schema to only apply to the Front Matter output channel

