tea 🌺May 8, 2024

I have someone I'm shepherding to learn tailwind and Astro. They're contributing to an open source project. They are using tailwind with the apply directive in style files with classes.

How can I politely tell them to use inline classes, colocate jsx / component and styles? I feel like coming from a css background yeah files make sense. But with components it's an added step.

I can't find any articles advocating for colocation of jsx / tailwind nor know how to articulate the ask. Thoughts?

Show threadVint Prox

@thomasreggi Whatever happens, just don't fall in the CSS-in-JS rabbit hole. Phooie, what nonsense even is that, I mean?

Now, in regards to #JSX and #components... As long as it's the same #CSS or, perhaps, CSS and non-over-the-top #CSSModules, the transition should not take much time. One serious benefit is maintaining component styling in one file with the layout and script bindings (most of the time, it results in less split brain logic than with separate files).

May 8, 2024 at 3:46pmWeb
Show threadVint ProxMay 8, 2024
@thomasreggi You mentioned #Astro. If JSX syntax is killing your fellow #CSS enjoyer and aspiring components coder, you can take Astro's flexible architecture and employ #Vue, #Svelte or another framework of their choice for the set of components they are working on. Sure, this way you are bloating beyond simple #React, but for the sake of exchanging syntax to something bearable for your contributor, as well as you!