imbahub
Menu +
EN
Talk to us
IMBAHUB / Knowledge & guides

A publishing workflow that survives launch day.

A sustainable CMS workflow needs a writer, a clear review and someone authorised to approve publication. Start with a small process the team can follow. Add stages when they solve a real problem rather than because the tool offers more settings.

Give every change a receiving owner

  1. Prepare

    The writer supplies purpose and supporting facts.

  2. Review

    The owner checks content and affected languages.

  3. Verify

    The publisher inspects the actual public page.

Separate knowledge from permission

The person who understands a service best is not necessarily the person who should change the public website. Let the factual owner check the offer while the editor improves wording and structure. One person can fill several roles in a small team, but the responsibilities should remain explicit.

Agree how a task begins. A short change request naming the page, purpose and factual source is often more effective than a long email chain. For a changed service, specify what no longer applies, which related pages are affected and when the update may become public.

Use four observable stages

Begin in a draft or the preview environment your setup supports. Read the result as a visitor: does it answer the main question and make the next step clear? Review service claims, contact details and any terms before the authorised publisher approves the public version.

After publication, inspect the actual page rather than just the editor. Links, imagery and forms may not behave as expected. The publisher also needs an agreed way to handle a mistake. Base the process on permissions and features that really exist in your configuration; CMS products do not all provide the same revision and approval functions.

StageOwnerCheck
DraftWriterPurpose and evidence supplied
ReviewFactual owner and editorOffer, language and links accurate
ApprovalAuthorised publisherCorrect version and timing
Follow-upPage ownerPublic page checked and review assigned

Track changes across languages

If a service changes in one language, other language owners need to know even when their pages are not edited the same day. Maintain a change list identifying the topic, affected languages and reviewers. Keep a translation marked as pending until someone confirms the underlying offer, not simply the replacement words.

For example, a business stops providing installation and offers advice only. The consequences may include the CTA, enquiry options, FAQ and supporting guides. Translating the main heading is not enough. Follow the whole customer journey in every affected language and assign the remaining changes explicitly.

  • Give every page a named content owner.
  • Record the reason for a change and related pages.
  • Test the intended editor role rather than an administrator account.
  • Document how urgent factual errors are escalated.

Keep the process proportional

A small consultancy rarely needs an elaborate editorial department. Start with a shared work list and an agreed approval method. As contributors and languages increase, tighten permissions and add review stages where necessary. Check whether people actually use the process. A simple documented routine the team understands and can rehearse provides more control than a sophisticated workflow everyone bypasses.

Try the method on a bounded example

Rehearse a phone-number change in an isolated version. The writer supplies the approved number and intended locations. The reviewer checks whether the footer, contact page or other languages also need updating. The publisher tests the link and visible number. Record the approved version. If the routine misses the footer, improve the change request rather than simply asking someone to be more careful. The exercise demonstrates why even a small update can need coordination across several parts of one website.

Questions, answered

Must approval be built into the CMS?

No. A documented external approval can work when it clearly identifies the version and the publisher follows it. Use the features actually available.

How often should a page be reviewed?

Base the interval on how quickly its information changes. Contact routes, services and terms need attention when the business changes, not only on a generic calendar.

IMBAHUB

What would you like to make possible?

A sustainable CMS workflow needs a writer, a clear review and someone authorised to approve publication. Start with a small process the team can follow. Add stages when they solve a real problem rather than because the tool offers more settings.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.