Consistency fixes

[mikealmond]

The second commit is to make the index page consistent with the 404 page (#1016). It's a little controversial so I understand if there is a lot of push back.

And... discuss.

[tomByrer]

The line on one of your changes states "/* Black prints faster: h5bp.com/s */". Does that mean the using "black" is faster than "#000" perhaps due to parcing? I wonder how one can test this...

[barryvdh]

No, that line was already present before the commit. This is for consistency (always use a hex code)

[mikealmond]

@tomByrer Black also refers to #000, or rgb(0,0,0). What is happening is that when a document is printed, text that are certain shades of grey take longer to print in some browser. One of the comments in the article stated that there was no speed differences

I found the results to be the same regardless if I was using hex, rgb, or named keyword.

[tomByrer]

Thanks for the insight @mikealmond!

[necolas]

Why did you modify the margin on the chromeframe css?

I'm -1 on removing the closing tags from the main index file. I'd rather add them back to the 404

[mikealmond]

@necolas I felt the bar looked awkward with a margin on the top but none on the sides. I can revert it back if needed.

Part of the reason I removed the closing tags was because of a few PR's that were rejected putting them back in the 404. I'm pro removing tags that don't need to be there, while still making code legible. Basically for me, that's only the html, body and li's on short lists. I thought it would also spark some conversation. I'm good with any decision, I just want it to be consistent.

[foiseworth]

-1 for removing closing tags because we should be consistent and if we are being consistent we should also remove closing head tag.

+1 for adding quote and changing black to #000

[necolas]

All this and more should be addressed in #1112

[necolas]

Dealt with as part of 7a2f9dc