Covers many aspects of functional programming that a software architect has to know working with Javascript (as both functional and object paradigm elements present in JS).
2) Clean Architecture by Robert C. Martin - quite a popular book, so you perhaps already heard about it.
I'm a strong advocate of this style, but keep in mind it is has a relatively high threshold for both developers experience and the domain complexity, so don't apply blindly everywhere (like I once tried :sigh)
3.1) There's also a few materials from Martin Fowler (author of "Patterns of Enterprise Application Architecture") about DDD: martinfowler.com/tags/domain%20…
4) Khalil Stemmler's blog - not a book, yes, but there r many valuable articles on the architecture subject.
5) "Patterns For JavaScript Frontend Applications" on Cloudboost: blog.cloudboost.io/the-state-of-w…
"Unidirectional user interface architectures" by André Staltz: staltz.com/unidirectional…
Again, not books, but articles covering important aspects of architecture from frontend perspective.
6) Refactoring Guru - it is the greatest project I've seen so far about Design Patterns (except for @martinfowler's publications).
Refactoring Guru contains quite sufficient explanations for the popular patterns with examples in different programming languages - those sometimes require a bit of thinking on how to apply them in your codebase, but nevertheless, the project is worth investing your time into.
Suggestions on the frontend developer portfolio and projects there:
1. Add a link to your Github profile somewhere on the page, so it is visible. I usually quickly skim over portfolios and want to have a look at that to see some general activity on Github (comments, PRs, etc)
Even though HRs may not care, developers are actually quite interested in that one to see whether how long your were coding, how do you communicate, have you tried working in collaboration on something, and so on.
2. I recommend you adding links to project repositories. This one rising straight from the previous point. I usually just take a quick look at the deployed version of one or two of the most recent projects in the portfolio and it is enough to understand what those are about.
There's nothing that prevents you from starting learning NodeJS after you got slightly proficient with HTML, CSS, and basic Javascript.
Especially if you feel like you are really interested in cross-functional development when you may be involved in really diverse tasks - I strongly like it myself as it allows me to work with various technologies and solve diverse development challenges.
At the same time, thinking about the beginning of a web development career, I would still consider the thought that you need to have a primary skill that distinguishes you from the other developers.