Since the beginning of WordPress the desire to publish the content in different languages is huge. But the topic can quickly become complex, because not only the rendering of content in the form of text in different languages is an issue, we also have to take care of the meta data for content, for images that can be different depending on the language and the use of the admin interface in the preferred language. Thus, only a part would be covered depending on the requirements (a example on StackExchange) it would quickly become an project and WordPress would be just a "small" framework behind it. There are already many Plugins available, the different approaches - new tables in the system or separation of content for each language in a table entry to post, or other solutions.
All these solutions have their limitations, are inflexible and you go into a dependency that will be hard to get out and with each update of WordPress you have to check if the Plugin is still working or has any bugs with the new version. Therefore, I would suggest a solution that we use in our Inpsyde Team frequently for customers and maintained their strength in the flexibility, in extensibility and in its capacity to use the WordPress standard without changing the core or anything else. You can deactivate the Plugin at any time, you won't lose anything, your website remains the same.
- 2/3, if not even more, of the worldwide population speak another language
- Go global with your company
- Better distribution of content
- Service for the client
- Search Engine Optimization
WordPress Multisite provides the solution already.
This makes the management of different instances, with similarities and differences, with the help of an installation possible. The exchange of data is possible via core functions, which get united and simplified via Plugin.
- WordPress Core Functions
- No dependency to Plugins
- Independent to WordPress development*
- Control Themes, Plugins at a central place, use them decentralized
- Low maintenance
- Seperating languages in Backend/Frontend (user dependent)
- Complete mirrored or in every content form seperated
- Subdomains or Subdirectories
- de.example.com, example.com/de
- Seperate Domains via Domainmapping
- example.de, example.com
- Free in development in design and usability
- Optimization not only on frontend, also lang-attributes, SEO
With all these requirements and benefits, we use a base that is available as a Plugin here: MultilingualPress . The plugin provides several convenient tools to use Multisite for the implementation of multilingualism.
This plugin simplifies the identification of different blogs in the network to a language and linking to other blogs, so that when you publish the content in blog A, it will create a post as draft in blog B. Thus, the articles are in relation, the system knows this and with the help of some functions, it may be used in the frontend and backend.
The Plugin provides in the article or page the ability to see a meta box with the content of the linked data, in the simplest case as a translation aid. Similarly, there is a widget that simplifies the frontend to change. In each blog you can be make some adjustments, assigning a flag and language.
WordPress Multisite provides the basis and with some adjustments, a clean, controlled solution exists for the use of WordPress in a multilingual environment. Now it's up to you - use Multisite, Test the Plugin and give us a feedback.
This was our last door of our Advent Calendar. We hope you enjoyed it!
We wish you a Merry Christmas and thanks a lot for reading our posts!