WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

#16436 closed enhancement (duplicate)

Use <article> in theme markup

Reported by: Malcjohn Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Themes Keywords:
Focuses: Cc:

Change History (13)

comment:1 ericmann3 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Markup of pages sent to the front-end is a theme issue, not a core issue. The same goes for the child elements of <article>.

comment:2 scribu3 years ago

  • Component changed from Post Types to Themes
  • Keywords 3.2 removed
  • Resolution invalid deleted
  • Status changed from closed to reopened
  • Summary changed from [HTML5] use <article> in the post. to Use <article> in theme markup
  • Type changed from feature request to enhancement

Yes, but we bundle the Twentyten theme with Core.

comment:3 follow-up: Malcjohn3 years ago

Hi,
i thought it should be made in the core. It has nothing to do with a theme. Doesn't matter what theme is istalled, because you are sending the post from the editor (Ty..) and it shows on the theme.

BTW sorry for my poor English.

comment:4 in reply to: ↑ 3 andrewryno3 years ago

It's still a theme issue because the themes only take the content and wrap it in whatever HTML the theme developer wants. However since twentyten is pushed with core, it can probably be changed with that theme.

If we are changing to use <article> in twentyten, would it make sense to just implement <header>, <section>, etc. as well? I would vote for sticking as is since IE doesn't support all of the new elements well enough for the change.

comment:5 solarissmoke3 years ago

Javascript DOM manipulation in IE<8 is a disaster when you use these new HTML5 elements - basic things like innerHTML calls and getElementsByTagName don't work properly because it doesn't recognise the new elements as valid - and for that reason I don't think core is ready for these new elements.

Suggest wontfix/maybelater - at least until IE loses majority market share ;)

comment:6 ericmann3 years ago

Replying to 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.

comment:7 Malcjohn3 years ago

  • Keywords 3.2 twentyten added

OK, thanks for feetback. set for the future release of twentyten.

comment:8 nacin3 years ago

  • Keywords 3.2 twentyten removed
  • Milestone Awaiting Review deleted
  • Resolution set to maybelater
  • Status changed from reopened to closed

Going to close as maybelater, as Twenty Eleven will be HTML5. Don't need this ticket to remind the initial developers :-)

comment:9 Malcjohn3 years ago

  • Keywords reporter-feedback added
  • Resolution maybelater deleted
  • Status changed from closed to reopened

This article from yeasterday is great. Below is a link to download it. Maybe we should use it as our standart theme, which we can use instead of ours.

Links:
http://www.smashingmagazine.com/2011/02/22/using-html5-to-transform-wordpress-twentyten-theme/
http://www.twentytenfive.com/

comment:10 nacin3 years ago

Indeed, nice article. My original point stands: Twenty Eleven will be HTML5.

comment:11 nacin3 years ago

  • Resolution set to maybelater
  • Status changed from reopened to closed

comment:12 ocean903 years ago

  • Keywords reporter-feedback removed
  • Resolution maybelater deleted
  • Status changed from closed to reopened

comment:13 ocean903 years ago

  • Resolution set to duplicate
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.