I'm all about this. When I made my personal webpage, this is how I do it. I'm surprised it's not more popular (at least for certain things) because it looks nice and clean, is fast, and crucially, is easy to put together. Most webpages don't need a ton of JS to "accomplish the mission." I get that not everything can do this, but there are soooooo many sites that can strip down to a more minimal site and have better functionality and a better experience. This is a case of less-is-more.

I don't agree with the problem they aim to solve with those goals.

But today it takes several years of mastering tools and frameworks to get to that stage. HTML First principles should allow people to unlock that feeling, and level of mastery, much earlier on in their coding journey.

The onboarding process can be made easier for devs new to the project (junior or senior) with decent documentation. Just enough install/build the project in their local machine and understand the gist of the technologies.

5. Rule - Prefer Naked HTML

HTML? Naked?? Man, I always did 😍.

deleted by creator

Where possible, maintain the right-click-view-source affordance. The beauty of the early web was that it was always possible to "peek behind the curtains".

Just make the source code availible behind a visible link (hosted on Github or another similiar platform if possible). I don't see this being a problem by any means.

As someone who was a web developer since the mid-2000's (and not more recently), an HTML first approach speaks to me. I am still of the belief that your contents should be in HTML and not pulled in via JavaScript.

The article is a bit self contradictory. It encourages specifying style and behavior inline and not using external styles and scripts but also discourages using a website build pipeline or dynamically generated HTML. So how can you maintain a consistent look and feel between pages? Copy and paste?