HN user

aaronharding

6 karma
Posts0
Comments6
View on HN
No posts found.

i am not sure its that tricky, just have some user settings that are loaded when you open individual markdown files. show a different ui or hide some parts of the ui if need be!

The docs address this actually:

Making changes in a project that has tons of custom CSS is worse.

You have to think up class names all the time — nothing will slow you down or drain your energy like coming up with a class name for something that doesn’t deserve to be named. You have to jump between multiple files to make changes — which is a way bigger workflow killer than you’d think before co-locating everything together. Changing styles is scarier — CSS is global, are you sure you can change the min-width value in that class without breaking something in another part of the site? Your CSS bundle will be bigger — oof

Check it out here: https://tailwindcss.com/docs/reusing-styles

There are surprisingly a number of benefits when you allow this kind of duplication. It's a subtle idea but the idea is not all duplication is bad and not all duplication is alike.