Play with TailwindCSS in the Browser

Re:Play with TailwindCSS in the Browser by aaronbrethorst on Friday June 10, 2022 @12:04PM (#31696018)

This isn't meant as a contradiction of your point, but there are plenty of ways to use component-based architectures with server-side rendered apps, too, like GitHub's ViewComponent gem for Rails. https://viewcomponent.org

Also, I'd go so far as to say that if you're not using a component based architecture for your web app's view layer, you're creating a ton of extra work for yourself.

[ Parent | on HN ]

Re:Play with TailwindCSS in the Browser by cgarvis on Friday June 10, 2022 @02:28PM (#31697713)

+1 Using it in a Elixir/Liveview app. Using phx_component_helper has made making those components really easy. https://phx-component-helpers-demo.onrender.com

[ Parent | on HN ]

Re:Play with TailwindCSS in the Browser by inopinatus on Friday June 10, 2022 @07:44PM (#31700585)

I’d add you don’t even need ViewComponent. Layouts, partials, variants, and helper functions provide plenty of heavy lifting options when it comes to refactoring your HTML.

My take on ViewComponent: it’s what helper functions become when they grow up into proper objects. Great for larger projects, may be more infrastructure than necessary for smaller ones, adopt incrementally when they seem compelling.

[ Parent | on HN ]

Re:Play with TailwindCSS in the Browser by aaronbrethorst on Saturday June 11, 2022 @05:51PM (#31708797)

Don't need it, but I've found ViewComponent to be a big win over partials. Being explicit with the available state instead of implicit has helped me catch plenty of bugs.

[ Parent | on HN ]

Re:Play with TailwindCSS in the Browser by Vinnl on Sunday June 12, 2022 @06:10AM (#31713365)

Yep exactly, and Tailwind does indeed still make sense with that approach!

[ Parent | on HN ]