Demonstrating best practices that you invite other people to follow requires that you properly recognize the existing best practices. And if they are conflicting then you need to say why you picked one over the other.
When you do this you set a bar for other people to join the discussion--they will need to show examples rather than asserting the color for your bike shed.
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.
The Snapchat Pixy was an amazing drone that we loved in my family. And sad to hear that ALL of them are now recalled for fire risk.
If you missed this chapter in the drone world, Pixy was a fun yellow and very simple flying selfie machine. It had just a mode dial and a go button. My three-year-old (and anybody's) had no problem using it and having fun.
So sad to see this erased from history. And I don't know anything like it.
Can you imagine the US Treasury saying "Um, we made a deal with Blackrock and they bought all our treasuries. It's an exclusive deal and we're not letting anyone else buy treasuries now. Oh and p.s. the price is secret."
https://github.com/fulldecent/moodle-local_plugin_template/i...
I'm not sure why HN chopped it off