7 reasons why I switched to MDX for My Blog, and why you should too

Photo of the author, Morgan Feeney

Morgan Feeney

2 min read

I used to rely on a CMS for all my blogging needs, but after working with MDX for over a year, I know firsthand how it’s a smart choice for developers.

  1. Unmatched Freedom: With MDX, I've found a level of creative and technical freedom that surpasses traditional CMS limitations.
  2. React friendly: MDX merges markdown with React code (JSX), allowing me to add completely custom components directly in markdown files, and position them anywhere I want.
  3. Fewer dependencies: I have fewer moving parts to deal with now, no CMS integration, no backend to manage, and no related libraries that I need to keep up to date. This is great when you work locally.
  4. Learning and growth: Using MDX has been a rewarding learning experience, enhancing my dev skills, and opening my eyes to what's possible from a blog authoring experience.
  5. Customisation: Unlike rigid CMS structures, MDX is highly customisable, when combined with contentLayer you can create type-safe schemas for React props, and add any props you want.
  6. Ease of use: For those who already use Markdown, MDX is straightforward to slide into. If you've not used it before, don't worry, it's really easy to pick up, and well documented.
  7. Cost-effective: You can get free hosting with Vercel and others such as Cloudflare 💰💰, moreover, MDX can reduce or completely eliminate CMS hosting, you won't need it as no backend is needed with MDX.