Most of Front Matter is configurable to your needs. In this part of the documentation all settings are explained.
Team settings and local settings
Since version 4 of Front Matter, Team settings got introduced. Teams settings allow you to have all
settings on the project/solution level. You will be able to override them on user/local level
The purpose of team settings is to share the global configuration of your CMS configuration. This way, your whole team can use the same tags/categories but apply their changes locally.
As you do not typically share your
.vscode/settings.json configuration, we went for a
frontmatter.json file on the root of your project/solution. The settings you provide in this JSON
file are the same as you can configure on a local level. This allows you to easily copy, move
settings from team to local level and vice versa.
Migrate local settings to team settings
To allow you to easily migrate already defined settings, you can run the
Promote settings from local to team level command. The very first time, it will also ask you if
there are settings that can be promoted.
Splitting your settings in multiple files
Some of the Front Matter settings can be split in multiple files to make management of these easier. For example, in case you are using multiple content-types for your site, you can now split each content-type to its own file. This allows you to easily manage the settings for each content-type.
Important: The configuration of the
frontmatter.jsonfile will override the settings which you might have splitted.
Supported settings to split
The following settings are supported to be split in multiple files:
|Setting name||Folder path||JSON Schema|
Important: The folder path is relative to the root of your project/solution and you create the files in their corresponding folder. The file name is the same as the
idof the setting.
You can use the JSON schema to validate and get intellisense for the settings. Use it as follows:
Example of splitting a setting
Example 1: Specify a blog page folder
Example of specifying a page folder in a separate file:
Contents of the
Example 2: Specify a custom data type
You are also able to define sub-folders for your settings, that way, you can easily group your
settings. For example, in this case we'll create a
baz data type in its own folder.
Contents of the
You can extend the settings of Front Matter by using the
frontMatter.extends setting. This allows
you to extend the settings from a custom local or remote location. This can be useful if you want to
share a common set of settings across multiple projects.
Reviewing composed settings
You can inspect your composed settings with the diagnostic logging command, which shows you the Complete frontmatter.json config in a virtual Markdown document. Use that output to verify that your split configuration settings are applied the way you expect.
Did you spot an issue in our documentation, or want to contribute? Edit this page on Github!