Docs
Structured Content
Translate structured fields intentionally with connector mappings, previews, publish modes, and field-level handling rules.
The dashboard is a signed-in workspace. If you are new, create an account first. If you already have access, continue into the app and pick up the same guide there.
When to use it
Know when a connector is appropriate
Structured-content workflows are the advanced path. Use them only when field-level translation and destination-system behavior actually matter.
- Use a connector when a content system needs localized entities, drafts, or published writeback.
- Use the core delivery model when rendered page localization is enough and no field-level system writeback is required.
- Do not adopt structured workflows just because they exist. Use them when they remove real operational friction.
Workflow
The connector workflow
The connector path should be a controlled pipeline from mapping to preview to translation to publish.
Step 01
Configure the connector
Set the base URL, auth posture, and whether the connector should be enabled now or staged for later.
Step 02
Discover or define mappings
Decide which fields should be translated, copied from source, protected, locale-derived, or held for human-only handling.
Step 03
Preview an entity
Test a real collection item or global document before translating so field assumptions are proven against actual content.
Step 04
Request translation
Generate the localized entity once the mapping, source locale, target locale, and entity identity all look correct.
Step 05
Publish with intent
Choose whether the output remains hosted, becomes a draft writeback, or becomes a final writeback into the content system.
Publish
Choose the right publish mode
Where the localized artifact ends up should reflect your editorial process, not just your technical capability.
Publish modes
Hosted artifact
Use this when Transcontinent should serve the localized result and the source system does not need the translated content written back.
Draft writeback
Use this when editors should inspect and approve localized content inside the source system before it becomes canonical.
Final writeback
Use this when approved final localized content should become the source system's published version for that locale.
Field handling modes
Translate modes
Use translate modes for plain text, rich text, safe HTML, and safe metadata when the field should become localized.
Copy source
Use this when the value should stay identical across locales, such as fixed IDs, immutable codes, or intentionally source-authored values.
Protected-term only
Use this when a field must stay tightly constrained and any variation should orbit protected vocabulary rather than broader rewriting.
Locale-derived or human-only
Use locale-derived for values like slugs or routing helpers that follow locale rules, and human-only for fields that machine output should never finalize.
Best practices
Run structured-content rollout carefully
A connector workflow should make editors and operators more confident, not add opaque complexity.
Start with one content type
Prove the workflow on a single collection or global first before you map the entire content model.
Preview before you translate
Preview is the cheapest way to catch wrong field mappings and avoid generating content that never had the right shape.
Prefer draft writeback when review matters
If editors or market owners need to inspect content, make draft review part of the workflow instead of bypassing it.
Use connectors only when they add value
If rendered-page localization solves the problem, do not force structured workflows into the program just because they exist.