> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/motors-theme-documentation/customization/localization.md). # Localization You can change your site's main language via **Settings -> General -> Site Language** It’s easy to localize your site using [Loco Translate](https://wordpress.org/plugins/loco-translate/) plugin. Here you can see the related tutorial – ]\(). Another way is to add your translations via creating your own .po files. Before adding translations for static strings, it needs to rename language files correctly according to your site languages. Theme language files are located in a **../wp-content/themes/theme-folder/languages/**folder. You can find a list of language codes here [WordPress in your Language](http://codex.wordpress.org/WordPress_in_Your_Language). As an example, the language code for English is **en\_EN**, so you would save the translated files as en\_EN.po first, then en\_EN.mo. There are several ways to fill up translations. One of them is using [PoEdit](https://poedit.net/) platform. You can add translation via editing your **.po** file and at the end **PoEdit** generates **.mo** file for you. Then you need to upload ready translation files to primordial folder (../wp-content/themes/theme-folder/languages/). Motors theme includes ready translation files for 6 languages: **Arabic**, **Germany**, **Spanish**, **French**, **Italian,** and **Portuguese**. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stylemixthemes.com/motors-theme-documentation/customization/localization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.