Who should use the Website Localization workflow?
Teams or solo builders working on development tasks who want a repeatable process instead of one-off tool experiments.
Execution Map
5-step pipeline — follow each step in order
1Setup · Step 1 of 5
Open task pageNeural Machine Translation
Prepare inputs and settings through Neural Machine Translation before running website localization.
Why this matters
Neural Machine Translation sets up the foundation for website localization; clean inputs here reduce downstream rework.
What you get
Inputs, context, and settings are ready so the workflow can move into execution without blockers.
More optionsCompare
2Input · Step 2 of 5
Open task pageLanguage Detection
Use Language Detection to build supporting assets that improve website localization quality.
Why this matters
Language Detection strengthens website localization by feeding better supporting material into the pipeline.
What you get
Supporting assets from language detection are prepared and connected to the main workflow.
More options
3Core · Step 3 of 5
Open task pageWebsite Localization
Execute website localization with Website Localization to produce the primary final deliverable.
Why this matters
This is the core step where website localization actually happens, so it determines baseline quality for everything after it.
What you get
A first-pass final deliverable is generated and ready for refinement in the next steps.
More options
4Refine · Step 4 of 5
Open task pageGenerate website layouts
Refine and validate website localization output using Generate website layouts before final delivery.
Why this matters
Generate website layouts adds quality control so issues are caught before the workflow is finalized.
What you get
The final deliverable is improved, validated, and prepared for final delivery.
5Deliver · Step 5 of 5
Open task pageOptimize website performance
Package and ship the output through Optimize website performance so website localization reaches end users.
Why this matters
Optimize website performance is what turns intermediate output into a usable, publishable result for real users.
What you get
A finalized final deliverable is ready for publishing, handoff, or integration.
More options