Code Examples: Validate HTML and CSS

[ZoeBijl]

As Karl pointed out, all code examples should be validated.

• Button
• Alert
• Checkbox 1
• Checkbox 3
• Link
• Radio
• Slider 1
• Slider 2

For those wondering: I've removed all role="main" attributes. These trigger a warning in the validator. Besides, the main element should suffice; there are no other structural landmarks.

[karlgroves]

As this tends to relate to other issues, such as #88, #131, and #95, it might make sense to introduce at least one important dependency: Grunt. You can add some sensible Grunt tasks to handle some of this stuff. LMK if the WG would like some help here.

[ZoeBijl]

I think we better start with the simple addition of an .editorconfig file and go from there. We need to see how that impacts the people working on this. To be honest, I'm not sure about adding dependencies on this. (I feel) this is stuff is not all that complicated. On the other hand, automated HTML validation and the like would be a plus.

[ZoeBijl]

I have validated all examples (the code still needs cleaning up, but that is a different issue): fadbd7f

@karlgroves I'll let you know if we're going forward with adding something like grunt/gulp/npm scripts.

[karlgroves]

Definitely agree with starting small, but IMO you could/ should auto beautify to enforce your coding standards and require that all PRs pass the validity checks.

[ZoeBijl]

I agree, have filed an issue: #202