← Creative

Give every public page an intentional destination

By Redstart Media

A public route should identify an approved content record, not whatever happens to be in a working folder.

Give the route a clear owner./ideas/a-useful-lessonApproved Creative recordIts example, visual, and linksAn intentional public destination.The route and the content should describe the same destination.

Choose which content will be public and give each page a deliberate address. A file’s presence in a working folder does not establish that it is ready for the public. In Redstart’s current system, PostgreSQL records and explicit route relationships identify the public content, while the application owns delivery behavior. A route catalog records these deliberate connections between public addresses and content. It allows the team to know which record a link represents and the reader to return to that record without understanding its internal storage.

Connect the public route to the intended record.

A working folder may contain drafts, experiments, and approved pages. Treating all of them as public would confuse storage with a publishing decision. An explicit list of public routes makes that decision visible and gives each approved page a deliberate address. A new Creative is stored with its worked example and canonical article route in one audited database operation. The index, search result, and detail page then refer to that same identity. A temporary note elsewhere on disk is not a second version of the Creative and should not be used as its publishing mechanism.

Choosing the public records explicitly helps both readers and the people maintaining the site. The audience receives a coherent collection of working destinations; the maintainers can trace a page back to its actual record. Keep the route decision explicit without adding unnecessary ceremony to routine content creation. Check that the intended content exists in the database and reaches readers correctly through the application.

Put it into practice.

Save the primary public address with the complete content record, and keep useful older or alternative addresses working. Check that the destination resolves to the intended record and that public links use the deliberate route. Keep operational material and incidental files outside the public content collection. In this site, creating a complete supported Creative record and its route makes it available through the existing application; there is no separate file-based publication step to invent.

What makes this page ready to belong in the public collection?

Our work begins with people.