Frontend Architecture for Design Systems: A Modern Blueprint for Scalable and Sustainable Websites 1st Edition

Frontend Architecture for Design Systems: A Modern Blueprint for Scalable and Sustainable Websites is a top-notch O'Reilly book. The author, Micah Godbolt, does a great job covering a somewhat complex topic surrounding the 3 primary CSS design methodologies: OOCSS, SMACSS, and BEM. He covers each method in detail with a wide-array of graphic illustrations and screenshot examples but does spend majority of the book on his own blend of SMACSS and BEM, which as a front-end dev myself, found very applicable for my work with PHP-based CMS solutions. Regardless of what front-end framework you deal with, this book will spark all kinds of new ideas and help you expand your own reach with CSS.

This is a solid read for someone needing to make sense of the "Why" of the current CSS landscape. For those experts who've already been doing this, it provides a solid summary without being too annoying.Not a fan of the writing style. In fact, I feel that this editor failed their author. I'm not sure who's at fault for the divisive rants, needless paragraphs and all-around immaturity. Although this might be a marketing strategy to get at front-end developers who don't have broad industry experience.The first half of this book is really close our CSS interview. The second half is how Red Hat derived their own Pattern Lab. And for all the talk of JSON Schema, I feel that this book didn't do enough to demonstrate the connection of JSON that ran through the view templates back through to the APIs. A larger architecture diagram of the final version might have helped here.

Making a web site is easy. But for a truly great site, one that is accessible, scalable, and maintainable, your team needs a clear strategy and common project language. This book is where you start. Micah not only covers the fundamentals of site architecture, but with examples and case studies, this book gives great strategies that any team can start using.

For folks with extensive software development experience, most of the content will seem common sense/knowledge. Even so, they may find interesting new bits in the book. I found two bits to be interesting: 1) the list of automation tools mentioned in the book and 2) explicit exposition about how common software engineering best practices are applied to front-end development.My biggest qualm with the book was the term "front-end architecture" used in the book was a misnomer as architect/architecture was defined/described in relation to the process and tooling used to build a system and not the overall structure and organization of the system/building (traditional notion of architecture). I thought the book was dealing with software engineering best practices being applied to front-end development.

In the last year I have been building a development system for web UI. I was fortunate enough to meet the author at CSS Dev conf. This books is a great view into building something like architecture for consistent UI. I really enjoyed it!

I gave it to my friend who is a programmer and enjoyed it.

The best part of the book is when he write about being a front end architect, that part is interesting.But all related to a design system feels old in this times, I’m a design system advocate, and lead a design system team, and there is no useful information about it in this book. Many concepts are explained in a very high level, but in some parts there are css code, or html, or npm commands that feels disconnected and useless.Sorry by being tough, but it was a waste of money.

The book isn't very informative