Opening to apply One Mozilla blog theme to blog.mozilla.com/addons Owner: Justin Scott Deadline: March 29, 2012
Would love some more details on this.
@fligtar Sure thing, I'm sorry I haven't been able to catch up with you sooner. Earlier we had some conversations with Val about merging Add-ons into the main blog. As an interim step, which will allow for separate blogs to stay separate, we're uniting all official Mozilla blogs (as specified by PR) by applying a branded visual theme. This theme will help identify to users, press, etc. that a particular blog is official (we have more than 100 blogs on the domain). We won't need to merge your blog, and the result will be positive for all. Additionally, creative and webdev teams will only maintain this single theme v. the dozens out there, so we're making the most of our resources. Wiki: https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Universal-Blog-Theme Pros: Responsive layout - this theme is fully responsive Customization - there are four approved color schemes/backgrounds you can choose from, and the Add-ons graphic will be added into the logo spot, as well as decide on a 2 or 3 column layout Plugins - we will enable a multilingual plugin for L10N efforts, as well as a few others listed https://wiki.mozilla.org/One-Mozilla-Project/Documentation/Universal-Blog-Theme#Plugins_Included_in_the_Updgrade Social - we will add the universal social sharing asset when it's ready Tabzilla - built-in Ongoing development - we will continue to optimize Blogzilla features on an ongoing basis --- Before this is applied, I'll walk you through the theme in a short 1:1. Lastly, I'll upload a screen capture here tomorrow, unfortunately there's no staging for Wordpres, so I can't point anywhere.
Bulk move to Websites::blogs component, per bug 1353528
Component: blog.mozilla.org → blogs
Component: blogs → WebOps: Blogs
Product: Websites → Infrastructure & Operations
Old bug; the One Mozilla theme was applied long ago.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.