AEM 6.2 Cloudwords Connector User Guide


Cloudwords Connector provides an interface between Adobe Experience Manager(AEM) and Cloudwords products. The connector functionality enables adding the content required for translation from AEM. The content can be pages, assets, assets metadata, tags, tags metadata and i18n dictionaries. These all content are present under an AEM project. Connector enables sending the project containing source content into Cloudwords. As soon as user logs into Cloudwords account the project is already created and the source files are uploaded into the project. Once the entire vendor selection and bidding process is completed, the translations are available in Cloudwords for review. The translated files are then imported into AEM and are available for review at AEM side.


The scope of the document is to provide details on how to use Cloudwords Connector with AEM. This includes Project creation at AEM, adding pages to the created Project and sending it out for translation to Cloudwords.      


  • Cloudwords Account (Access to URL and API key)
  • Adobe Experience Manager 6.2 installer
  • Cloudwords Connector Package installed
  • Cloudwords Connector Installation completed (Reference - Installation Guide)
  • Page versioning feature should be enabled on AEM environment to restore the content whenever required 

Using Project Creation Wizard to add source files for translation

The project creation wizard provides an interface to create projects and add the pages required for translation.

1) Sign in to AEM home page and navigate to Project Creation Wizard by accessing URL: http://<host>:<port>/projects.html


Click on Top Navigation -> Projects, the project management interface can be accessed.


2) Click on Create -> Create Project. 

3) Select ‘Translation Project’ and Click on ’Next'

4) Project Creation Interface opens which consists of Basic and Advanced tabs. Values can be added in both the tabs here are the details:

Basic Tab - Title(required), Description(optional), Due Date(optional) [No need to add any users in Users option]

Advanced Tab - Name(required, automatically filled), Source Language(required), Target Language(required), Translation Method(required), Translation Method(required, value should be Human for Cloudwords), Translation Provider(required, Cloudwords), Cloud Config(required, Cloudwords Configuration where URL and API key are added)

New Input fields on the advanced tab will be added as soon as you select ‘Cloudwords’ in Translation Provider selection.

New Fields on Advanced Tab if Delta Content translation and Delta project level option is enabled:

  • Enable Delta Content translation: Checkbox to enable delta feature for this project. (Note: If disabled, then all previous files of this project and metadata files for delta feature will be deleted.)


5) Click on ‘Create’ button present on top right corner and a dialog Box with Success/Error message should open. Now Click on ‘Open’ to add pages to the view created project details and to have access to Translation Job widget to add pages which are required for translation. 


6) Click on elipses below ’Translation Job’ widget or click on ’Translation Job’ hyperlink text. An interface to add pages to the project should open.

7) Click on ‘+Add’ button. This provides option to add AEM Pages/Assets, any internationalisation dictionaries used for content creation and even Tags. Any option can be selected as per the requirement.
for now let’s say Pages need to be added in the project.
8) Select ‘Pages/Assets’ and content browser containing all the content present on AEM instance would open. The pages required for translation can be selected. 

9) In case language copy of the ‘target language’ doesn’t exist, then a Warning Alert box opens. This one has option to either ‘Create Language Copy’ by clicking on the button or to replace the source language content with the translations by clicking on ‘Overwrite’ button. 

Following are the use cases to be taken into consideration:

1. If language copy of Target language exists, then add Target Language Pages. In this case the dialog box to Override or create Language copy wouldn’t populate. For e.g., in case source language = 'en' and target language = 'fr', then while adding the pages select from ’fr’ node. In case if ‘en’ pages are selected, then the dialog box would open and either Override or Create language copy again.
2. If language copy doesn’t exist, then add source pages and the dialog box would come, then either override or create language copy as per the requirement. For e.g., source language = en and target language = fr, then while adding the pages select pages from ‘en’ node. Then if language copy needs to be created then Create Language copy from the Dialog box .

10) Once the pages are added, by clicking on ’Translation Job’ on the top, select the current project to go back to Project Details interface.
11) Click on the arrow besides ’Translation Job’ and then click on ’Start’. This will initiate the translation process.
If there is no error, then a success message on top should be shown and the Project Status (just below Translation Job) should change to ‘Committed for Translation’ from ‘Draft’.
But in case of any error, an error message in red should appear on top of the screen and the Project Status should be ‘Draft’.

Using Sites to add source files for translation

The projects can be created and pages can be added to it even from Sites section. The limitation of this approach is that language copy of the target language site should already exist and the interface is not that intuitive. But the advantage is that multiple language can be selected as target language in one go.

Prerequisite: Language copies should be created for required languages before proceeding with this approach. Reference -


1) Navigate to Sites interface by accessing URL: http://<host>:<port>/sites.html


Click on Top Navigation -> Sites, the sites interface can be accessed.

2) Select the page in Sites console which needs to be sent for translation.

3) After selecting the page, click on ‘References’ tab from left panel. On expanding ‘Create & Translate’ widget, all language copies codes should be available for selection.  


4) On selecting multiple languages, an information message would be displayed on the top stating the created translation projects. Since multiple languages are selected, corresponding multiple projects would be created with required project details.


5) On accessing the Project Interface (http://<host>:<port>/projects.html), a folder containing required languages projects is available.

After this, above mentioned steps from 6) to 11) can be repeated to send the project for translation.

For further details, please refer to -

Cloudwords Translation Process

1) Once the translation process has started from AEM end, one can login to Cloudwords. The project with same Title(as AEM’s project) and details like Description, Department and Due Date should be available on Cloudwords. Click on Next to validate further details.

2) The pages which were added to the translation project should be present in Source materials of Cloudwords project. The source and target languages should also be pre filled with the same values which were selected during AEM’s project creation. Click on Next to wait for bids in case bidless option isn’t configured (this depends on how one’s Cloudwords account is configured, please contact Customer Success team for further details).


 3) In case Bids are required to be selected, please select them.

 4) Once the bid is selected, the translations are available for review depending on vendor selection (Project Status - In Review).

5)  Click on Review to review the provided translations. The OneReview process is generally generated once the scheduler runs after defined time in configurations.

In order to generate the preview instantly, go to AEM’s project wizard and refresh the screen once. The translation job status should change to ‘Translation In Progress’. In case there are no exceptions, the preview should get generated in couple of minutes (depending on factors like network bandwidth, number of pages sent for translation and content present on the page).

In this step, a fake import of translations received from Cloudwords to AEM is done. So versioning of the pages should be enabled, so that the content can be restored whenever required.

Click on Review button to review the received translations.


6) The translations can be Approved or Rejected as required.

7) Once the translations are approved in Cloudwords, the translated pages are imported into AEM and can be opened in AEM.



Have more questions? Submit a request


Please sign in to leave a comment.