Production

Your CMS needs a content-ready checklist, not a save button

By Jasper

Most CMSs let you save incomplete work

You can click "Save Draft" with an empty title, no image, and a body that's three words long. The system doesn't care. It stores whatever you give it. That's fine for actual drafts, but it's a problem when you're trying to publish.

The gap between "I can save this" and "this is ready to go live" is where bad content happens. You meant to come back and add the excerpt. You forgot to check the category. You left the placeholder image in place. The publish button was right there, and you clicked it.

A checklist surfaces what's missing

Before you can mark something ready to publish, the system should show you what's incomplete. Not as an error message after you try to save—as a visible list while you're working.

  • Title filled in
  • Excerpt written
  • Featured image uploaded
  • Category assigned
  • At least one tag selected
  • Body text over 200 words

You see what's checked off and what isn't. You don't have to remember the steps. The interface remembers for you.

This isn't about blocking you from saving. You can still save a draft with half the checklist empty. But you can't move it to "Ready for Review" or "Scheduled" until everything's done. The status change is gated by completion, not by whether you remembered to do the work.

Build it into your workflow states

If your CMS has custom publish statuses, tie the checklist to the transition between them. Moving from "Draft" to "Ready for Review" runs the check. Moving from "In Review" to "Scheduled" runs it again.

Different content types can have different checklists. A blog post needs an excerpt and a featured image. A landing page needs a meta description and a primary CTA. A case study needs a client name and a project date. The checklist adapts to what you're actually publishing.

Some fields are always required. Others are conditional—if you pick "External Link" as the post type, the checklist adds "Destination URL" and removes "Body Text." The system knows what complete looks like for each scenario.

Make the checklist visible, not hidden

Don't bury this in a validation error that only appears when someone tries to publish. Show the checklist in the sidebar while they're editing. Let them see progress as they work.

If the featured image is missing, the checklist shows "Featured image: not set" with a link directly to the upload field. If the excerpt is empty, it shows "Excerpt: not written" and focuses the excerpt box when you click it. Each incomplete item is a shortcut to fixing it.

This is especially useful for teams. An editor can glance at the checklist and immediately see what the writer forgot. They don't have to read the whole post to spot the gaps. The checklist is a handoff tool as much as a quality gate.

Start with the minimum checklist

You don't need to enforce every possible content standard on day one. Start with the fields that cause the most problems when they're missing—usually title, category, and featured image.

Add to the checklist as you find gaps. If people keep forgetting to write excerpts, add excerpts. If posts keep going live without tags, add tags. Let your actual mistakes shape the list. Don't try to anticipate every possible failure upfront.

The checklist isn't a rulebook. It's a safety net. It catches the things you meant to do but didn't, before they go live and embarrass you.

A save button just stores data. A checklist makes sure the work is actually finished.

← All posts