Content Approval: From Draft to Publication
· PoolByte Technology
What the "Save" button does on a site where more than one person enters content is very important. Will a draft be created, will the current page be changed immediately, or will the editor's approval be awaited? If the publication workflow is not determined, an incorrect price text or an incomplete announcement may be unintentionally made available to the public.
Identify states and transitions
Statuses such as draft, in review, published, and archived can be used. Write down the meaning of each situation and who can make which transition. Drupal Workflows description demonstrates the concepts of state and transition. A similar structure can also be established in a custom content panel according to business rules.
Specify specifically which version will be shown to the current visitor when a published page is edited. While the new change is waiting in the draft, the old approved version may remain live. The “Saved” notification should clearly communicate this distinction. The editor seeing the change made is not the same as the customer seeing it on the published site.
Keep the number of roles as needed
The author can prepare the text, the editor can review it, and the publishing officer can make the final decision. In small teams, roles may merge; But it is not necessary to grant unlimited administrator rights to all accounts. Determine which areas need a second eye based on content risk. You do not have to manage a help article and sales terms with the same approval rule.
The approval should be tied to a specific version of content, not just the title. If the text under review changes later, the previous approval should not automatically remain valid. Cover image, link and SEO description may also be included in the scope of the review as they may be misleading. Thus, the uncertainty of “I approved the text, but then it changed” is reduced.
Also run scheduled posts
The release date, time zone, and automation task should work together. When scheduled content is manually withdrawn, the old task should not republish it. If a publishing job runs again it should not produce a second copy. It should be clear in which time zone the time is displayed on the panel.
Limit the reach of the pre-publish preview link. Private campaign text should not accidentally appear in the search engine or public preview. Keeping the visual and link behavior the same between the preview and the actual publication increases the value of the review. Text that looks good in the editor alone is not enough.
Change log and rollback
- Who changed which version, when?
- Which fields changed and who approved it?
- Can the previous version be viewed?
- Can the rollback be done without overwriting later edits?
- What happens to links and menus when content is archived?
- Are translations subject to re-examination when the source changes?
A release log is not a tool for punishment, but a source for explaining and correcting the error. Especially in multilingual content, when the Turkish version changes, the old translation should not be presented as if it is up-to-date. Good workflow ensures that the right version appears at the right moment before adding more buttons.