@jemeneradev
Posted
Personally, I find css preprocessor quite useful. With scss, for example, you can nest css definitions. That makes things logical and neat. You can also have modules and mixins that act a type of style inheritance, so you don't have to repeat common styles. Not to mention loops in css.
For clean css, you'll just have to look at different approaches. For instance, nowadays, tailwind css is all the rave. I tend to stay away from that because it makes the markup too cluttered. You could also checkout bem (http://getbem.com/introduction/).
As far as I know, gatsby is content management system, so between the two, I would opt for nextjs.
Regarding component structure. One rule I follow is, if I find myself repeating code, more than likely it can be group logically.
Marked as helpful
@kristiingco
Posted
@jemeneradev Thank you so much! This helps a lot. I am definitely interested in utilizing Tailwind and/or BEM conventions in my next project!
