Automating WordPress Translations
One of the strong points of WordPress is that it's easy to translate the tool itself. As discussed in [Translating WordPress Themes](https://publishing-project.rivendellweb.net/translating-wordpress-themes/) the process for translating WordPress elements is as follows: Add a domain to the `style.css` theme boilerplate to make sure that WordPress doesn't confuse the translations of your content with other plugins, themes, and the core itself. ```php /*! Theme Name: rivendellweb Version: 1.0.0 Text Domain: rivendellweb */ ``` Then you need to change the way you write strings for WordPress. Instead of using the raw `echo` command, like this: ```php ` or cancel if you change your mind. The last step, once you've completed the translations, is to export to a PO or POT format. One way to do it is to click on the Export link at the bottom of the screen and keep it the default settings as they are.  Links to import and export translations from Glotpress ## Conclusions POedit and Glotpress have their advantages and disadvantages. One thing you could consider is using them together. Use POedit to generate your first, automated, pass at translation, and then upload it to Glotpress and let your colleagues and your localization contractors work with the translations there. There are other ways where on their own or both together these tools can be useful for translating WordPress themes and plugins. This is a starting point for you to work on your own translations.