search

mezzoblue / csszengarden.com

The source of csszengarden.com
Other
1.88k stars 587 forks source link

Fix the markup #1

Closed mezzoblue closed 11 years ago

mezzoblue commented 11 years ago

I've taken a first pass at converting the previous XHTML over to HTML5, but there's so much more that can be done here.

Semantics can be improved. Redundant spans will go away. ARIA hooks can be added. It's all up for discussion.

GaryJones commented 11 years ago

One thing that would be worth reading is http://www.w3.org/TR/html-polyglot/ which outlines how to make the code into a polyglot document - one that can be read by HTML and XML parsers (i.e. can be served as HTML5 or the XHTML variant of HTML5). Since the markup is going to be controlled (rather than having user-added content), then it's perfect for something like this.

That would mean keeping in the otherwise optional closing slashes on empty elements (reverting #11).

GeorgeZamfir commented 11 years ago

:+1:

I'll definitely take a stab at ARIA & semantics.

p.s. for now I'm still getting up to speed Git / GitHub :)

GaryJones commented 11 years ago

Some of the elements have IDs. Could equivalently named classes be added as well? (The IDs would obviously be needed for BC with existing submissions.) The use of classes (as per OOCSS, and SMACSS) would simplify the specificity calculations too.

mezzoblue commented 11 years ago

Initial push of classed elements went up tonight. A bunch of multi-file find and replace allowed me to convert the existing designs over to use them, then provide alternate IDs for the sake of in-page linking.

Have a look and let me know what you think.

mezzoblue commented 11 years ago

Closing in favour of newly-opened issues that break these down by topic.