This article would likely be more meaninful and useful if it had 1:1 comparison of a completed component or two.

But of course, that would IMMEDIATELY illustrate why CSS frameworks are utter and total disasters of ignorance, incompetence, and ineptitude, pissing on usability, accessibility, and efficiency from so on-high you'd think the almighty just got back from a kegger.

Though honestly your entire "What is CSS and Why We Need It" section glosses completely past what CSS is, much less what it's for... but that's typical for framework apologists who never learn what HTML or CSS are for or why they are separate in the first place.

Hence your vanilla CSS section being filled with the same blind parroting of unfounded propaganda we always hear. Lies, Lies, and more bald faced lies.