Integrating Integrations: A Tale of Two Vendors at DrupalCon Portland

Staff Reporter

A complex data structure, a very active marketing team, and not one but two translation vendors: if this doesn't sound daunting enough, imagine if those two vendors weren't able to talk to each other out of the box. That was the status quo at Pega until 2020. On the one hand they had Lingotek, well known for its seamless Drupal integration. On the other they had Acclaro, our provider of excellent translation services. What they had standing between the two was a painstaking work of copy and paste, many spreadsheets, and a lot of frustration.

What made everything even more urgent was that Pega Academy, their new learning site, was going to start offering multilingual content in early 2021. They had a few main goals:

Put a stop to the copying and pasting, and allow their data to flow between both vendors' APIs.
Use Drupal as the main control center, to provide as much information as possible in a single place, and limit the number of clicks and open tabs required of their localization specialists.
Create a process that would allow translating tens or hundreds of related nodes at a time, without anyone having to hunt around for each individual one.
In true Drupal fashion, avoid reinventing the wheel. Instead, reuse and improve on what is already there.

This session by Tony Savorelli, Pegasystems focuses on the driving criteria behind their development effort, the technical building blocks, and a small demo of the completed work.

Follow TheDropTimes on LinkedIn for more updatesFOLLOW

Comment

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please let us know in the comments below and we will try to address the issue as best we can.

Integration