How do you translate a CoreMedia Content Cloud website while keeping a master site, derived language sites and publication changes consistent? This CoreMedia translation guide explains multi-site localization, Studio translation workflows, master-derived relationships, synchronization, editorial review and live-page quality assurance. It is intended for international publishing teams that need accurate multilingual content rather than a collection of disconnected copies.
CoreMedia Content Cloud can represent relationships between master content and derived content for other languages or regions. The important distinction is that translation and synchronization serve different needs. One may require new language, cultural context and a subject-matter review; another may propagate changes between sites using the same language while retaining a local identity. Neither operation removes the responsibility to check what each visitor is actually told.
This practical CoreMedia multilingual CMS tutorial follows a fictional international museum network with English master content, a French-language site and a regional English site. It turns official CoreMedia documentation into understandable editorial decisions about site hierarchy, start-and-finish workflows, change tracking, linked content, source revisions, permissions, SEO, launch and rollback. Use the worked checks to confirm not only that a workflow ran, but that the right meaning reached the right audience.
Quick answer: keep the master relationship visible
Start by documenting the source site, derived sites, languages, regions and target content owners. Draw the relationship between the master item and each derivative. Decide whether each site is meant to translate the source language, synchronize shared same-language content or manage some items independently. This decision is more important than how quickly a workflow can create copies.
Configure the roles and work queues for the actual editors. Translate one complete journey in a test environment, including page, teaser, associated media, a form and related items. After a change to the master, observe which derived items are notified and how they are reviewed. Finally inspect each public route while signed out, including its title, navigation, date, call to action and SEO metadata. A content item is finished when the destination can be understood and acted on, not merely when Studio reports a completed task.
Why master and derived sites matter
CoreMedia’s multi-site model gives organizations a way to reuse common content without losing sight of local destinations. A master content item has a relationship to derived content created for another site. This can reduce the disorder of manually copying pages and forgetting where they came from. It also creates a responsibility: editors must understand whether a derivative should follow the source or exercise local authority.
Imagine a global museum announcing a travelling exhibition. The central description is approved in English. The French site needs an accurate translation, but its ticketing and address information are local. A regional English site may use the same language while displaying different accessibility arrangements and opening hours. Treating all three as identical copies can create errors. Treating all three as completely independent wastes effort and makes future corrections harder. The site hierarchy should express the real ownership of information.
Translation versus synchronization
CoreMedia’s documentation distinguishes translating content into derived sites with another language from synchronizing content to sites with the same language. The underlying multi-site relationships are related, but the editorial obligations differ. Translation must preserve meaning through another language. Synchronization may carry material from a master to a local market without changing its language, yet still needs regional review if service details differ.
Do not label synchronization as translation simply to make a status dashboard uniform. A localized English page that receives a centrally revised disclaimer may still require a local legal review. A French page needs more than synchronization of source words. Write the purpose of each derived site in plain language. When a source revision arrives, ask: should the target inherit it, translate it, adapt it or decline it? Recording this answer makes a system feature into a defensible publishing decision.
Plan the site hierarchy before creating variants
Draw the organization as a hierarchy that corresponds to real editorial responsibility. Put the approved shared source at the correct level and identify each language or market derivative. The CoreMedia multi-site manual discusses site hierarchy variants, locale planning, language tags and content-integrity challenges. Those are not simply configuration details: they determine how change relationships are understood over time.
A poorly chosen hierarchy can make every correction appear to require manual reconciliation. Another arrangement might cause local material to be overwritten by an inappropriate master change. Before setup, model three sample updates: a universal factual correction, a new regional offer and a sentence rewritten solely for clarity. Decide which child sites should receive each, which should be notified and who can approve adoption. Run the examples through the proposed hierarchy. A good hierarchy makes legitimate differences visible instead of treating every difference as drift.
Use valid locale identifiers and a clear market register
A site locale needs to describe the language and, where necessary, the regional variant. Do not assume a French-speaking audience means one uniform set of laws, prices or availability. Keep a register listing source language, target language, market, public host or path, reviewer, fallback policy and release status. Use accepted language tag conventions and confirm the exact CoreMedia version’s supported configuration.
Keep language differences separate from regional content differences. A French translation of a universal exhibition explanation may be shared across several locations, while local ticketing terms should be specific. Name all variations in a way editors can recognize when they select a workflow target. If two destinations use the same language, explain why they still need separate regional versions. The register becomes a shared vocabulary for developers, translators, curators, legal reviewers and the team responsible for publishing.
The master record is a reference, not a command to overwrite
Master content helps a team understand the origin of a derivative. It does not necessarily mean the master has authority over every local fact. CoreMedia documentation notes that tracking of the master may be disabled when a derived item is intentionally managed independently. That option should be governed carefully rather than used as an escape from repeated notifications.
Write down which fields must follow shared source truth and which fields have a distinct regional owner. For example, scientific facts should normally be corrected at source and translated consistently, while an opening time belongs to the local venue. If the team detaches a local item from source tracking, record why and provide another method for discovering material source corrections. Independence can be legitimate; invisibility is dangerous. Without an explicit relationship policy, an editor can appear to have finished the translation while future revisions never reach the page.
Understand Studio’s translation workflow
CoreMedia Studio’s documentation describes translation workflows that can be started for derived sites and used to coordinate work between a master site manager and destination managers. A workflow supports delegation, but it should not be mistaken for approval of every claim in the content. People still need to decide what has changed and whether its local representation is correct.
Follow one item from source selection through initiation, target creation or retrieval, translation work, review and final publication. Record whether the item already existed in the target site. Note what the workflow creates automatically and what remains the responsibility of the editor. Test a small example first because source content can contain links to additional pieces that also need destination equivalents. An apparently single-page translation may become a group of dependent content items requiring separate editorial attention.
Roles and permissions should match accountability
Official CoreMedia workflow documentation describes translation-manager-related roles and site manager membership as conditions for starting workflows. In practice, permissions must support the whole editorial chain without granting everyone unrestricted publishing power. Map who can initiate a translation, edit a target, review language, approve a market-specific claim and release material publicly.
Test the process with actual roles, not only an administrator account. A workflow that functions for an administrator may fail for a translator who cannot see a source item or complete a handoff. Conversely, broad privileges can allow an inexperienced contributor to publish a draft to all markets. Keep a test account for each role and a short escalation route when a task is blocked. A responsible workflow shows why a person can act and how mistakes can be corrected without altering protected source items casually.
What happens when a target item does not exist?
In CoreMedia’s described translation workflow, target content may be created when a corresponding target item is absent. This is helpful for building a new language site, but it can bring along additional linked items. Treat creation as the start of a translation obligation, not evidence of a finished translation. Content may exist in the repository before its audience-ready state has been established.
Use a new target article in staging and inspect all properties: title, rich text, teaser, media references, related items and local links. Ask the reviewer which values are copied, translated, inherited or still unresolved. Do not assume copied English content should become public on the French site. If a derived item exists but is outdated, compare it against the source revision instead of overwriting its local decisions. A deliberate target-state check prevents workflow success from becoming accidental publication.
Linked content can multiply the scope
An article rarely lives alone. A museum landing page might reference a curator profile, collection image, event schedule, booking module, campaign banner and accessibility notice. CoreMedia translation documentation discusses the relationship between linked original and translated content. Editors must know whether linked destinations are translated, inherited, copied or unresolved before approving the main page.
Build a dependency list for the page in order of reader importance. A broken related link may be inconvenient; an incorrect booking term is consequential. Review all links using the target site, not just the source. Where the target has no approved equivalent, use a purposeful, transparent fallback or withhold the link. Avoid creating a route that suggests the user has entered a fully localized experience and then drops them into an unrelated region. A language journey consists of all the connected content the reader actually touches.
Side-by-side comparison supports thoughtful review
A side-by-side view is useful because translation quality depends on what the source means, including changes that are easy to overlook in a polished target paragraph. Examine the source and target together. Mark changes to quantities, names, dates, conditional language and claims. Separate a new factual assertion from an ordinary change in style. The English master might add a restriction; the French translator must preserve its force, not simply imitate its sentence structure.
Ask reviewers to explain the difference in ordinary terms. If the source says registration is required for some sessions, a target saying registration is required for all sessions fails even if every word is idiomatic. Preserve the source revision used for approval. Side-by-side interfaces do not replace domain expertise, but they allow people to see which claims need attention and why a target translation should be revised.
Change tracking is a signal, not a release instruction
CoreMedia can track changes in master content and present them to derived-site editors. That makes drift visible. However, a notification does not by itself say that the change can be applied without local review. Sometimes the source update is a typo that may have no effect in another language. Sometimes it changes a requirement or deadline that must be urgently reflected across markets.
Define categories of change: editorial only, new factual information, legal or safety-sensitive change, link update, asset replacement and local-market change. Each category gets a response rule and reviewer. An editor should be able to close a source-notification task with a reason when the target correctly remains different. Conversely, a critical change should not be ignored because it is inconvenient to translate. A practical audit log links source revision, decision, target version and public validation.
Synchronizing a same-language regional site
Consider an English source site and an English-language venue site in another country. The central exhibit description may be reused. Prices, opening hours, accessibility facilities and contact instructions cannot be blindly inherited. Synchronization should carry the shared description while preserving or prompting review of regional fields, according to the organization’s model.
Try an experiment in staging. Change the master description and the master address. Observe which values the synchronization process makes available and how an editor sees differences. Test that regional contact information remains correct. Also review the visible date and currency formats in the final page. This exercise explains why using the same language does not guarantee identical content. Synchronization is successful only if it saves work while retaining the local responsibilities that the reader actually depends upon.
Translating a different-language derivative
A French editor should receive a source that is stable enough for meaningful translation, along with context about audience, terminology and intended action. If the source article has an embedded technical warning, protect its meaning. If the content mentions a British event location, do not replace it with a French venue merely to make the text feel local. Translate what is true, then add a separately approved regional adaptation when appropriate.
A good translation task includes the exact source revision, desired language, related images, expected URL, terms requiring consistency and a named subject reviewer. For marketing copy, allow natural rewriting that preserves the promise. For safety conditions, favor precise equivalence over stylistic freedom. On completion, require someone to inspect the target as a reader would, with local navigation and links. A successful word exchange is not enough if the page invites the wrong action.
When should a derivative be independent?
Some local sites eventually produce original stories rather than translations of the master. Those stories should be represented honestly. CoreMedia permits editorial strategies in which master change tracking can be avoided for independently managed material. Use that only after deciding who will keep the new source accurate and how it relates to neighboring sites.
Avoid disabling tracking simply because notifications are noisy. Instead fix the content model or responsibility map that is producing needless tasks. A local original article may still share global brand terms and reusable disclosures that need centralized updates. Record the status as local original, adapted derivative or translated derivative. Each category has a different maintenance expectation. This prevents a future editor from treating a local article as an obsolete translation or applying a master change that erases an approved market-specific explanation.
Build a field-level translation map
For a sample content type, inventory the headline, description, summary, image, alt text, metadata, CTA, legal terms, location, numeric identifiers and publication status. Mark each field as translated, shared, market-specific or computed. A source item may be copied into a derived site while only some values require new language. The field map helps translators focus on what the audience actually sees.
Include invisible strings such as structured data descriptions and accessible labels. A media file may be globally shared while its caption needs a language-specific value. A price can be regional data rather than prose. Check the field’s real source and destination behavior in the installed CoreMedia project, which may use custom content types and templates. Do not assume every organization has the same model. The most robust translation workflow makes distinctions explicit in the schema and the review procedure.
Treat media and campaign components as first-class content
Images, video, PDFs and promotional banners often have their own version history and language needs. A global banner may contain English text inside the image even when its surrounding page is French. A localized video might need subtitles, audio descriptions and captions. A PDF download might remain in English and should be labeled accordingly.
Inventory media references from the translated article rather than checking only the visible body text. Record approved versions by destination language, and test their public delivery. If the system links to an asset from the master site, determine whether that relationship is intentional. Review licensing, regional permissions and time-limited campaign promises. A campaign that has expired in one market should not remain active because a reusable component was synchronized without checking its context. Meaning travels through assets as well as sentences.
Preview, publication and delivery are different states
Studio may show material to an authorized editor before it is visible on a public page. A translation workflow can finish while a public delivery path remains unchanged or cached. An article can also be publicly available but still fail quality checks. Define separate states for source approved, target reviewed, publication complete and public delivery verified.
Test the specific published URL in a session without editor permissions. Record the title, primary language, key claims, local links and date of the response. If the browser receives an older version, investigate publication and caching before rewriting the translation. A staging success should be compared with the actual delivery environment. This distinction is especially important for global sites with several regional domains, front-end applications and independent cache layers. The final evidence belongs to what the reader can obtain, not only what the CMS says internally.
Organize international URLs deliberately
Decide how each language or market page will be addressed: locale path, regional subdomain or dedicated domain. Public navigation and redirects must align with the chosen CoreMedia site hierarchy and front-end integration. A language switch should take the reader to the appropriate counterpart when it exists; it should not always reset to an unrelated homepage.
Test direct links with a fresh browser, existing cookies and mobile devices. A shared French URL should continue to show the intended page when opened by someone whose browser prefers English. Where a counterpart is unavailable, explain that plainly instead of silently inventing a complete translation. Record the relationship between source item, derived item and public URL in one place. That helps editors find broken alternate links after structural changes or renamed campaigns. Stable links are part of a dependable multilingual publishing experience.
International SEO needs honest variant mapping
Search engines should be able to identify real language variants and understand their preferred URLs. For each approved public page, record canonical URL, HTML language and alternate-language destinations when relevant. Do not emit hreflang links for drafts, dead links or unreviewed fallbacks. Translated titles and summaries must accurately describe the page’s content rather than being mechanical versions of English marketing text.
Check the page as rendered to the public. A CMS field can contain a French title while the front-end template emits English metadata. Likewise, a translated story can be excluded from search accidentally when a centralized canonical tag points to the master. Evaluate the entire result, including sitemap presence, redirects and links from language-specific navigation. International SEO is not a separate trick layered on top of publishing. It is a description of the real multilingual content estate.
Forms and contact workflows must keep their meaning
Suppose a visitor reads a French programme page and opens a form to request group attendance. The form asks about arrival time, dietary requirements and consent to communications. Every visible label, error and confirmation must be understandable. The form may be a separately integrated application rather than a CoreMedia content type, so a translated page does not automatically localize it.
Test valid and invalid submissions. Preserve backend field keys and data types. Review whether consent wording is approved for that market. Follow the submission through confirmation email and any linked policy page. If the visitor is told that registration was completed when the system only received an enquiry, the translation fails its purpose even if the words are natural. The acceptance standard should describe the action and resulting status that a reader can reasonably infer.
Data presentation is not prose translation
Dates, times, quantities, currencies and measurements should be stored as appropriately typed information and rendered according to verified locale requirements. Translators should not silently convert a fixed amount into another currency or change a deadline to match a guessed local time zone. Those actions require separate business rules and authoritative data.
For each regional page, check the source of opening hours, fees and addresses. Record which values may differ by site. A global fact like the year of an artist’s birth remains the same across languages. An exhibition’s local opening time might not. Add test data that includes a decimal, range, time zone and a sentence with a condition. Ask the reviewer what a reader will believe. Errors in data presentation can undermine an otherwise accurate translation without leaving any obvious typo in the page body.
Accessibility must follow the translated journey
Language-specific pages need appropriate language metadata, meaningful headings, localized accessible names, descriptive links and understandable form errors. When a user switches languages, focus management and navigation should remain sensible. Text expansion may change layout and must be accommodated rather than cut until conditions disappear. Right-to-left languages demand additional checks for mixed scripts and reading direction.
Conduct a keyboard-only and screen-reader test from public entry page through a related article and form. Review images with meaningful text and ensure captions or descriptions are appropriate in the target language. If a video contains spoken content, evaluate subtitles and transcripts. These checks are not separate from editorial translation: they determine whether the same supported information reaches people with different ways of navigating. A multilingual page is not complete when only its visual headline has changed.
Build a source-change response protocol
When master content changes, the derived site’s editor needs to know not only that something changed but what kind of change it was. A new legal condition, corrected measurement or changed event date should receive high-priority review. A stylistic change may be adopted later or not at all if the target already communicates the same meaning.
Link the source revision to affected target items. Preserve why the target was updated or deliberately left unchanged. Use a priority queue that matches reader risk rather than treating all notifications equally. After approval, check publication and public delivery. If a change creates an inaccurate active page in another locale, apply the site’s withdrawal or warning procedure. The goal is a sustainable multilingual system in which accuracy can survive normal editorial change, not just a one-time launch.
Practical QA: the twelve checks every release needs
For each destination, verify source revision, master-derived relationship, target language, editorial approval, associated links, embedded assets, regional data, public URL, metadata, accessibility, search and the intended reader action. Record the observed result and responsible reviewer. Include an unavailable-translation test and a same-language synchronization test if both behaviors are part of the project.
A checklist is useful only when it has evidence. Avoid marking a box because a contributor says the content looks fine. Capture the actual URL, language, version and outcome. If a failure is found, distinguish whether it belongs to content, workflow, permissions, routing or delivery. Repeat the failing journey after the correction. This makes quality assurance practical for a distributed team and prevents every future problem from being sent back to translators, even when the real cause is elsewhere.
Troubleshooting: a target page is unexpectedly English
Begin with the exact site, item and public URL. Is there an approved French derivative? Does the link actually point to that item? Did the translation workflow create content that was never translated? Is the target ready but not published, or is the front-end retrieving the master? Check template and cache behavior before editing prose.
If only a teaser is English, trace the teaser’s field or linked component separately. If a new source update appears without review, inspect synchronization and change-tracking choices. If the editor cannot run the workflow, check permissions and site management roles. Preserve a screenshot and content identifiers for reproducibility, but do not treat the screenshot as proof of source identity. Once the root cause is isolated, repair the appropriate layer and repeat the whole reader journey to confirm that no new wrong-language link remains.
Troubleshooting: changes overwrite local work
Investigate whether the derived site was intended to synchronize a field, translate it or manage it independently. Compare the latest source revision with the target’s previous approved version. Identify whether the overwrite came from a workflow decision, template behavior or incorrect content ownership. Recover the correct local facts using version history under appropriate editorial controls.
Prevent recurrence by tightening the field map and responsibility register. Do not solve the problem by disabling all change relationships, because that can leave important central corrections undiscovered. Instead decide which fields legitimately inherit source changes and which require a conflict review. Use a test where the master and target intentionally differ in contact information, then run the expected synchronization. The acceptance criterion is the preservation of approved local meaning alongside updated shared facts.
Troubleshooting: workflow says complete but the page is missing
A workflow’s status refers to its own process, not every step of delivery. Check whether the target content was created in the expected site and folder, whether its publication state permits public access and whether the URL resolves. Verify front-end routing, cache and search index separately. A hidden page may be a deployment issue rather than a translation issue.
Test with an anonymous browser session and, where relevant, a direct API read. Avoid accidentally publishing a draft while investigating. Use the target item’s actual revision as the point of comparison. When the page becomes visible, confirm that its metadata, links, language and actions match the approved content. Then document the missing step in the workflow so a future team can detect it before an audience does. A resilient process makes failure states comprehensible and recoverable.
Release governance: who decides that a language can launch?
Assign distinct responsibilities for source content, translation, regional adaptation and technical publication. On a small project a person may handle several responsibilities, but the decisions should still be named. The language lead can approve natural and accurate phrasing; the subject owner approves factual claims; the regional owner approves local availability; the release owner confirms public behavior.
Set launch gates that are based on reader harm and practical completeness. An optional decorative caption may be lower risk than an incorrect admission condition. Define whether partial locale launches are permitted and how they are labeled. Keep an urgent correction path and a rollback plan. A master-derived architecture is valuable precisely because it can support coordinated change across markets, but only if human ownership remains clear. Software can route work; it cannot replace the judgment needed to tell readers the truth.
Ten worked editorial situations
Worked scenario: a shared artwork description
The English master includes a curator-approved explanation of an artwork’s history. The French target is translated and reviewed by a fluent editor and the curator. A later correction changes the artist’s year of birth. The change notification identifies the target. The reviewer updates the number without rewriting unrelated local copy, republishes and checks the French article and its search card. The record proves which source assertion was corrected and which reader-facing destinations received it. This is a suitable use of the master relationship because the historical fact is shared across regions.
Worked scenario: two English-speaking venues
The global museum operates one venue in London and another in Melbourne. The descriptive exhibition text can be synchronized, but the booking phone number, local currency and opening hours differ. A staging exercise changes both master prose and master address. The synchronization should apply or offer the shared prose while leaving venue-owned data correct. The page reviewer checks actual public routes in both places. If the data model cannot distinguish those responsibilities, the team must adjust its editorial design rather than instruct editors to repair predictable overwrites after every update.
Worked scenario: a missing translated biography
A French exhibition page references a visiting curator whose biography has not yet been translated. The workflow may create a target-related item, but that does not mean it has been approved. The release editor sees the dependency and decides whether to withhold the link, provide a clearly labeled English biography or complete the translation. The French page is not published with a misleading link presented as French. The decision is recorded so a later reviewer can replace the interim route without creating a second biography detached from its source.
Worked scenario: the conference date changes
A multilingual conference postpones a workshop. The source date field and explanatory notice change together. Editors review every language destination, calendar card, registration form and confirmation message. The French translator preserves the meaning of postponed rather than cancelled. The regional team checks whether travel arrangements or deadlines also changed. The release is tested via direct links and search. An accurate date in a CMS field is insufficient if a teaser or email still tells visitors to arrive at the earlier time. The incident makes visible why a complete journey must be mapped.
Worked scenario: a local page becomes original
A regional team writes an independent interview. It references the same global exhibition but does not originate as a translated version of the central article. The editor labels the relationship correctly and avoids treating future master revisions as instructions to overwrite the interview. Shared terminology and exhibition dates still receive their own maintenance path. This distinction preserves local editorial independence while allowing central facts to remain dependable. It also helps search engines and readers understand that two pages are related but not simply alternatives in different languages.
Worked scenario: a link to a withdrawn source
A master item is withdrawn after a factual error. A derived language page remains live because nobody followed the status change. The release manager traces linked derivatives and determines whether they repeat the affected claim. The team temporarily withholds or corrects the target content, checks old direct URLs and invalidates stale search results. The editorial note records the reason for the change and the replacement source. This is more reliable than assuming that a translation workflow automatically removes every misleading derivative. Withdrawal needs the same deliberate cross-site attention as publication.
Worked scenario: a French site with English SEO tags
The visible French page is reviewed, but its title tag and search description are supplied by a shared English template. A searcher sees an English result and lands on French material. The team traces metadata ownership, establishes a localized source and checks canonical and alternate relationships. The fix is validated on rendered public HTML and real direct routes. A translation is not discoverable and transparent merely because its body copy is accurate. Search-facing text should describe the same language and subject that the visitor will find after clicking.
Worked scenario: translating a crisis notice
The museum closes because of unsafe weather. Editors must publish a clear notice quickly in multiple languages. The source owner confirms the fact and scope; translators preserve whether the closure is temporary and which visitors are affected. If a locale is not ready, the site uses its approved interim notice policy rather than presenting an outdated page. The team checks homepage cards, event pages, banner, forms and social links. Once the venue reopens, a new verified source revision removes or replaces the warning. This scenario reveals why source-change priority and accountable publication gates matter.
Worked scenario: permissions block the final review
A translator has completed a French derivative but cannot initiate or finish the expected workflow. The team tests the user’s actual site manager and translation role permissions. It makes a narrow administrative correction through normal governance, rather than temporarily granting unbounded access. The editor then completes review and the release owner verifies public delivery. Documenting this case separates workflow configuration from linguistic quality. A good translation should not be held hostage by a role mismatch, and a role mismatch should not become a reason to bypass approval.
Worked scenario: a revised image reverses a message
A master page replaces an image that included a directional arrow and a caption. The French derivative retains the old caption and points the user to a section that has moved. The content owner treats image, caption and navigation target as one dependent unit. Review checks that the new image contains no untranslated embedded text and that its accessible description remains useful. After publication, the team follows the link as a visitor. The incident shows that an apparently minor asset update can alter the action readers are being instructed to take.
Frequently asked questions
Does CoreMedia automatically make a target translation correct?
No. Workflows coordinate content and relationships; human review must establish meaning, market appropriateness, publication state and reader outcomes.
Is synchronization the same as translating?
No. CoreMedia’s documentation distinguishes translations into another language from synchronizing content between sites using the same language. Both can require editorial decisions.
Why does a linked item appear without a finished translation?
A workflow may create related target content when absent. Editors still need to check its language, status, meaning and publication readiness.
Can derived-site editors reject a master change?
Editorial policy and configured relationship options determine how local material is maintained. Record deliberate differences and source revision decisions rather than silently ignoring changes.
What proves that a French page is live?
A signed-out test of the exact public URL, including its target content, metadata, links, assets and intended action; Studio task completion alone is not enough.
What is the best first pilot?
Translate one source article with a teaser, media item and link, then change the source and observe the entire notification, review and publication path.
Official CoreMedia documentation
Consult the documentation for the exact release used by your organization. The official CoreMedia Content Cloud 2512.1 manuals describe multi-site hierarchies, localizing content, translation and synchronization workflows, as well as user roles.
- CoreMedia Content Cloud Multi-Site Manual 2512.1
- CoreMedia Studio: Localizing Content
- CoreMedia Studio: Performing Translation
- CoreMedia Studio: Synchronizing Content
Continue reading eduKate’s translation architecture
The Master Art of Translation examines source truth, changes and cross-language meaning. The Translate Like a Pro series index groups practical platform-specific implementation guides. This article owns the CoreMedia-specific distinction between master-derived relationships, translation and synchronization; broader translation principles belong to their established guides.
A well-run multi-site publishing system lets a team reuse the right information without erasing the decisions that belong to another language or region. Its success is measured in trustworthy pages readers can actually use, and in the ability to keep those pages trustworthy as the source changes.