contentlayer VS Next.js

Contentlayer to manage content logic

This looks and sounds great...

I'm currently using [contentlayer.dev](https://github.com/contentlayerdev/contentlayer) to manage docs and blog content, mostly .mdx files on urlbox.com.

It works well with next.js but unfortunately is abandonware now.

I also have a few custom remark/rehype plugins.

You're right it is a pain to update articles buried in your repo especially with less technical team members. I already tried out TinaCMS to try and solve the editing issues, but their editor wasn't so nice, and it seemed to implicitly make a commit on every tiny change to any content, so I'm really hoping I could use something like this to edit my already existing content...

Content Management: Contentlayer

For my personal website, I use Next and Contentlayer since I prefer to write my content as markdown files. I then host it using vercel's free tier.

I've seen https://www.contentlayer.dev/ used for similar stuff on open source codebases like taxonomy from shadcn

Contentlayer makes it super easy to grab our mdx blog posts in a type-safe way.

Flowershow uses Contentlayer to turn your Markdown content into data stored in JSON files. By defining document schemas, Contentlayer can generate data that is validated (making it type-safe) and can be imported from anywhere in your Next.js app.

My first reaction was to use MDX and use next/image just as in the example. But that means that we can't use normal markdown images and it turns out that this won't work with contentlayer. This wont work, because Next.js does some magic on the import of the static image. The object which gets returned by the import, contains not only a path to the image, it contains also the width and height, plus a very small version of the image for the blurred placeholder. This magic does not work if the MDX file is loaded with contentlayer, because contentlayer uses its own bundler, which does not know about the import magic for images.

6. Next.js + Vercel: The Full-Stack Framework That Actually Ships

You're minding your own business, managing AWS infrastructure for a client with a pretty standard e-commerce setup: a Medusa.js backend, a Next.js storefront, and most importantly for this story, a PostgreSQL RDS instance safely stashed away in a private subnet where nothing from the outside world can touch it. Exactly how the AWS gods intended.

Turbopack is now powering vercel.com, nextjs.org, and a growing number of real-world apps. It’s clearly the future written in Rust, blazing through cold builds, and supposedly replacing Webpack altogether.

next — Next.js framework providing SSR, routing, and server functions.

3. Next.js and React (Frontend framework)

My primary passion is backend development, but I wanted to build a user-friendly frontend to complete this project. Given my experience with React, Next.js was the obvious choice due to its excellent documentation and ease of use.

This is a Next.js project bootstrapped with create-next-app.

Official Example: Dynamic Imports