Porting legacy Frontmatter with FrontMatterRegexes?

[bellons91]

I'm porting my GatsbyJS blog to Statiq.Web.

All my article (~130) have the frontmatter set such as:

---
title: "How to customize Conventional Commits in a .NET application using GitHooks"
path: "/blog/conventional-commit-with-githooks"
tags: ["dotNET", "npm", "MainArticle"]
featuredImage: "./cover.png"
excerpt: "Using Conventional Commits you can define a set of rules useful for writing meaningful commit messages. Using NPM. Yes, in a dotNET application!"
created: 2023-02-07
updated: 2023-02-07
---

Since some of those section names are not supported, I have to write a custom FrontMatterRegexes - I suppose.

Where can I find some documentation and some examples?

The documentation does not provide any example

You can also customize the front matter styles using the following settings:

FrontMatterRegexes: Defines the default set of regular expressions used for identifying front matter. Changing this setting will overwrite the defaults above.
AdditionalFrontMatterRegexes: Defines additional regular expressions used for identifying front matter in addition to the defaults described above.

Any idea?

[daveaglick]

The front matter regex settings are only used in very advanced scenarios where you want to change the front matter delimiters (I.e. the --- lines that indicate the start and end of a front matter block. There's really no standard around how delimiting front matter should work, so by default Statiq tries to accommodate the most popular conventions allowing for both an initial --- and ending --- as well as just and ending --- without a starting delimiter (which itself can end up with some confusion - see statiqdev/Statiq.Framework#264).

In any case, coming from GatsbyJS you've already got the starting and ending --- which Statiq supports so there's no need to change anything there.

One thing that's different about Statiq over other static generators is that any front matter is valid front matter. Whatever YAML you add to front matter ends up as metadata for that document and can be retrieved. That doesn't mean a particular Statiq theme knows what to do with all of it, but the values will be there regardless. So in this case, no extra work is needed - this document will end up with metadata for all the values above, including those which are not "standard" metadata that the default themes understand. Does that make sense and answer your question?

[bellons91]

Ok, so if I understood correctly, I don't have to add configurations to Statiq.Web but rather to the theme I'm currently using - which is CleanBlog.