Docs
The Definitive Guide To Transcontinent
Use this docs section as the product contract: what the platform is, what each abstraction means, how the first launch should work, and how to configure delivery without guesswork.
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.
Start here
Transcontinent is a product for operating multilingual websites intentionally. The point is not to translate everything by default. The point is to give teams a coherent operating system for deciding what should be localized, how quality should be shaped, when a locale is ready, and how much automation the program actually needs.
These docs are written as the product contract. If a page here feels clearer than the actual UI, the product should move toward the docs. If the docs are vague, the product model probably is too.
The public docs are the pre-auth guide. If you are evaluating or onboarding, read the docs first, then create an account and continue the same workflow inside the dashboard.
Handoff
From reading to doing
The docs-to-product transition should be obvious. A new operator should know exactly what happens before and after auth.
1. Read the launch runway
Use the getting-started guide to choose the right defaults before you touch the dashboard.
2. Cross the auth handoff
Create an account if you are new, or sign in if you already have workspace access.
3. Start the real workflow
Open the dashboard and create the first site workspace from one representative URL.
Docs map
Choose the path you need
Use the docs in the order that matches your job. If you are new, start with onboarding and the product model. If you are already configuring a site, jump directly into delivery or operations.
Getting Started
Launch the first site, choose the right defaults, and understand the shortest path to value.
Product Model
Understand the site workspace, the main abstractions, and how the app is organized.
Brand And Locales
Learn how brand guidance, corrections, reports, and approvals shape quality.
Delivery And Configuration
Configure delivery mode, URL strategy, route eligibility, DNS, and translation profile settings.
Operations
Operate monitoring, billing, reports, recovery, and operator review with predictable spend and visibility.
Structured Content
Use structured-content connectors only when you need field-level translation and writeback workflows.
Product contract
What the product provides
The platform should feel like a set of services a product team can reason about, not a bag of edge infrastructure details.
Core services
Site workspace
A single operational home for one website. Brand, locales, delivery, monitoring, reporting, and advanced controls all hang off this workspace.
Brand guidance
A practical copy brief that helps translated output preserve voice, terminology, and audience fit instead of drifting into generic language.
Locale launch control
Locale reports and approvals make release decisions explicit. Generated output is not the same as an approved market launch.
Delivery policy
Choose who sees localized content, when routes become crawlable, which routes are eligible, and how unknown locales should be handled.
Monitoring and recovery
Keep localized output current with explicit spend, visible change detection, and calm recovery instead of silent background churn.
Structured content workflows
Go beyond rendered pages only when you need field-level translation previews, writeback, or connector-managed localized artifacts.
Where the product fits best
Strong fit
Public marketing, docs, blog, landing, and selected commerce-content surfaces where multilingual reach and controlled quality both matter.
Use caution
Search pages, form-heavy flows, and route classes that are not yet well understood can work, but they deserve narrower rollout and closer review.
Usually exclude
Auth, checkout, cart, account, dashboard, and user-specific flows are not the right default target for generalized localization delivery.
What the product is not
It is not a replacement CMS, not a command to translate every route indiscriminately, and not a substitute for product judgment when launching a real locale in market.
Use the right page
Common journeys
Different teams land on the product with different goals. These starting points keep the path obvious.
I want to launch quickly for real users
Start with runtime-only delivery, approved locales only, and one or two launch markets so the review loop stays fast and clear.
I want the product model to make sense first
Start with the workspace and service abstractions before you touch settings. Clarity here makes every other page easier to use.
I need stronger quality and terminology control
Invest in the brand profile, protected terms, and human corrections before you widen the locale footprint.
I need crawlable localized SEO
Use indexable SEO mode, narrow the eligible routes, and treat validated final output as the release gate for search exposure.
I need predictable spend and calm operations
Understand units, passive mode, monitoring costs, and report workflows before you rely on automation for freshness.
I need field-level translation and writeback
Use structured-content connectors when rendered page localization is not enough and editors need entity-level control.
Workspace
How the app is organized
The app is organized around the site workspace because most customer intent revolves around one website and its evolving multilingual policy.
Main product surfaces
Home
Paste one URL, choose the first delivery posture, and see the launch runway in one place.
Site
The center of the product. Brand, Locales, Delivery, and Monitoring all live here because they describe one operating system for one site.
Billing
Understand headroom, choose the right plan, add top-ups, and avoid launching into a low-balance surprise.
Reports
Review locale artifacts in a format that can actually support sign-off, discussion, and launch readiness.
Admin
Use advanced controls for route insight, recovery posture, translation memory visibility, and structured-content connector workflows.
Read this next
- Read Getting Started if you have not launched a site yet.
- Read Product Model if the app surfaces or abstractions still feel fuzzy.
- Read Delivery before changing rollout posture, crawlability, or route eligibility.
- Read Operations before enabling monitoring or scaling the spend profile.