The idea of multilingual web publishing sounds straightforward enough. A publisher operating in multiple countries, or in a country where multiple languages are spoken, needs the ability to manage content – as well as site features like navigation – in multiple languages.
But having worked on many such projects in my career, I can assure you that multilingual publishing means different things in different situations. Is content always created in one particular language, then translated into the others? Or can content originate in any of the operational languages? Is every piece of content translated? If so, when, and by whom? If not, what do you do when a piece of content isn’t available in the language being viewed?
WordPress has been fully translated into dozens of languages, from Afrikaans and Albanian to Vietnamese and Welsh; but it doesn’t have a built-in solution for multilingual operation. While that might initially seem like a negative, it means there is scope for a number of different approaches, reflecting the different scenarios and workflows associated with multilingual publishing.
At last month’s Big WP event in London, Giuseppe Mazzapica from VIP agency partner Inpsyde reviewed the approaches taken by some of the best known WordPress plugins, noting their respective strengths and weaknesses.
Inpsyde are, of course, the agency behind Multilingual Press, the multilingual plugin we use most often at VIP. Its approach, based on the multi-site mode built into WordPress, stays closest to ‘normal’ WordPress operation. This means other functions, including third-party plugins, are much more likely to work without workarounds.
But the VIP platform also supports other solutions, which may be a better fit for certain clients, their requirements, and their workflows. Our engineers are always happy to talk through the workflow needs of any given project, and help our clients make the right choice.
Thanks to Chrissy at Inpsyde for the beautiful featured image on this post!