Yeah, that makes sense. I think the value of this particular text is that it teaches some of the underlying architectural principles, but truthfully, you probably won't be making those sorts of decisions until later in your career (unless you end up working at a really small shop).

For now, just focusing on the basics of HTML/CSS and especially JS will get you going well enough, and those will all be applicable in web work no matter what specialization you choose.

Those are what we normally consider frontend technologies (though JS can also be used on the backend). If you also want to learn the backend side, having some frontend knowledge still never hurts, if only so you can work with the frontend people better.

This text might be worth circling back to later in your career, once you start considering architectural patterns. But for now you have a lot of other great suggestions :)