Simplify markup house style page about frontend-playbook HOT 5 OPEN

Oh, i forgot the outline section was on that page. That is interesting because i'm in the middle of the new a11y checklist and I was also thinking about how to include stuff about the outline algorithm there. This markup doc is super old, I think it might have come from a page in the old Nature wiki? It's about time for a refresh.

As i said, I wanted to put something about the outline in the refreshed a11y checklist. I don't want to have a huge amount of content on the checklist itself. I do want to link off to other bits of the playbook from the checklist. IMO we should keep the outline stuff here (as a deep dive), link to it from the a11y checklist, and make the whole page less scary 👻

(edit: omg it's not old at all and it's not from the old nature wiki!)

from frontend-playbook.

I would have thought we have now standardised on HTML 5 across various sites and products.

XHTML may still be used on some legacy pages, but HTML 5 has been the defacto standard for web development for a while now. So yes as you say it just adds to the confusion.

from frontend-playbook.

As HTML5 can still be written in a XML syntax & serialisation, and some people assume XML is desirable because it is more strict (not an unreasonable assumption), I'm keen to retain the reasoning to avoid anything XML being considered.

However I'd be happy to see any proposal reorganising or rewriting this doc, to make it less intimidating for those unprepared for the @jpw XML rant 😛

Considering this is directly related to accessibility and assistive technologies, should this section be included with the rest of the accessibility stuff (and adding links where necessary), instead of here?

Yes, but this is the markup house style page and I think should best live here? Maybe more cross-linking as you suggest?

from frontend-playbook.

from frontend-playbook.

interpret out instructions typo

from frontend-playbook.