The Website Content Editor Is a Different Problem

As I build the Blog Post Manager, I start thinking about editing the rest of the website.

Pages like Home, About, and Contact have information I may want to change without editing the page layout itself. That sounds similar to managing posts, but the content is organized differently and has different fields.

One idea, two kinds of content

The Blog Post Manager is built around posts: there is a title, a date, some tags, and a body. A website content editor needs to work with the information used by different pages, and those pages don’t all have the same shape.

I build a separate editor so I can explore that problem without making the blog manager responsible for everything.

It is still rough. Some of the content rendering is glitchy, and I haven’t settled on the best way to handle every page. But even an imperfect first pass shows me where the real complexity is.

Tools can grow alongside the site

The editor isn’t finished just because it has a form. It has to make the content easy to understand and save it in a way the website can actually use.

I’m learning that the editing experience is part of the website’s system, not an afterthought.