Depending on the project, frontmatter objects can get pretty big and there are essentially two kind of keys:
things used by brut (template, published_date, permalink, title, buildScript[^1], possibly others like is_draft, excerpt, or updated_date in the future, etc.)
It would be nice to isolate one from the other. It makes things clearer and avoids scenarios where brut introduces a new key that clashes with an existing custom one.
Custom frontmatter could be under data for example:
title: My post
published_date: 2024-08-16
data:
subtitle: Look at what I wrote today
featured_image: cat.jpg
Depending on the project, frontmatter objects can get pretty big and there are essentially two kind of keys:
template
,published_date
,permalink
,title
,buildScript
[^1], possibly others likeis_draft
,excerpt,
orupdated_date
in the future, etc.)featured_image
,subtitle
)It would be nice to isolate one from the other. It makes things clearer and avoids scenarios where brut introduces a new key that clashes with an existing custom one.
Custom frontmatter could be under
data
for example:(Inspired by Cobalt again: https://github.com/cobalt-org/cobalt.rs/issues/257)
[^1]: this might get deprecated soon