← Creative

Model the work people actually do

By Redstart Media

Let real records and real editing needs determine the structure of a content system.

Model the work people actually do.What happens when a lesson changes?Creative recordTitleSummaryLessonModified datePageSearchPreviewOne real edit. Three consistent results.Add structure for an observed need, not an imagined workflow.

The records and fields in a content system should reflect information people actually maintain. Before adding a field, approval stage, or special case, identify the real decision it serves. Include enough structure to make editing predictable, without asking editors to follow steps that no real task requires.

Start with a real edit.

Consider an editor changing a Creative title and summary. The illustration puts those facts in one database-owned record, then branches to the article, search result, and preview. The editor should not have to find and correct three copies. The article, search result, and preview each use the same content for a different purpose.

Redstart’s content already belongs in PostgreSQL. Python reads that shared database to assemble pages, so creating a new Creative means creating its complete database records and relationships. Keeping the system simple means making those records easy to maintain and display through the agreed database, without postponing it or adding a separate file-based publication step.

Put it into practice.

Follow one real edit from its owning record to the page, preview, and search result. Store each fact once, define how pages and previews read it, and add fields or record types when editors need them for an actual task. Honor the chosen database architecture throughout that path.

Which real edit should become simpler because of this structure?

Our work begins with people.