New Theme Update

It’s been two weeks since we started switching Rosetta sites to using the new theme. Since then a good amount of bugs were fixed and missing features added. If sites have showcase items for example, they now get displayed properly and replace the global showcase links.

Custom slug for download page
Sites can now declare any page their downloads page, simply by assigning the Download page template, and are no longer limited to the default txt-download. When adding a page to the navigation menu that has either the txt-download slug or the Download page template assigned, it will automatically converted to the download button you’ve seen on the global site. So far I’ve always added that page to the menu when switching to the new theme.

No Built-in Contact Form
With the switch we decided not to continue maintaining the contact form page template, but rather have sites use Jetpack’s contact form builder. The experience there is superior to what we had so far, and more importantly it makes it theme-independent, meaning it’s not something that would need to be carried over from theme to theme.

Switching Remaining Sites
So far we’ve switched sites when their translations reached 100%—19 so far. As discussed in this morning’s polyglots chat, we’ll start switching over the remaining sites a week from now, with the goal of having that completed by the time WCUS happens.

Please let me know in the comments about questions or concerns, or—if you find a bug—please head over to #2861-meta and make a note there. The transition has been as smooth as it could be so far, it would be great if we could continue that 🙂



New Theme Ready for Translations!

As a first step in the effort to bring the homepage to Rosetta sites, we built a new theme to take advantage of the modularity of the base theme and make it easier to later add the enhancements mentioned in #2861-meta.

We tried to lighten the load for translators by importing existing translations from the current rosetta and plugin directory theme, which covered 50% of strings for the more active locales. The project is available at:

We also decided to keep the design as close to the existing Rosetta theme as possible for now. So while you’ll see some changes—primarily in font size and margins—the overall look and feel should not be too far off. The goal was not to revolutionize the way international sites look, but rather to bring the design closer to parity with the root site.

Newly created locale sites will automatically use the new theme. Once the theme is translated to 100% for an existing locale, it will be activated for its Rosetta site. If you do encounter bugs or unforeseen behavior, please leave a comment on #2861-meta.

Thanks to @ocean90 for raising the issue and for his continued feedback on this effort.