Feature/swap html5 elements

[middlesister]

No description provided.

[middlesister]

@emhr This is basically a complete port of my html5 plugin. The only thing not added is a str_replace on wp_page_menu to use the <nav> element. Do we want it?

Still not swapped are some loops that are directly in template files, namely 404.php, attachment.php, links.php,page.php, search.php, template-page-archives.php and template-page-fullwidth.php.

The Links page is getting deprecated (right?), but the others need to be addressed. The reason I didn't swap them yet is because I need to solve how to do the legacy mode. We could simply move these too into content-extensions.php, and treat them the same as the others.

Also missing are unit tests for the childtheme_override_* functions. I have to figure out how to test those.

Otherwise I think the html5 elements are there.

[middlesister]

Tests for childtheme overrides are now in a separate group and can be run using a command line parameter.

phpunit --group overrides

Legacy mode is also a separate group and is run with

phpunit --group legacy

And the rest is in group default

phpunit --group default

[middlesister]

A possible solution for the template files is to include them in the legacy folder and then swap them in via the template_redirect hook or template_include filter.

add_filter( 'template_include', thematic_legacy_templates' );

function thematic_legacy_templates( $template ) {

    if ( is_page( )  ) {
        $new_template = TEMPLATEPATH . '/library/legacy/page.php';
        if ( '' != $new_template ) {
            return $new_template ;
        }
    }

    return $template;
}

Of course with added checks if child theme has defined the files etc, but as a general principle. cc @emhr

[middlesister]

Something like this - http://wordpress.stackexchange.com/questions/50201/custom-taxonomy-in-plugin-and-template/50206#50206

[middlesister]

Legacy template files are now loaded in legacy mode. Merging this.