dtedesco1

> taking care of all the hairy details around `<CustomComponent>...</...>`

Precisely! Thank you.

Can you share more about what you have in mind for frontmatter? I don’t really understand the need/use cases yet.

Bingo!

Thanks for calling out. I’ve opened [an issue to look into this](https://github.com/dtedesco1/nextjs-markdown-boilerplate/iss...).

Awesome work. Very snappy and crisp. For this project, I’m still stuck in React hell though because I want to use React components XD

This is great! Thanks for sharing.

I actually previously used Jekyll! Built this largely because I want full React component functionality sometimes. Also I think Jelyll gave me some issues with routing that I didn’t like.

These are great for adding more flavor to md -> html, but I want to be able to use React components sometimes, not just JS/CSS.

You’re getting close. The biggest thing is that I want to be able to use React components sometimes and anywhere on the page. If you just want md -> html, there are of course much better options.

Yep, but I still want to use React components sometimes. That’s my biggest holdup.

These look really promising! Can I bring existing React components with me to any of them? That might be the biggest hold up. I’d also worry about maintainability as web standards evolve, since these (mostly) seem like pretty small projects.

Can I still bring my React components when I want them? Haven’t tried out HTMX yet.

Intriguing. Does it render React components when you want to add them?

Ha! I would love that.

Haven’t gotten this feedback from anyone else. Are you using a browser extension(s) that might be affecting how it renders?

Agreed! Give me a better option that supports React components?

but nextjs is in the title… :)

Does Obsidian support React components when you want to add them? That’s my biggest issue.

That’s good if I’m really *only* ever using Markdown. But what about wanting to use React components sometimes? That’s my biggest problem.

It’s the I-sometimes-want-to-use-React-components issue that is my holdup. They make it easy to do some visual/behavioral stuff and are often directly portable from other sites or oss projects.

This makes sense for one-way posting, but there are two issues for my main use case (personal and small company websites):

1. I want to edit the pages sometimes, and I want to do so using markdown without extra steps.

2. I still want to use React components *sometimes*.

3. I want it to be really easy to deploy and monitor. Nextjs is really easy for those things.

Solving the first issue and third issues don’t require React, but the second definitely does. So I’m still stuck.

I agree, but it's just too difficult to get away from the React ecosystem...

Do you have suggestions on a better alternative?

I wanted a dumb & simple way to make a modern website with text files, so I made one. Small, static-first Next.js boilerplate, intentionally minimal, just markdown → website, with optional React components when you want them.

Just updated it; what’s new:

• Next.js 15.5.2 + React 19.1.1 • Better typing for error boundaries (React 19) • Robust handling for Next 15 async params • Updated DaisyUI, MDX, and tooling

Use it for docs, personal sites, landing pages, or simple content sites that still want modern Next.js ergonomics.

Given you have an existing website, it might be easier for you to add Markdown support to your site through a static site generator or server-side conversion step.

Or you can even use a Markdown-to-HTML tool (I believe pandoc has this feature) to convert the pages yourself before posting. That's a bit more manual but wouldn't require changing your current structure.

Anyway, if you end up using boilerplate, let me know what you think!

Three main reasons, two functional and one practical:

1. Built-in MDX support means you can seamlessly mix Markdown and React components. (I previously had some trouble with the @mdx-js/react library and was in the market for more native solutions.)

2. Next.js makes it pretty easy to do modern web stuff, like client/server components and Tailwind/DaisyUI styling.

3. With Vercel spending so much getting YouTubers to create general Next.js tutorials, I found it very easy to get this set up.

If you're dealing with purely static Markdown content, I would recommend something simpler.

Since I don't post about myself much on social media and I'm a bad correspondent, it's been a really wonderful way to keep in touch. Also, seeing myself change over time and hearing back from long lost friends are added benefits.