A Small Publishing Workflow That Scales With the Writer

Publishing systems become difficult when every state means the same thing. A draft, a review copy, and a published article should answer different questions for the person writing and maintaining the site. A draft is private working material. It can be incomplete, have temporary wording, and change often. The important feature is that saving a draft should be cheap and reliable. Writers should not have to make publication decisions every time they want to preserve an idea. Review is a useful state when another person or a later pass needs to inspect the article. It creates a deliberate pause between “the content exists” and “the content represents the site.” Even for a solo writer, review can mean checking links, headings, metadata, images, and the reading experience on a small screen. Published content needs stronger guarantees. It should have a publication date, a stable URL, complete metadata, and a clear way to return to the editor. Queries for public content should explicitly filter out drafts, archived items, and soft-deleted records. That rule belongs close to the data access layer so individual pages do not accidentally expose internal states. Revisions make the workflow forgiving. They provide an audit trail and let a writer change direction without losing the previous version. A revision does not need to become a complicated version-control system; storing the meaningful content and timestamp is already enough to make edits safer. The goal is a system that supports the act of writing instead of turning it into administration. Keep the states understandable, make saving dependable, and put publication checks at the boundary. A small workflow can remain pleasant for one writer while leaving room for more authors and richer review later.