Setting up Your Local Site

Now that you’ve translated WordPress into your language, it’s time to create a website for your localeLocale Locale = language version, often a combination of a language code and a region code, for instance es_MX denotes Spanish as it’s used in Mexico. A list of all locales supported by WordPress in https://make.wordpress.org/polyglots/teams/. These are called RosettaRosetta The code name of the theme for the local WordPress sites (eg. bg.wordpress.org is a “Rosetta” site). All locale specific WordPress sites are referred to as “Rosetta sites.” The name was inspired from the ancient Rosetta Stone, which contained more or less the same text in three different languages. sites (after the great Rosetta Stone) and will be setup at [lang].wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. For example, Portuguese has the language code of “pt” and is given a domain of pt.wordpress.org..

A Rosetta site is your gateway to your local community. It is also the place where people go to download WordPress in your language. Rosetta sites are also used to give means of communication with local WordPress contributors and showcase great websites created with WordPress.

Setting up a Rosetta Site Setting up a Rosetta Site

When you request a new locale, you can also request a new Rosetta site for your community. Setting it up is as easy as setting up any WordPress site. It is recommended that it has a team page, a contact page, a blog and a showcase page and a page explaining potential contributors how to join the translation team.

Top ↑

Adding your team to your site Adding your team to your site

The first thing you should do is add your team members to your brand new site. Unlike a standard WordPress installation, Rosetta sites have a a couple of additional roles that are used for giving permissions to translation editorsTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor. Those are integrated with Translate WordPress’s user permissions, and will give that users the right to approve suggestions and corrections.

You also have a way of giving translation editorTranslation Editor Translation editors can approve translations for projects. The GTE (General Translation Editor) and LM (Locale Manager) roles can add new users with the "Project Translation Editor" role that can approve translations for specific projects. There are two different Translation Editor roles: General Translation Editor and Project Translation Editor permissions for specific projects. Read more about it in the Roles and Capabilities section of the handbook.

Top ↑

Configure your site’s pages and menus Configure your site’s pages and menus

Configure your site’s pages and menus, to be found under the Pages menu and the Appearance > Menus items on your WordPress Admin Screens. Some pages need a specific page template to work, so please don’t change that.

gFPzlxahv8LIeqKhYzz2gjmepx8-j8yQcNhzgmp4Pow

 

Also, whenever you see “Please, neither delete this page, nor change its slug! The contents of this page are filled automatically, you don’t need to spend time here. Just change the title.” as the content of a page, well, don’t delete it and don’t change its slug.

SEg88Hw8oeQ52y6EdTXorwtuuTyBeB_J1Et5e-cCQUw

 

Top ↑

Configuring the HeaderHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. Image Configuring the Header Image

The header image can be configured at https://[site]/wp-admin/themes.php?page=custom-header, where [site] is your Rosetta URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. Be sure to upload an appropriately-sized image.

[Expand this page with screenshots and directions for getting to this page through the admin interface.]

Top ↑

Making your site RTL Making your site RTL

If the text direction of your Rosetta site needs to be RTL (right-to-left), you can configure that yourself by translating a specific this string in the WordPress project (Please change the locale in the URL with your own locale code). For the change to take effect, you will need to request a deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. and wait for the Polyglots technical lead to deploy the changes.

Screen Shot 2015-09-16 at 10.25.45 AM

The above process will make your Rosetta site, local theme repositoryWordPress Localization Repository The WordPress Localization Repository at https://i18n.svn.wordpress.org/ is a Subversion repository where official WordPress translations are maintained. See Working with the Translation Repository for details. and local forums RTL.

Making your pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party repository RTL

The plugin repository is not covered by the process above. To make your plugin repository RTL, please  post a request on the Polyglots blog.

Top ↑

Administrative Processes Administrative Processes

[Backend processes required for admins to create Rosetta sites or make changes only admins can make.]