Agreed on sentiments, critical discussion is important. The navigation uses anchor tags, these are identified by 'id' and not 'name', therefore not HTML5. This

Agreed on sentiments, critical discussion is important. The navigation uses anchor tags, these are identified by 'id' and not 'name', therefore not HTML5. This only works because some browsers are generous like that. The document is not complicated, there are H1 tags followed by lots of p tags in sections. There is no reason to use classes to style this content or to use a stylesheet that is 96% unused. There is also no need for a huge amount of normalise.css if you are not using forms or anything else 'tricky'. The content unstyled is still readable on some lame Internet Explorer browser, so normalise is not needed. Stuff can look different. That is allowed. For visual hierarchy those h1 tags could be h2 after the document title/heading. CSS grid would work nicely to get the white space right with a handful of lines of CSS. Such a trimmed stylesheet for this document could fit on a screen and could therefore be inlined, not externally loaded and made 20 times bigger than it should be. Actually if you look at the document outline it is all over the place. Things get nested deeper and deeper. The structure should look better than that but it gets thrown off by things like the advert in the middle making subsequent sections sub-sections of the advert according to the outline. A <nav> tag around the TOC would help with the document outline. The address tag should also be used for attribution at the bottom and the figure tag should be used for images if accessibility matters, coupled with picture and srcsets if you can magically generate them. A couple of points regarding the content of the article: I question the insistence on 'ask a designer' as I don't believe the best designers always call themselves 'designers'. Any 'ask a designer' comment is best qualified, e.g. 'ask an experienced user experience designer'. The premise of 'design for a small screen first' is a conversation that needs to be re-framed as 'design for all devices, all input methods and all orientations' rather than this wireframe for mobile and that wireframe for desktop approach. Responsive Web Design was a great idea five years ago but the game has moved on. Fluid typography, custom properties and other new HTML5 things such as CSS Grid can't be mocked up with Sketch or Adobe products. The design tools are stuck a generation behind what can be achieved, as are those that only know how to use said tools. It is fine to have that content as unordered lists and lots of sections whilst you are working on your document structure. It is no good thinking 'burger menu first'. It is as silly to working on a car engine and confining yourself to working in just the engine bay and not on the workbench guided by someone's drawing of what the car with the bonnet/hood closed looks like.