amp.dev VS content

Here's one: https://amp.dev/documentation/examples/components/amp-analyt..., backed by https://github.com/ampproject/amp.dev/blob/future/examples/s...

Shay's website is a great resource. It's a little outdated but has valuable information. You could also look into MDN's website, which is actually THE best resource for web development.

Yeah, non-trivial CSS can be problematic (I'm full-stack dev but do not have to touch CSS that much), I find https://developer.mozilla.org and https://caniuse.com usefull to learn more about different topics (CSS+javascript).

Don't tell me he's a victim of the regime, when other library authors add banners about the war in Ukraine he does not like it https://github.com/medikoo/es5-ext/issues/116 https://github.com/mdn/content/pull/18946 and like the comments about Poland becoming “Russia Poland People's Republic” doesn't look like a victim https://github.com/medikoo/es5-ext/issues/116#issuecomment-1066989820 https://monosnap.com/file/zZl6PrsxPTCtI0qx9XH6AZSb19eX6t and like comments about “Ukraine hit Donetsk with Tochka-U” https://github.com/medikoo/es5-ext/issues/116#issuecomment-1068768522 https://monosnap.com/file/bczy9oIIMSKz48P6K4MlkttrJ5jo5C

For learning, I'd suggest you cut the middleman as much as you can here and go straight to authoritative sources instead. For web development stuff, I always go back to the Mozilla Developer Network (https://developer.mozilla.org) In particular, I rely on https://mdn.io/ to get me to what I want quickly.

Browser compatibility matrix: You can check the browser compatibility matrix for the latest JavaScript features on websites like caniuse.com or the MDN web docs

Get very familiar with the MDN and when you run into specific issues Google is your best friend. I’ve been learning Web Dev for an entire year now and knowing what to ask if important. Be specific in your searches. There are so many tutorials and teachers out there. You can PM me if you want

Mozilla Developer Network (MDN)

I have found that when you start working on just a single project, it will naturally lead to other opportunities (e.g. upstream libraries, similar projects, etc). When I started working on MarkBind, a static site generator, I was also making occasional contributions to some of the plugins for markdown-it, the Markdown parser that MarkBind uses. I was fixing bugs in MarkBind by discovering the root causes in the upstream libraries and pushing fixes there to hopefully benefit other projects as well. I even made a pull request to fix the documentation that I was reading on an MDN page for : The Table Body element, something that broke the server-side rendering of MarkBind.