Open Jamiewarb opened 1 month ago
This approach sounds promising. It might be worth considering a tailored tailwind.config.js
to promote consistency across the starter, rather than relying on Tailwind’s full defaults. For instance, reducing the 26 sizing options down to just 6 might simplify design decisions.
Users can always revert to the full suite, but this approach encourages more thoughtful section design and theming right from the start.
Yeah for sure. I'd probably remove most of the default configuration.
Lots of CSS methodologies and libraries.
My gut feel is a mix of Tailwind for layout utilities, and CSS Modules for main styling.
CSS Modules are nice, neat, co-located, and route split.
Tailwind utilities are great for quick, one-off layouts, like flex, margin, and padding, where there is no real semantic meaning.
What other approaches might work in a similar way, and are widespread enough that they will be useful to a wide audience?