Projects help you organize content items that need to be translated using a specific service, workflow, and target language set.
You can create translation projects either directly in the Localization Hub or from your connected CMS (for example, Sitecore, Contentful, or Optimizely).
If you want to learn how to create a project directly from your CMS, see one of the dedicated guides:
Below you'll find the instructions on how to create new translation projects in Localization Hub.
1. From the dropdown in the top-left corner, select the Workspace you need.
2. Open the New Project page from the vertical menu.
⚠️ Can't find the "New Project" page, Targeted or Dynamic projects? Check whether Project creation restrictions are enabled in Settings → Details. Note that some connectors do not support Dynamic Projects.
3. Decide whether you'd like to create a Targeted or Dynamic project.
Targeted Project
A Targeted Project is a manually created translation project in the Localization Hub where users select specific content items (pages, blocks, or assets) to send for translation.
When a Targeted Project is created, Content Analysis is automatically performed to detect changes in the selected content.
Unlike Dynamic Projects, jobs are created for all selected items, regardless of the analysis results.
When exporting a project to the translation tool, you can choose whether to send only the content that has changed or all content.
💡 Best for: Manual, one-off, or campaign-based translations where users need full control over which content items are included.
If you selected the Targeted project, move to section: How to create a Targeted Project.
Dynamic Project
A Dynamic Project is an automatically analyzed translation project in the Localization Hub that helps users detect and translate only new, updated, or missing content.
When a Dynamic Project is created, the system runs Content Analysis across the entire CMS content or selected areas to compare the latest source content with the previously translated version.
Jobs are then created only for content that contains changes, ensuring that translation effort focuses exclusively on updated items.
💡 Best for: ongoing website localization, continuous content updates, or large-scale projects where automation helps reduce manual selection and translation costs.
If you selected Dynamic Project, move to section: How to create a Dynamic Project
How to create a Targeted Project
- Select a service you would like to order. A service defines a set of settings used for content transferring.
2. Select Domain.
⚠️ Can't see Domains? If you can't see domains, this means that either there are no domains set up in Localization Hub or they are not connected to the service you selected.
3. Select the Requested due date (optional). It is the date by which you expect the project to be completed. Translators can view this date in the Localization Hub.
This date appears in the Due column within the table listing all jobs in the project.
The Actual Due date matches the Requested Due date unless translators set a different due date in the translation tool (if supported). If it doesn’t update, check that the project is synced with the translation tool.
For new projects: The requested due date is assigned to both the entire translation project and all jobs created within it. You can adjust the due date for individual jobs later if needed.
For existing projects: If you add jobs to an existing project, the requested due date applies only to the new jobs and does not affect the overall project due date.
4. Select the Project type — Personal or Shared.
Personal — only you and users with "Access all projects" permissions can view and manage the project.
Shared — everyone with access to the same Workspace can view the project and add jobs to it.
5. You can create a new project or add content to the existing one.
Select New if you need to create a new project.
Select the project number if you would like to add jobs to the existing project.
If only the New option is visible, no projects match the selected parameters (Service, Domain, Project Type).
6. Provide the project name.
Each project is given a specific automatically-generated number but you can provide a user-friendly name. This option is available only for newly created projects.
7. Add instructions to the Briefing.
The instructions will be added to all jobs and seen as tooltips near the Jobs' IDs in the Jobs tab in the Project. These instructions will also be sent to the translation tool or other systems encoded in the XML file.
8. Select the Cost Center. Cost Centers help to define to which department the project must relate.
⚠️ Can't see Cost Centers? If you can't see cost centers, this means that either there are no cost centers set up in Localization Hub or they are not connected to the service you selected.
Once project details are specified, move to the next step.
9. Check the content items you need to order for translation in the content tree.
If you need to find a certain content item, use search, Last Updated and Content type filters. After you choose the filters, click the Apply filter button.
💡 Note: the filters can be different for different CMSes.
When you click on a specific content item, you will see detailed information about the content item in the right sidebar.
To expand or collapse the content tree, use the button in the right corner above the content tree. There, you’ll also find the refresh button that you can use if you need to instantly reload the tree.
When selecting items in the content tree, you may notice that some items have more light grey colors and are in italics. Such items can’t be selected as they are either virtual elements or do not correspond to the filter options and are shown only for the correct structure of the content tree.
After you checked all necessary content items, move forward.
10. Check the required target languages and move to the next view.
In case you have one target language and multiple source languages, please read how to create projects with multiple source languages.
11. At the end of the order form, you’ll either create a new project or add jobs to an existing one — based on your earlier selection.
Create – Starts a new project without launching it. You can add more jobs later.
Create & Launch – Creates and launches the project immediately. No further jobs can be added.
Add jobs – Adds jobs to an existing open project. You can continue adding more before launch.
Add jobs & Launch – Adds the jobs and launches the project in one step.
💡 Button names may vary depending on your service setup (e.g., “Submit” or “Send for Translation”).
How to create a Dynamic Project
Analysis Scope
1. Select Dynamic Project Service from the dropdown. In the selection, you'll see only those services that support "Analysis" step in their workflow.
💡 Note: The service for the Dynamic project can be changed later during the transition to the next step in the workflow if necessary.
2. Select Analysis Criteria:
- Missing block language versions – Content blocks missing translations of the selected target languages.
- Missing page language versions – Pages never translated before in the selected target languages.
- New properties – Newly added content fields.
- Outdated properties – Updated content since the last translation.
3. Choose the Target Languages to analyze for missing or outdated translations.
4. Select the Services to be used for Content Analysis. Only content ordered for translation through the selected services will be included. You can filter the content by Last applied service or All applied services:
Last applied service — Shows and analyzes only content whose most recent translation was completed using one of the selected services.
All applied services — Shows and analyzes any content that has ever been translated using one of the selected services.
💡 Note: You can change Analysis Criteria after the project is created. For Dynamic Projects that use the “All content” option for analysis, you can update the Target Languages and Services for Content Analysis later as needed.
5. Content Selection. Choose:
Analyze all content – Full CMS scan (slower).
Select specific content – Faster, focused analysis.
💡 Tip: For large CMSes, start small with a few items to test the analysis setup.
Project Details (Optional)
💡 Note: The parameters below can be modified after the project is created.
Add a Requested due date. It is the date by which you expect the project to be completed. Translators can view this date in the Localization Hub.
This date appears in the Due column within the table listing all jobs in the project.
The Actual Due date matches the Requested Due date unless translators set a different due date in the translation tool (if supported). In that case, the Actual Due value will be updated accordingly. If it doesn’t update, check that the project is synced with the translation tool.
2. Specify Project name. Each project is given a specific automatically-generated number but you can provide a user-friendly name. This option is available only for newly created projects.
3. Add instructions for the jobs to Briefing. The instructions will be added to all jobs and seen as tooltips near the Jobs' IDs in the Jobs tab in the Project. These instructions will also be sent to the translation tool or other systems encoded in the XML file.
4. Choose a Project type:
Personal Project – visible only to you and users with "Access all projects" permissions.
Shared Project – accessible to other team members.
Personal projects will appear with a shield icon beside their name.
5. Select Domain.
⚠️ Can't see Domains? If you can't see domains, this means that either there are no domains set up in Localization Hub or they are not connected to the service you selected.
6. Select the Cost Center. Cost Centers help to define to which department the project must relate.
⚠️ Can't see Cost Centers? If you can't see cost centers, this means that either there are no cost centers set up in Localization Hub or they are not connected to the service you selected.
Once project details are specified, move to the next step.
Summary
Dynamic Project Mode
Dynamic Projects can operate in two modes:
One-time – The project will run analysis once. To analyze again, you can trigger it manually or switch the mode to Continuous.
Continuous – the project will automatically rerun analysis on a set schedule using the saved criteria, target languages, services, and content scope. When you create a Dynamic Project in Continuous mode for the first time, an automation is created automatically. You can adjust its schedule in the Automations tab of Workspace Settings. The automation is named: [Service name] analysis automation.
💡Tip: Use Continuous mode for ongoing web or product localization to keep translations automatically up to date.
Create or Analyze the Project
Once you reviewed the project summary, click:
Create – Creates the project but does not start analysis yet (you can run it later).
Create & Analyze – Creates the project and immediately starts Content Analysis.
Once the project is created, you’ll see it appear in your workspace with status Analysis.
📖 Read more about the actions available during the Analysis step.
Comments
0 comments
Please sign in to leave a comment.