Multilingual is complicated—no doubt about it. We’ve come a long way since Drupal 7, though. In Drupal 8 there is a lot of excellent documentation and blog posts to help with the basics, but the learning curve is steep and the path forward can be more twisted and booby-trapped than a pharaoh’s treasure tomb. However, it doesn’t have to be all shambles, brambles and sharp pointy sticks.
Multilingual has to solve too many needs and interact with too many parts of Drupal to ever be simple. Knowing what to be prepared for, learning the basic vocabulary and having a human-friendly road map on how to translate the varied parts of a complex modern Drupal site will impress your co-workers and might just save your life.
Just like the Rosetta stone provided the clues necessary to decipher ancient heiroglyphics, this session will shed some light on Drupal 8 multilingual by talking about:
- Why/when to use multilingual and its impact on timeline and budget
- Planning for and working with content, configuration and interface translations
- Complex development translations
- Improving the translation experience for editors
- Common boulder traps and solutions
Examples will come from a recent multilingual project for a large non-profit.
Attendees will leave the session being able to make an informed decision on whether or not multilingual is right for their project. When building a multilingual site, developers will be able to plan for and work with content, configuration and interface translations. Developers will also learn how to avoid common gotcha's in the multilingual development process as well as how to improve the editorial translation experience.