Currently working on a redesign for my passion project website directory intrasti.com. There's websites and topics but there's a lot of focus on topics. I'd like to bring the focus away from topics and balance it out between them. The new design is going to introduce a new 'topic card' UI instead of a shelves approach that's currently live.
I've been avoiding using Tailwind or any framework as to try to identify maintainable ways to build with just the web platform in a way that I also enjoy writing code. The last day or so I've been strictly using child combinators (the > in: .container > .thing) and I've found my CSS to easier to read and less likely if not impossible to pollute child components.
Also I recently converted the whole project from a domain-driven source code organizational approach to a more flat horizontally layered approach, that's TBD on its usefulness although first impressions is that I don't feel like something could be amiss when I go to deploy whereas in a heavily domain-driven architecture I get a feeling that there seems to be a stone left unturned somewhere.