Yeah, I think having the tailwind for layout only is a safe approach

I agree with you @mainawycliffe.dev
Indeed a setup like this requires some extra attention

Having reusable CSS variables between these two, could work nicely for styling as well.
A setup like this could be used by any new component development. What I've seen happening a lot though, is that Devs apply inline styling Vs creating reusable components. 2/2

My take on this is that I would prefer to have tailwind only for layout and not styling. For styling we have the UI lib components.
But, the product's design system could demand more UI components that might not be supported by, say, material. 1/2

Would you combine both Angular material (or any other UI lib) along with tailwind? If so, what would be the purpose of tailwind?
Layout only or styling as well?

📌

Congrats @brandonroberts.dev 🎉🎉🎉

I haven't tried that. Can I record and edit through the same app?

Congrats 🎉🎉
Very well deserved 💯