Alert: This page is still a draft and being actively written. If you find an error, please comment below.
Translating WordPress is a big responsibility. Distributing a localized version on WordPress, hosted on WordPress.org, is a bigger responsibility. Because WordPress in your language may be downloaded by millions of people all over the world, there are certain expectations the Polyglots Team has before giving you a locale-specific WordPress.org subdomain.
A “Rosetta” site is a localized version of WordPress.org that serves as the entry page for users of your locale. Each Rosetta site consists of the following pieces:
A front page with included download link at [locale].WordPress.org
A showcase featuring WordPress sites in your language
A contact page
Other pages as needed
Optionally, if your locale meets certain requirements, you may request localized forums.
Rosetta sites work best when they have been translated into the language they represent. That’s why your first job as an editor of a new locale is to prepare your Rosetta site for people who speak your language, but don’t speak English.
Some links to third-party (external) community sites, such as local community sites and links to community support forums (until that feature is added for your locale on WordPress.org) are accepted practice. In the best interest of the WordPress project, additional expectations are listed here:
Rosetta sites are expected to benefit the WordPress community rather than specific business(es) or individual(s). (Note the general expectations for translating WordPress.)
To avoid any conflict of interest, it’s expected that validators and translators will not use their own sites as examples of good WordPress sites in their showcase. The WordPress community is large and examples of WordPress sites are very easy to find.
Rosetta sites are expected to not include advertising and affiliate marketing and to link only to websites that benefit the local community. Rosetta sites can not link to websites containing advertising for busineeses or individuals.
Add a page about Translating WordPress in your language with a link to the development project on Translate.WordPress.org. Some teams include guidelines for translating in that particular language and links to the Glossary of common terms.
To avoid receiving a lot of support requests through the contact form, add a text on top of the page in your language, specifically explaining that support requests will not receive an answer.
Use the blog to announce WordPress releases in your language or local WordPress community events. The blog content of every Rosetta site appears in the News Feed in the administration of every site that has switched to that language.