The App Router makes it possible to keep most content rendering on the server, but a CMS integration can still introduce unnecessary requests and client code if boundaries are chosen carelessly.

Start with the friction

  • Fetch content close to the server-rendered route that uses it.
  • Keep editing metadata out of the public client bundle.
  • Use explicit media dimensions and a controlled rich-text renderer.

Make the next revision useful

Profile the published page rather than the dashboard. A fast editing interface and a fast public website are related design goals, but they require separate checks.

The goal is not to add more activity. It is to make the next decision clearer, then verify whether the change helped.

THAT’S THE NOTE

Want to talk through how this applies to your website?

Tell me what you’re working on