get pages frontmatter from remark plugin instead of additional frontmatter package

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

Currently there is a secondary plugin needed to extract the frontmatter from a markdown file, in addition the existing remark-frontmatter plugin, which (in theory) should be able to get it for already.

const settings = config.markdown.settings || {};
const fm = frontmatter(markdownContents);  // one plugin

processedMarkdown = await unified()
  .use(remarkParse, settings)
  .use(remarkFrontmatter) // another one here
  .use(remarkPlugins)
  ....
  .process(markdownContents);

if (fm.attributes) {
  // do stuff
}

Details

It would be great to just get everything from processedMarkdown directly, instead of needing a second package just to get the frontmatter. From the docs, this should be possible, but I was having issues when I tried it initially, but hopefully by now we can figure it out. 🤞

[thescientist13]

As we are extracting frontmatter within Greenwood itself, and as part of #1457 all the markdown plugins are getting moved out of the CLI, this will dependency will be removed as part of that PR.

---

I think there could be an interesting discussion around not supporting frontmatter at all in the Greenwood CLI, but that discussion can come at another time.

---

edit: actually, we do need that frontmatter plugin otherwise frontmatter will start turning up as HTML. Woops! 😅

• https://github.com/ProjectEvergreen/greenwood/actions/runs/17358888803/job/49276026361
• https://github.com/ProjectEvergreen/greenwood/pull/1457/commits

So we it was never duplicated really; we needed it unified to get rid of the frontmatter, as well as to actually extract frontmatter values for the graph.

So I guess we can actually cancel this issue then 👍