Two simple things I wish from anyone attempting to create a "CSS framework": - Don't use class-based styling - Don't use CSS. All I'd want from a "framework"

Two simple things I wish from anyone attempting to create a "CSS framework": - Don't use class-based styling - Don't use CSS. All I'd want from a "framework" is to give a consistent set of SASS mixins, and I want to have one single sass file that generates all the CSS I need in one single place. It's not just for the purism of "separation of design and content", but also to make changes easier across a whole site. I started doing something like that with https://gitlab.com/mushroomlabs/zenstyles https://gitlab.com/mushroomlabs/zenstyles, but only out of necessity for my work on Hub20, I still think that if more designers started taking this approach, there could be a substantial increase in the quality of the "theme templates" offerings. Pair it with something like https://headlessui.dev https://headlessui.dev and application developers could take a basic spreadsheet to focus on functionality at first, and then you easily switch between whatever "sass theme" you wanted without having to touch any of the code.