Aaron, thanks for the list of hooks that belong in themes. Now, I’m off to make sure these go into every theme I have, especially as I’m looking to make my themes as easy to upgrade as possible.

I’ve looked at Revolution, and it looks nice — but Thesis was the first “premium” theme I actually went out and bought, mostly because I love Chris’s respect for standards and his love of good typography. Plus, if I don’t use it for Filmgirl.tv, I can give it to Grant and he can re-do his site using Thesis instead of Cutline.

Chris has been a strong supporter of using custom.css
Ian advocates the use of child themes

The biggest advantage of Ian’s method seems to be that you can work with multiple design revisions from a single code base easily, or for example switch between designs using a different functions.php

I can’t think of any advantages of using custom.css over child themes.

Opinions?

Best of all, Brian has continued to improve and expand the Revolution themes, making everything available to existing Developer license holders – with so many good free themes out there, I was somewhat reluctant to dip my toe into the world of premium themes but the way in which Brian stands behind his product, and rewards his existing customers, continually impresses me.

Also makes it easier to upgrade

A WordPress user after my own heart. Thanks, Aaron.

* Logo – filter
* Custom CSS – filter
* Below the header – action
* Above the first post – action
* Between every post – action
* After the last post – action
* Above, below, between every sidebar element – action
* Separate footer hook at top of footer div – action
* Credit/Copyright in footer – filter

wp_head hook should be last line before

. wp_footer should be the last line before

That gives plugin authors extreme ability to modify themes via plugins and not hacking the code of the theme. Also makes it easier to upgrade.