When a theme author adds Jetpack Infinite Scroll support to their theme, they configure its options specifically for that theme. Occasionally you might want to override the theme’s defaults for your purposes, and in this article, I’ll show you how to do so in a child theme.
There was an interesting bug reported for Twenty Twelve recently: The
.single-attachment body class only gets applied when the attachment’s parent is a post (or custom post type). If the attachment’s parent happens to be a page, that class is missing.
In case you have been using
.single-attachment to specify styles for the image attachment page, make sure to test your theme with images that have a page as a parent. And use the
.attachment body class in the future. ;)
Chip Bennett, Team Rep and Administrator of the WordPress Theme Review Team, wrote a comprehensive post about the intricacy around home page and front page templates. Highlights are his tips around conditionals in
front-page.php to avoid code duplication. Enjoy!
_s, I came across an issue asking if we could remove the loop syntax in singular templates since there is never more than one post. I asked for Michael Field‘s opinion on the matter and he pointed me to a core ticket for Twenty Eleven about the same issue. Continue reading
I had the chance to speak at WordCamp San Francisco this year and, this time, I tried to do something different. Instead of doing a talk with lots of code examples and howto info that could be read in a blog post I decided to put my heart on my sleeve and shoot for inspiration. Of course, I still talked about WordPress themes. No one wants to hear a rousing talk from me on how much I love cooking at home. I tried with this talk to share why I love working with WordPress themes. Because I really do. I got the impression that people liked the talk. Maybe you will too. Check out (What’s So Funny ‘Bout) Themes, Love, and Understanding on WordPress.tv. Or just watch it here on ThemeShaper!
P.S. Someone remind me the next time I speak to not wear a shirt that gets wrinkled so easily. :)
Photo adapted from a banksy shot by Thomas Hawk.
I’m excited to share that we’re pushing things forward in WordPress 3.6 – default snippets for comments, the comment form, and the search form are updated with the latest HTML5 markup.
While the changes to both the search form and the comment form are rather marginal (added classes and some streamlined markup), the comment markup changed a bit more. The new version offers the best features from previous default themes and the pre-existing markup from core.
At Automattic, we exclusively use the Customizer for theme options instead of theme option pages. We believe that themes should only alter the display of content and should not add any additional functionality that would be better suited for a plugin. Since all options are presentation centered, they should all be controllable by the Customizer.
Review is a key part of Theme Wrangling, so we spend a lot of time looking “under the hood” at themes. Here are some of most common theme development errors that come up in the review process, and some tips on how to avoid them.
Looking for a better way to manage featured posts from theme to theme? Kirk Wight has a great post explaining how to use Jetpack Featured Content in your theme.
They say Valentine’s Day is all about love. Well, the thing I love the most about working on the Theme Team at Automattic is the attention to detail that goes into each theme launch. There is an inital build process followed by a series of peer reviews. More times than not a theme will be put under the microscope of 2, 3, or sometimes 4 different team members before launch. The sheer number of things that can potentially go awry in a theme can be overwhelming at times. This review process allows us to catch as many bugs as possible before people start using our themes.
Our peer reviews focus on a mixture of three areas: code quality, usability, and discovery of theme-specific anomalies. Over the years, our review process has grown organically. When we discover a new issue we will generally post about it to an internal P2-powered website for team discussion. While this process works really well, it can be a bit time-consuming to navigate through three years’ worth of posts to find an isolated conversation about a particular issue.
Recently, we thought it was a good idea to collect all of our theme guidelines and create an easy-to-follow resource. Instead of posting this internally, we decided that we would like to share our guidelines with theme developers everywhere. I would like to present to you the first installment of The WordPress.com Public Theme Guide. We hope that you get as much use out of this as we do!