If you’re interested in learning more about how to use get_template_part() in your themes and why you might want to, designer and developer, Terry Sutton, has a great post up called Tighter and leaner WordPress templates with get_template_part(). It’s well worth a read. (And not just because he mentions _s though that’s pretty cool too.)
There are a couple of spots that I always keep handy when looking for information about WordPress’ query handling. Consider this Gist an addition to my list:
Fun fact of the day: about 37% of WordPress downloads are for non-English, localized versions.
So as a plugin or theme author, you should be thinking of localization and internationalization (L10N and I18N) as pretty much a fact of life by this point.
An excellent post from Otto on improvements to make and pitfalls to look out for when performing i18n on your WordPress theme.
There are some simple instructions in the theme
readme.txt on how to get started with our new starter theme, _s, but, to be honest, I’m not exactly the most reliable readme reader myself so here are those instructions with a bit more explanation. :)
The first thing you want to do is copy the
_s directory and change the name to something else. Like, say, megatherium.
Then you’ll need to do a three-step find and replace with your favorite text editor on the _s name in all the templates.
My coworkers at Automattic and I frequently discuss the speed with which we’re able to onboard new themes into the WordPress.com theme directory.
Our top priority as the Theme Team is to make sure that all of our users feel like they have a theme that fits them perfectly; in order to meet that goal we’re focused on bringing a variety of themes into WordPress.com through a few primary channels: the WordPress.org theme directory; premium theme shops; and Automattic (in-house) themes.
It’s often the case that each conversion—that is, making a theme’s code WordPress.com-safe and ready—will take us anywhere between one week and one month, depending on the complexity and quality of the code. In a perfect world, though, we’d be able to snap our fingers and have every single awesome-looking theme available on WP.com right now.
If you haven’t yet you should make some time to read Building Twitter Bootstrap at A List Apart. Especially if you’re interested in building a WordPress Theme Framework or WordPress Starter Theme.
I think it’s safe to say that I’m somewhat obsessed with themes that help you get your WordPress projects started quickly. Most likely because I’ve been there, staring at an empty project folder wondering where I should begin. Well, you shouldn’t have to stare at that empty folder for any project. Even when you’re starting from scratch you’re probably not really starting from scratch, right? You’re taking an existing WordPress theme, either your own or someone elses, and hacking at it until it’s something new. That theme is your Starter Theme.
But not all Starter Themes are created equal. If you’re using the same theme again and again and always adding the same code to it, well, shouldn’t that code always be in there in the first place? Or how about the reverse? If you’re always cleaning out the same code from your theme is that really a great starter theme? Should it have sample theme options? Or a CSS reset? Basic styles? How much style? A grid system? … The questions could go on for a while.
So, what are you using for your Starter Theme? And what do you think you really need in a WordPress Starter Theme?
Konstantin Kovshenin has a great post on one of my pet peeves. The lock-in effect. The rub? When you go to switch themes you find that your content is tied into the theme (or plugin) you’ve been using. Not good.
WordPress has been known for its backwards compatibility for ages. In fact, you’ll not loose your content when you downgrade (provided that you’re using the core features only,) plus WordPress provides several export options that can easily be read by other software and services. WordPress gives you control over your data so you’re never locked in to using WordPress itself. WordPress does not lock you in.
Plugins and themes are somewhat different though, mainly because developers are overlooking the WordPress API and a bunch of features which already ship with WordPress, and tend to reinvent the wheel. Another situation is where plugins or themes introduce some brand new features unavailable in WordPress so they store your data in a unique way which is not what other themes and plugins can understand. If not treated well, the lock in effect can cause loss or corruption of your data …
I recently started subscribing to RSS feeds again after having given them up totally for several months. I was relying on the cream to rise to the top in Twitter and a handful of sites that I would visit every day or week. And now, after declaring feed bankruptcy, I’m back at it again (switching to Reeder as my feed reader was a big part of that decision). I have pared things down though. Here’s my must-follow short list of WordPress and Web Design sources that I’m following right now. These sources let me keep on top of what’s going on in WordPress and Web Design.