1. What are your plans now?
2. Your style seems unique, and even your mood board that you shared with the designer has a particular style; did you always gravitate towards that type of art? If not, how did you come upon it?
> Historically, we avoided this to maintain a separation of concerns, but it's puzzling why some prefer reintroducing similar methods. Is it just to save a few keystrokes?
In bigger projects, if we start looking at the amount of files one has to deal with, Tailwind becomes very appealing.
We've went through the regular `.css` route but then you have weird names, and, potentially, duplications or even conflicts.
`css modules` is an option but you've now essentially duplicating the number of files that you have for each component / page.
`sass` or `less` essentially bring the problems from `css modules` and regular `.css` into one.
I don't inherently like or dislike Tailwind (although I very much started by absolutely disliking it) but you feel its value in a project with 200+ files composed of components and pages
The project is outstanding but the fact that you've documented everything AND did a video about it speaks volumes about what you'll achieve if you keep at it
I did but I've been feeling that the LLMs end up giving an average solution / something that I don't fully understand / the same solution that just looks slightly different and I think I'll end up getting influenced by its responses instead of thinking by myself or learning from others
Are you open to do it with Node? I wrote a blog post[0] with a fairly easy setup. If you're using markdown and any markdown processor you should be good to go.
