GSoC Menu Customizer Revised Schedule/Scope

Previously: GSoC Project Proposal: WordPress Menu Customizer. Week 1 – 5/19: Introduce the ability to view all existing menus as customizer sections with menu items as customizer controls. Week 2 – 5/26: Add the ability to edit menus (change labels, attributes, re-order items), including a temporary solution that includes the screen options found on the existing menus screen. Run user tests on…

GSoC Project Proposal: WordPress Menu Customizer

Please note that this post only contains the Project Description and Schedule of Deliverables sections, as they are the most relevant to public discussion. Project Description Describe your idea in detail: WordPress 3.9 introduces the Widget Customizer: a better way to edit widgets. This is a major step in the process of migrating every component of WordPress’ Appearance menu to…

On Contributing to WordPress Core

I’m honored to be featured on the WordPress 3.8 Credits page as a Contributing Developer/Recent Rockstar (Matt decided to list everyone in one big group this time instead of breaking it up, but the group is ordered randomly by a level of regularly active developers—the traditional “Contributing Developers”–and a level of developers who showed increased involvement and significant help in…

A screenshot of the Twenty Fourteen theme with the Fourteen Colors plugin, featuring a light gray contrast color and a light blue accent color

Custom Colors in Twenty Fourteen

Twenty Fourteen is WordPress’ shiny new default theme, released Thursday alongside WordPress 3.8. I worked with the Twenty Fourteen development team throughout the cycle, doing everything from proposing features to removing features to proposing design tweaks, fixing bugs, and testing the theme everywhere. Twenty Fourteen features black, white, and green as its primary colors. In September, I introduced an “Accent Color”…

Thirteen or Fourteen Colors

You may have noticed that I’ve added my eighth plugin to WordPress.org: Fourteen Colors. It adds color customization to the new Twenty Fourteen default WordPress theme, half of which was developed in the core theme before being removed yesterday, just over a week before the theme’s release (broader explanation coming soon).

In the next week, I’ll build out Fourteen Colors, creating what I hope is my most polished plugin yet, inside and out. I already know that I’ll be further utilizing the function that generates color variants, which I wrote when the feature was developed for the core theme, to ensure the highest color contrast possible given various contexts within the theme.

I also created a plugin to customize the (much bolder and more varied) colors of the Twenty Thirteen theme, entitled Thirteen Colors (that plugin is much less elegant than I hope Fourteen Colors will be). I’m starting to wonder why WordPress’ default themes don’t place an emphasis on built-in visual customization. Twenty Eleven was the last to have comprehensive color customization options, or even a link color option, for that matter.

The reasons that the custom accent color was removed from Twenty Fourteen seem referable to the broader lack of customization available in default themes. Hopefully, Fourteen Colors can successfully provide an answer to the concerns over giving users the power to make “bad” color choices, at least in terms of readability if not in terms of beauty. As for code complexity, maybe it’s time to consider customization as a component worthy of adding some weight, like featured content is in Twenty Fourteen. At the end of the day, these themes are the first thing users encounter when getting started with WordPress, and it seems wrong not to showcase the power and flexibility of the platform in the first-run experience (the ability to easily browse for new themes is also critical here).

Maybe Twenty Fifteen will bring the power of native visual customization back to the end user. After all, we have a wonderful Theme Customizer that works excellently for visual customizations. I’d love not to create a “Fifteen Colors” plugin next year.

WordPress 3.8 Is Going to be Awesome

WordPress 3.8 development is heating up, with huge developments in the last few days. MP6, the now-infamous visual redesign of WordPress, DASH, a much-needed refresh of that Dashboard screen that we all habitually ignore, THX, a gorgeous new theme-browsing experience, and many smaller components have been merged into WordPress trunk, the development branch, after being developed as plugins first. And…

Fixing a 9-year-old Typo in WordPress

I just patched a fix for a small grammar error in the instructions at the top of the Permalinks Settings page in WordPress (#25210). It fixes a sentence that Matt Mullenweg wrote in 2004 and hasn’t been touched since. I can’t believe no one noticed this over the past 9 years and millions of WordPress installs.

Needless to say, Sergey Biryukov committed the fix within a couple of hours. So, I guess that’s my contribution to WordPress 3.7. I’ve already made more substantial contributions  (both in code and discussion) to WordPress 3.8 via Twenty Fourteen, but I don’t expect to touch much else in 3.7 since it doesn’t address any UI components.