This is about the level of detail a lot of online guides/tutorials have for most of these packages/workflows/tools/watchamacallitnow. The next step is to read through the documentation, which is often verbose, not pedagogically structured, and sometimes non-existent. The method of last resort is to attack the source code: akin to reading someone's notebook written in a foreign language. You have to get used to their style and shorthand.
"Remember, we're just manipulating text" is what I repeat to keep me sane when troubleshooting tooling issues. It's a big time investment to understand the full-stack; a bigger one to keep on top of it. This issue will only grow exponentially as more code is written and more individuals become developers.
If anybody is interested in learning web development, Full Stack Python is a great resource that places lots of different web technologies in proper context, it helped me a lot in the past. I can also recommend Mozilla's Documentation Pages for HTML/CSS/Javascript as it relates to webpages, although the quality can be inconsistent.
(If you want an example of atrocious documentation, check out the Galago Search Engine/Lemur Project. It's so opaque a research paper dedicated a section to how hard it is for phd's to understand the source code)