I am thinking taking PHPDoc as foundation (it's already written and there is plenty of it), build pages for functions (like Codex pages for individual functions) and then add a layer of organizations - build calling hierarchies of functions, families of functions related to specific functionality... this is something Codex could have but won't because it's work and owners don't give a damn to have this :)
after automated stuff is done can think about taking user-submitted content, like PHP takes highly curated comments
Not shure if this will work - it may be that the conditionals are not working at this point...
// inside functions.php
function wpse47861_intercept_main_query( $wp )
{
// default
$nr_posts = 10;
if ( is_category( 'CAT NAME' ) )
$nr_posts = 4;
if ( is_category( array( 9...
@StephenHarris I wanted to work on my blog theme a little bit today, but found myself lost in continuous improvements. Therefore I thought "let's search for a free theme - again". Now I found some, which are not too crappy, but still have some solid drawbacks. Therefore I wanted to write a Q about "Where to look at a theme when I want to use it for my site". Point is that I think this will get some attention and I need a well spelled english title for that. Could you lend a helping hand?
@StephenHarris No, it's more like "How to judge a theme" or "At what files in a theme shall I look first" or "What is a no-go for a theme that I want to use". Something in the line of that.
@kaiser That's a difficult Q to answer - it could depend on what you wanted the theme for. Maybe, 'Best Practices for Theme Development'... might be a bit too wide.
@toscho It is a little bit about the title, because it implies the possible answers. But, ok. I give up. Just wanted a counter part to all this "this is great" answers, that people love so much.