jaredgorski

I was being tongue-in-cheek. Didn't mean to sound like a smartass. Thanks for reading!

Oddly enough, I just realized I do both

For clarity, this post was more creative writing exercise than technical treatise. Thanks for reading!

For clarity, this post was more creative writing exercise than technical treatise.

Maybe you should write a web blog post nobody will read about it

Your exasperation is absolutely shared. Thanks for engaging

I did mention that our clients are enterprise-level.

But I did fail to address a more general decision-making process regarding choosing frontend architecture. If I did (and I probably will soon), I would talk a lot about the egregious initial load times on too many blogs that roll crazy dynamic tools for what should be a completely static site.

Right?! Yeah, the title should be “A few patterns we implemented lately”. I do have more thoughts specific to practical frontend architecture though, so I guess I’ll just hope you see the next post.

Using Tailwind alongside anything is pretty simple. It just generates stylesheets for you based on what you use. All you need to do is set up the build (so that it knows which style rules to include and which to purge) and then start using Tailwind classes in your markup.

As for “best practices”, I’d say there’s not many problems you’ll run into using something like Tailwind. Any configuration improvements you make probably won’t break anything, but you should still read the docs before you get started.

Ha! Yes. It’s pseudo code though. Please don’t copy and paste it.