Yeah, it's a little weird and out of place. I thought it was a page about PWA Fundamentals.

You'd figure they would start off with an opening statement of what "Web Fundamentals" means exactly, instead of some random feature.

We are constantly updating the site (it's been live for two years now), and that was one of the newest areas that has come through.

We manage all of this on github (https://github.com/Google/WebFundamentals) and love getting feedback on what we need to improve!

"Fundamentals" does not mean "the newest thing that has come through". It means almost the opposite.

It's your site, but if I meant fundamentals, I would call it fundamentals and start with fundamentals: HTML and CSS. If I meant building on the fundamentals, I would write about the standard uses of JavaScript to bring HTML and CSS to life. If I meant "newest things", I would call it a blog and talk about the newest things: recently implemented and incompletely supported APIs, such as notifications. Some of the newest things are very interesting as what they are: new things.

Maybe I'm missing something, but I don't see any reason to label a site "web fundamentals" and lead with something that has never been fundamental to the Web unless the agenda of "web fundamentals" is something other than teaching web fundamentals.

It's a good point. We chose to aim this at already practicing web developers and show them the best practice. There are already great HTML, CSS and JS resources over on MDN and we had no intention of competing with them.

The home page needs some work, clearly and we can sort that.

In addition to that, the Home section shows new content. We try to cover everything – from the basics to new APIs on Web Fundamentals.

But yes, we should sort this to make it clearer

I'm surprised Web "fundamentals" doesn't begin with HTML.

Knowing how to write HTML in 2016 is so passé, everything is abstracted on so many levels that nobody actually knows how to make a website.