Semantics - where next? about csszengarden.com HOT 13 CLOSED

Having two HTML's isn't biggest frustration as you could make it an attribute of the submission. Such as layout=1 or 2.

from csszengarden.com.

I don't think that'll be necessary, I've had a lot of luck with global find & replace -- all the designs currently in the repo (and the rest that aren't) have been converted to work with the current HTML5 version, including all the class/id changes. Should be possible to continue making changes and keep them in line.

from csszengarden.com.

We should also use the new "main" element, also, it may help our DIVs problem. Some questions answered about it:
http://www.w3.org/html/wg/drafts/html/master/grouping-content.html#the-main-element
http://stackoverflow.com/questions/13949009/when-can-i-safely-use-the-new-main-element-in-html5
http://filamentgroup.com/lab/the_main_element/

If you're thinking of having more / all H1s I'd say no at this point. There's still way too much confusion about the HTML5 outline algorithm:
http://html5doctor.com/outlines/
http://coding.smashingmagazine.com/2011/08/16/html5-and-the-document-outlining-algorithm/
http://www.456bereastreet.com/archive/201104/html5_document_outline_revisited/

from csszengarden.com.

I know you are trying to preserve the past themes, however I would like to think that a better teaching aid would mean getting rid of the old messy code that is no longer relevant and building it up the correct way using proper HTML5 markup.

from csszengarden.com.

@markaplet thanks for your input, but did you have any actual suggestions on how to achieve that and keep backwards compatibility? Examples of what proper semantics should look like, perhaps?

from csszengarden.com.

@mezzoblue No, I dont have any specific suggestions outside of perhaps using JS. But I know that has it's own challenges. My comment was more of an encouragement to ditch the old markup in favor of all new markup. The old themes can still use the old HTML, but they would essentially be two separate files.

Sorry it's not the answer your looking for. But like IE6 sometimes we have to let go of the past in order to make a better future.

from csszengarden.com.

@markaplet have you actually looked at the markup as it exists, on the site today? Have you seen issue #13? Aside from the work I've already done and that one issue, I'm not sure what else you're advocating here.

from csszengarden.com.

@mezzoblue Sorry Dave I can see why you were getting pissy with me. Yes I did look at the code, but obviously not that good. I think I just zeroed in on all the spans and id's. Excuse me while shrink back to the hole from whence I came.

from csszengarden.com.

What about microformats? This is google-centric, but their thoughts on microformats extend HTML's default semantics to cover microobjects such as People, Addresses, etc.

Beyond that, if this is supposed to be an educational/best practices exercise, should the HTML be extended to add in examples of the full list of available tags? Especially now that the web is becoming more and more media heavy, there's a distinct lack of videos, images, etc. that present new stylistic opportunities.

Even HTML elements that have been in the spec/supported for a long time, are conspicuously missing:

• dl/dt/dd
• tables (with actual tabular data)
• form
• citations
• definitions

I think part of stretching people's imagination in use of CSS includes being able to style a multitude of types of information, more than just text-heavy or text-centric "pages".

from csszengarden.com.

Heh, same argument people have been making since almost the very beginning: it doesn't represent a wide enough amount of the tags/content types/data we work with day to day.

I really don't want to turn this thing into a full on style guide. Let's keep in mind it's also intended to be a playground. If we make it look too much like work, it's not going to be much fun to submit a design.

from csszengarden.com.

No to microformats, but yes to microdata (if anything is applicable) for anything HTML5.

from csszengarden.com.

FYI, .p1 through .p5 over-classing is now a thing of the past. Next on the hit list: spans.

from csszengarden.com.

Closing in favour of more specific semantic updates like #28

from csszengarden.com.