[badsectoracula]

Well, here is the thing though: you don't need most of that rendering stuff to learn how to make a game engine - if anything it might actually be better to not focus too much on the rendering as there are many people with the misconception that a game engine is really all about its renderer when in most engines it only is a small fraction of it (i remember checking my own engine some time ago and only around 10-15% of the codebase was about the rendering, i mentioned it to some Godot developer who said that this number checked with Godot too and years ago a AAA game i worked on also had the rendering bits be around 7-10% of the codebase too, so i think on average the percentage is more or less stable) and there are a lot more things going on.

The content on the site seems to also follow, even quickly browsing from the materials there and despite using Vulkan (which is much more verbose than necessary), it still only mentions basic things like rendering sprites, meshes, some scene representation and leaves lighting and shadows (which only get a couple of paragraphs to describe the ideas behind shadow mapping) at the very end (up to that point everything is unlit/fullbright). Even lighting is only described at its basics and the page mentions some external resources to learn more if anyone wants to.