In a group with several companies or brands, the hard part of publishing is rarely the editor screen. It is knowing who may change what, who approves it, which content is shared and which is local, and how a correction reaches every site that reuses it. This page is about that daily workflow — not about group governance or about moving to a new CMS, which are covered separately.
MadeByCat designs and builds content operations for holdings and multi-brand organisations: shared content models, brand- and company-level editor permissions, draft and preview, multi-stage approval, scheduled publishing, multilingual delivery and controlled reuse of shared content. The aim is a central CMS that distributed teams can publish in independently, inside rules the group has agreed.
Three related questions are often written into one brief. Group governance decides standards, ownership and which companies inherit what. Migration moves content and URLs to a new platform. Editorial workflow — this page — is how people create, review and publish content every day once the platform exists.
A central CMS gives the group shared components, a design system and one operating baseline; distributed teams keep responsibility for their own content. The workflow has to let a company team publish without waiting for the centre, while keeping the centre able to update shared elements everywhere at once.
Permissions follow the organisation rather than the software defaults. An editor at one company should not be able to change another company’s pages; a group communications team may need to publish to all of them.
Content moves through draft, preview and review before it goes live. Where legal, brand or investor relations review is required, approval can run in several stages, and each step is recorded in the platform instead of in email threads.
Some content belongs to the group — leadership, policies, sustainability statements, shared news. Some belongs to a single company. The content model marks the difference, so shared items are edited once and reused, and local teams can add to them without overwriting the source.
Language versions are linked in the content model rather than copied page by page. Editors see which translations are missing or out of date, and each language version keeps its own metadata and correct language alternates.
A shared component library and design system let each brand look like itself while using the same building blocks. Editors assemble pages from approved components; accessibility and performance standards travel with the components rather than depending on each page.
Workflow rules are documented and reviewed: who holds which role, which content types need which approvals, how unused content is retired. Content and usage analytics are reported per site so each team can see what its content does, and the group can see where the model needs to change.
Global Ports Holding: ports operate their own localised content and white-label experiences on a shared master-site platform with CMS governance. Çalık Holding: group properties migrated to date onto MadeByCat XMS work with centralised content entry and operations. Hayat Holding and Shaya show long-running operations across several brand sites.
Workflow depends on the platform and the operating model around it.
Tell us how many companies or brands publish, who approves what today and where content gets stuck. We will outline a workflow that fits your organisation.
Contact us→