* Create something different than the year before
* Show off the latest and greatest features
* Support child themes and encourage customization
* Have an aesthetically pleasing design
* work for a blog or a website
* Represent best coding practices, technical excellence

* HTML5 comment markup
* HTML5 input types for comment form and search form
* Provide context for translation in search form and comments heading
* Twenty Thirteen to be designed with accessibility as a priority
* Video Headers

* Navbar widget area
– this may be released as a plugin, “for responsible users”
– this feature hurt Konstantine the most, he really liked this feature
* Many small details
– Only the Title in the floating static top bar
– Right aligned image feature, will only be left-aligned to fit the rest of the theme
* Alternate header images
– Konstantine will make sure this feature gets into the plugin
* Features that were dropped:
* Custom Backgrounds
* Dotted widget background in the sidebar
* Video Headers
* Multiple color schemes

This time around, we are releasing Twenty Thirteen earlier in the year so it can be used through the year. In Twenty Twelve, this didn’t happen and it made it into WordPress 3.5 so it wasn’t available very long.

Konstantine: “Twenty Twelve was much more of a ‘mobile-first’ approach, but Twenty Thirteen was not. But the theme will still work with all the screen sizes. The approach was different, but the result is similar.”

“Media queries in Twenty Thirteen, we designed them work for smaller screens, not starting with smaller screens and make them work for larger.”