[wp-trac] [WordPress Trac] #16436: Use <article> in theme markup
WordPress Trac
wp-trac at lists.automattic.com
Wed Feb 2 05:20:15 UTC 2011
#16436: Use <article> in theme markup
-------------------------+------------------------------
Reporter: Malcjohn | Owner:
Type: enhancement | Status: reopened
Priority: normal | Milestone: Awaiting Review
Component: Themes | Version:
Severity: normal | Resolution:
Keywords: |
-------------------------+------------------------------
Comment (by ericmann):
Replying to [comment:4 andrewryno]:
> It's still a theme issue because the themes only take the content and
wrap it in whatever HTML the theme developer wants.
Exactly my point. If you want WordPress to put out HTML5, that's up to
the theme you're using. If you want it to render XHTML instead, that's
also up to the theme. It's a decision made not by core, but by the
designer/coder of your front-end.
> I would vote for sticking as is since IE doesn't support all of the new
elements well enough for the change.
The biggest advantage of using WordPress over other systems has always
been compatibility. As Matt said once at a WordCamp, you can take pretty
much any well-put-together theme from 2.0 and drop it on a 3.0 (or 3.1)
installation and it will still work. We don't break things for people
using older systems - for a bundled theme, we should take the same
approach.
While HTML5 is all shiny, new, and cool ... IE doesn't properly support
it, and IE is still the market leader. I'm a big proponent of "decisions,
not options" so while having the *option* to use HTML5 for TwentyTen would
be nice, I think we should keep things as-is and leave that specific
option available for a child theme.
And building a TwentyTen child theme that uses `<article>` and `<header>`
and `<footer>` isn't too difficult.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/16436#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list