In this session, senior Drupal Architect Chris Leppanen will outline the history, challenges and solutions for multilingual management modules. Multilingual modules have long been a theme of conversation in the community, hence the Drupal 8 initiative already in tow.

Drupal customers often have to copy and paste their source content into a document they send to their translation vendors, and then copy and paste all the translated materials back into Drupal. The sheer time and error-prone nature of this makes translating Drupal content painful at best, impossible at worst.

There are various ways that translation happens, and there are essentially three different, and sometimes conflicting APIs. Chris developed a innovative way to overcome this and will share best practices with the group. For example, "how do you manage Drupal's Form and Batch APIs when having to perform sequential Rest API calls? What happens when one of the calls fails?"

His solution was a module built to integrate with Drupal and a translation management soultion, Cloudwords. Essentially, take the management part out of Drupal and move it to a dedicated service. Using its best-in-industry integration and API, the Cloudwords Module has made translating Drupal easier.

Pick what Drupal pages, nodes, etc. to send out for translation. Sync content and route it to the translation vendor(s) of your choice. Sync the translated content back into Drupal once your translation vendor has delivered the translated content into the Cloudwords service.