Publishing content in a CMS: how to organise roles, preview and approval
Set roles, draft states, preview, approval and public checks for a clear CMS publishing process.
Article language: English

In this article
A CMS lets you change website content without editing code. It will not decide who confirms a price, approves a photograph or corrects a mistake. Without those decisions, a “Publish” button can become an efficient accelerator of chaos. Set out a simple path from draft through preview and approval to checking the public result. A convenient editor and clear responsibility need to work together.
Design the process around one real editorial task, such as updating a service or adding a guide. Technology can then be chosen against testable requirements. The model below helps define the scope and assess an editor's work, whether content appears immediately or after a separate deployment.
Which changes should the process describe first?
List typical updates from recent months. Separate changing a telephone number, editing an article, replacing a photo and restructuring an offer. Each has different responsibilities and consequences if wrong. Record frequency, participants and affected parts of the site. A shared header may appear on many pages.
Choose two tasks to demonstrate: one frequent and one harder but important to the business. Ask to see the whole route from source material to the public view. A demonstration using an empty sample paragraph will not show how the system handles a long service name, a vertical image or a change of address.
Record requirements in your own project brief. The guide to a premium website brief (in Polish) explains how to prepare one. Instead of “intuitive CMS”, write: an editor updates a description, sends it for approval and can see whether the update has been published. That can be tested without arguing about personal preferences for the interface.
How should responsibility and permissions be divided?
Distinguish the author, the person approving content and the person publishing it. In a small company one person may perform several roles. It is still worth recording what they check before each step. A technical administrator separately manages accounts, configuration and updates.
Grant access according to the task. An editor does not automatically need permission to install extensions or delete the entire site. WordPress documentation on roles and capabilities shows one product's distinction between roles and permissions. Actual capabilities also depend on the company's configuration and extensions.
During acceptance, sign in with each role. Test both permitted actions and those that should be blocked. Do not judge permissions solely by a role's name in the panel. Keep a list of responsible people and arrange cover so one person's holiday does not require sharing their password with the whole team.
Which content states are actually needed?
A simple process may include draft, awaiting approval and publication. An extra state is useful when it changes responsibility or an action. “Under correction” without an owner and a condition for completion creates a queue nobody controls. Record who may move material forward at each stage.
Do not equate visibility with readiness. A draft should not accidentally enter public search, a news feed or related-article lists. Conversely, “published” in a panel does not always mean the latest version has reached every public location.
For sites built through a separate process, record deployment state too. An editor needs to distinguish approval from completed publication. The WordPress posts screen documentation describes states in that system. Do not assume another CMS uses identical names or mechanisms.
What should an editor complete besides paragraphs?
Design fields to match the content type. An article needs a title, description, image and relationships. A service may also require scope, conditions and contact. Separate required fields from supporting ones and give a short company-specific example where a field is difficult.
Limit freedom where consistency is easy to damage. An editor should select a heading's function rather than manually enlarge ordinary text. Use customer questions to decide how to organise the CMS fields. The article on writing service-page copy (in Polish) explains how to organise the copy around those questions. Do not, however, turn every thought into a separate rigid field.
Replacing a photo should account for alternative text and different crops. The team needs to inspect both a thumbnail and the full cover. The brand's photography plan should specify where each crop will be used; approving a large file alone is not enough. A system can enforce format, but a person still judges meaning. For generated material, check the origin and role of each AI image so replacing a file does not leave a caption implying a real completed project. The article on the origin and role of AI imagery (in Polish) discusses that distinction.
The brand photography guide (in Polish) also discusses crops, alternative text and keeping track of images.
How can preview and approval avoid mixing versions?
A preview must identify the material and version it shows. The approver should see the intended layout on a phone and a large screen. A text document alone will not reveal a cropped button, a poorly placed photo or an unreadable comparison. Record approval against a specific version.
Decide whether the preview link is public and how long it works. Confidential material needs appropriate access control. An obscure address is not a security measure. If approval requires login, check in advance that the decision-maker can actually open the material on their device.
After feedback, show what changed. A short list of significant corrections helps avoid reviewing the entire text again. If price or a promise changes after approval, send the material back for the appropriate approval. Correcting a comma and changing the service scope are not equally significant.
What does a hypothetical new-service publication look like?
This scenario is hypothetical. A consultancy adds a process-analysis service. An author creates a draft, the service owner confirms scope and an editor checks the language and materials. A phone preview reveals that a long heading covers part of the image. The team corrects the layout before approval.
A form check also reveals that the new service is missing from the enquiry topic list. The issue goes to the person maintaining the form. Publication waits for confirmation of that dependency even though the text itself is ready. That is the deliberately chosen acceptance condition in this example.
After launch, the editor opens the public address without an admin session, checks the link from the offer and sends a test enquiry. Only then do they record completion. The version, approvers and test result remain in the register, so the next update starts from existing decisions.
How can a mistake be reversed without losing history?
Distinguish version history from a backup. History can help restore text but may not include files, settings or the entire site. WordPress revision documentation describes comparing saved changes and restoring an earlier version. Check the actual scope in your own installation.

Run a safe-material test: change a passage, publish, restore the previous content and inspect the public view again. Check the image, links and dependent elements. Reverting text does not automatically guarantee reversal of changes in other systems, such as a form or catalogue.
Record an urgent correction procedure too. Who can withdraw incorrect information, how do they notify the content owner and how is the cause documented? Distinguish correcting information from removing an entire address. The latter requires considering links and the user's subsequent path.
How do you check the public result and dependent locations?
After publication, inspect the page at its intended address. Verify title, description, sharing image, content and relationships. If the site has news listings or search, check those too. The admin panel may show a newer state than a public view using cached content.
Changing an address requires a separate task, not an accidental field edit. When handling a site URL migration, check old links, destination content and the appropriate server response. The website migration guide (in Polish) discusses how to map and handle addresses. Keeping a published address can be safer than adjusting it for every minor heading change.
The technical SEO acceptance check (in Polish) describes basic conditions for presence at the correct address. Turn them into short operating instructions for the editor. They need not analyse the entire configuration themselves, but should know when and to whom to report a discrepancy.
How can the team work independently?
Base training on a participant's task rather than a tour of every icon. Ask them to create a draft, change an image, send it for approval and verify publication. Then ask about an error: how would they recognise the wrong state and where would they seek help? The exercise reveals missing instructions.
Provide a short guide with current screens, responsibilities and technical contact. List actions that require support, such as changing a service structure or integration. Assign an owner to update the guide when the panel changes. A recording from several versions ago may be less useful than one accurate page of text.
Test work while the usual editor is absent. The substitute needs an individual account and must know where the materials are. Giving access without context often leads to publication of an unapproved file. Responsibility for current content remains part of the business after the project ends.
Test disagreement about content separately. If two people give conflicting feedback, the editor needs an identified decision-maker instead of choosing the version in the latest message. Record the decision against the specific passage and explain the assumption. For a material change to a promise, also retain the service owner's confirmation. The panel need not create a complicated document workflow; a clear link between task, version and decision is enough. Months later, it helps a new employee understand an unusual wording. Text history shows what changed; context explains why the company chose it and when to review it again.
What CMS acceptance checklist should you use?
Close acceptance with specific tests:
- Each role performed its permitted task and could not exceed the agreed scope.
- The draft stayed out of public lists and search.
- The preview showed the correct version and approval had a named owner.
- Long text and a vertical photo did not break the layout.
- Publication was confirmed at the public address and in dependent locations.
- Previous content was restored according to the procedure.
- A substitute completed the full editorial task independently.
If you need to organise the editor alongside the website project, see the Aeneia Design scope.
Does a draft stay separate from the public version?
Save a draft of one existing entry and reopen it. Check that the public version stayed unchanged until publication was deliberately started. Saving working corrections should not itself expose them to readers.
What should be checked after moving a blog to a subdomain?
A new blog address requires checking the reader's whole route. Record a map of old and new addresses. Open an earlier link to a particular guide and confirm it reaches the same text, not merely an archive. Check its category, cover, paragraph links and offer button too. The guide to implementing and checking website language versions (in Polish) helps distinguish interface language from the actual publication language.
Accept the locations displaying article summaries separately. A new publication should appear in the right collection and on service pages using the feed. Do not assume changing the data source is sufficient: a consumer may have its own category filter, cache or restriction on image domains. If refresh fails, retaining the last valid list may be better than showing an empty section.
Finally, perform the technical SEO acceptance check (in Polish) at the public address. Compare the full HTML, canonical address, sitemap and CMS publication state. Check visit measurement separately: the presence of a script does not prove that an analytics service accepted an event. Decide who accepts each result and where evidence is kept. This protocol also helps when AI agents prepare some content.
For new material, decide when to publish a PDF and when HTML content is appropriate. That choice affects updating, accessibility checks and finding the right version. An attachment also needs an owner and a place in the correction procedure. For the trade-offs between the formats, see the PDF and HTML guide (in Polish).
How can a series of interlinked guides be released?
For one text, checking its links may suffice. A series adds sequencing: the first guide may point to a second still in draft. A reader should not reach a missing page merely because the editorial team is halfway through clicking “Publish”. Plan a joint release or temporarily point to material already working. Make that choice deliberately.
Before release, close the list of texts and check their mutual links. If the CMS supports batch publication, determine whether it validates the entire intended set and stops the operation if one article fails. Confirm it does not accidentally include other drafts. Preview and approval should cover specific saved versions. A change made in the meantime needs renewed agreement rather than silently overwriting the author's work. Design a simultaneous-edit warning and deliberate conflict resolution so the change is recognisable before saving. A warning alone does not prevent overwriting; check the protection separately. The simultaneous editing article (in Polish) examines ways to preserve work and compare versions.
After publication, open the series from several entry points. Check navigation between guides, category and the offer link. Separately confirm the sitemap and submission of changed addresses. A well-prepared batch saves manual clicking but does not replace public acceptance. A collection of green statuses still does not replace a working reader journey.
Who confirms the SEO update after publication?
Separate content acceptance from notifying search engines. The editor checks the destination article, cover, links and description. The person responsible for publication confirms the sitemap, canonical address and the submission result for new or changed addresses. Do not close both actions under one “done” state if the second is still pending.
Record the attempt date, address list, provider response and retry time. IndexNow documentation distinguishes acceptance of a submission from waiting for key validation. Neither result proves that an article is indexed. If there is an error, preserve the pending task; do not resubmit the entire library.
Google recommends using lastmod for a significant update to content, structured data or links. Rebuilding a site alone does not justify making a publication appear newer. Link practical acceptance to technical SEO checks (in Polish) and the decision register so the next person knows the previous attempt's result.
For the decisions behind a change, the project decision register article (in Polish) explains how to retain context and outcomes.









