It's a straitjacket to reduce inconsistency across different sections of a large app/family of apps - and which help a bit with finding common styles for refactoring.
It's not so much about what you do as a single designer on the initial design, more about what a team of designers do when adding new apos/modules to an existing product.
In theory you could use bootstrap and a theme - but your fellow team members will get lost, re-invent some styles etc.
I'm inclined to solve this problem with discipline and corporal punishment - but I'm afraid the tailwind-people are on to something.
Basically the cascading part of css does not work well for applications / a suite of applications - it works better for actual hypertext documents (like sgml might) - where you can make a layout that works, while the browser handles the user experience (UX). When layout/design becomes "just" part of how an app looks, but the important is how it beheaves (including things like hover, expanding menus etc) - bare CSS doesn't work as well. Not technically, but from a perspective of an evolving code base.
It's not so much about what you do as a single designer on the initial design, more about what a team of designers do when adding new apos/modules to an existing product.
In theory you could use bootstrap and a theme - but your fellow team members will get lost, re-invent some styles etc.
I'm inclined to solve this problem with discipline and corporal punishment - but I'm afraid the tailwind-people are on to something.
Basically the cascading part of css does not work well for applications / a suite of applications - it works better for actual hypertext documents (like sgml might) - where you can make a layout that works, while the browser handles the user experience (UX). When layout/design becomes "just" part of how an app looks, but the important is how it beheaves (including things like hover, expanding menus etc) - bare CSS doesn't work as well. Not technically, but from a perspective of an evolving code base.