Panel on building multilingual websites
summary
Panel explains concrete choices for multilingual WordPress sites: use WPML or multisite to keep each language as its own object, avoid plugins that store multiple languages in one post, and expect extra budget and time for translation and QA. WPML has a translation manager, wide plugin compatibility, and moved from lifetime to annual licensing; common pitfalls are poor editor workflows, mobile language switcher placement, and untranslated taxonomy — primary language first use professional translators.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 11:10What to do if someone asks for your help
- 13:40What percentage of your clients require multilingual
- 16:17Who translates for you
- 20:05Major pitfall of WPML
- 22:50Challenges of building multilingual websites
- 35:00One sentence
- 36:03Prepare yourself
- 36:38Random comment
- 38:10How can we tackle this
- 39:39Flags
- 41:30Home Page
- 41:55Splash Page
- 43:00Extra Click
- 44:11Language Switcher
- 45:30WPML Support
- 47:48Language Switchers
