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.
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.