-
Notifications
You must be signed in to change notification settings - Fork 4
Frontmatter support #10
Comments
Hi, @krry! The reason you're not able to add frontmatter is because of the way NextJS had set up their MDX support in |
Definitely not abandoned but my plate is also kinda full this month. |
Ah, thank you for this context! Continuing to attempt to solve this last night I also landed at next-mdx-remote for frontmatter support, and then ran into the nesting issue. I'll of course share any progress I make. |
I've updated my PR if you want to take a look @krry. You could modify the Layout and pass the frontmatter data from local mdx files. |
Aw, rad @zomars, thanks. I have recycled a lot of your PR in my app at this point, checking out the latest. |
Hiya, and thank you for this template 😸
I'm wondering if it supports/parses frontmatter, or could. Foam now allows us to put tags and such in the frontmatter, which I have started to do as another dimension of interlinkage.
And when I display my notes that contain frontmatter with this template, I see the frontmatter printed as though it were a horizontal line
---
, a<p>
, then a<h2>
. I don't understand why it is parsed this way.Here is an illustration. This markdown:
becomes this markup:
So far I have tried to adding the
remark-frontmatter
plugin in thenext.config.js
as you instruct, and in combination with theremark-parse-frontmatter
plugin. These seem to have no effect.I'm stumped. Have you gotten frontmatter parsing to work? Do you have any pointers?
Thanks again. It's so great to be able to use Next and Vercel to publish my second brain.
The text was updated successfully, but these errors were encountered: