Tailwind gives you a bunch of utility classNames to write CSS with. I've been loving prototyping with it, and I'm interested in why, because it's ideas often feel counterintuitive.
Tailwind gives you a bunch of utility classNames to write CSS with. I've been loving prototyping with it, and I'm interested in why, because it's ideas often feel counterintuitive.
Something I think a lot about is what level of abstraction to attack a problem on. Here is a loose cataglog of where I've been thinking about it lately.
Previously I've been reluctant to use libraries in my react code, generally preferring to roll my own solutions, believing that you tend to hit a wall with what you can do with libraries and working around their limitations becomes as much or more work than building your own. There are things I would use, like state management libraries, but I figured most of the interaction stuff I'd rather do myself.
I'm excited for all the energy around tools for thought. Some notes on my current thoughts (probably to be revised in future entries).
Blocks as a basic, contained, and usually addressable unit feels to me "right". You can see it in Notion and Roam and many others.
I'm excited for all the energy around tools for thought. Some notes on my current thoughts (probably to be revised in future entries).
Blocks as a basic, contained, and usually addressable unit feels to me "right". You can see it in Notion and Roam and many others.
How do you change things?
I'm interested in users having the ability to personalize websites. I've mainly thought about it as a case for UI that lets you choose different options, probably powered by CSS (see components.ai's CSS.GUI).
My CSS Paint project lets you use a brush. It's interesting to use a brush. Should we let people style their website using a brush to paint styles on to divs?