Solving the Multilingual Puzzle
summary
Drupal 8 multilingual setup for a large nonprofit shows concrete wins and costs: uses URL path prefix detection, enables content/config/interface translation per-entity and per-field, and adds Linkit, Transliteration and Search API fixes; Views get an interface language filter and an admin language column; a custom preprocessor uses the node getTranslation method to render chapter navs per language. Team estimates a ~33% project overhead; solution works but requires careful preplanning and QA.
AI-written summary · about
chapters (11)
- 0:00Introduction to multilingual setup
- 2:45Adding custom languages
- 3:08Types of translations in Drupal
- 8:03Improving editor experience
- 12:39Tips for site builders
- 15:48Design considerations for multilingual
- 17:16Front-end translation best practices
- 21:51Custom navigation for translated content
- 24:40Project planning and budgeting
- 27:51Key takeaways and final advice
- 28:37Q&A session
