Welcome to ManageWP.org

Register to share, discuss and vote for the best WordPress stories every day, find new ideas and inspiration for your business and network with other members of the WordPress community. Join the #1 WordPress news community!


Twenty Fifteen

A case for the new theme

Twenty Fifteen

Over the last 18 months I worked on three default themes, Twenty Twelve , Twenty Thirteen , and Twenty Fourteen . Each project was a little different from the other, and on each project my role differed too. Twenty Twelve was initially designed by Drew Strojny , with Lance Willett creating the templates, leading the project and herding volunteers. It wasn’t ready for WordPress 3.4, but was released with 3.5. I joined them in the 3.5 cycle I started helping out with testing and bug fixes.
For Twenty Thirteen, I was the main developer. Joen Asmussen designed the theme, and it was my job to take his mockups and make them work. Lance was again leading the project, reviewing and committing fixes after the theme was initially introduced to Core .
We took a different approach for Twenty Fourteen, where we ported over an existing theme, Further , designed and developed by Takashi Irie . Lance’s role stayed the same, while Takashi took on a more active role in bringing in fixes, and I reverted back in a more supporting role like in Twenty Twelve.
When we look at how the five Twenty themes were created, we can roughly categorize them in two approaches, “start from scratch” or “use an existing