skeleton VS view_component

I'm a bit bias here, but we've had a lot of support for my UI library called https://skeleton.dev/. We've taken a lot of the doc design and visual queues from them, though we've built with Tailwind/Svelte in mind from the ground up

I just found Skeleton, which are pre-built components using TailwindCSS. https://skeleton.brainandbonesllc.com/

I... might have inspected elements nonstop on https://skeleton.brainandbonesllc.com in order to figure out how your team did it and shamelessly applied it to my site example.

Skeleton looks promising, but you have to buy into Tailwind CSS.

Thanks! Even though the site is useable I'm looking into Skeleton (Tailwindcss Component Library that's good looking and quick/easy. In beta.) https://skeleton.brainandbonesllc.com/

You might check out Skeleton (full disclosure, I'm one of the creators)

https://skeleton.brainandbonesllc.com/

When my partner and I were getting started with Svelte we noticed there was plenty of wrapper libraries, but very few that lean into the benefits of Svelte specifically. We wanted something like Mantine from the React world.

We're still early days (we've open source and public for about a month) but the feedback has been really positive. The one thing to note is we pair heavily with Tailwind, so if that's not your jam the library may not be for you. However for any sizable app where you're building a design system, we find it extremally helpful and productive.

Hopefully you can give it a try and it helps out! My username on our Discord is endigo9740 if you need any help!

When searching for examples of table components built with the ViewComponent gem, I was surprised to find none. After some inquiries, I came across examples that worked like this:

View components offer two primary ways to interact with the component: passing arguments to the initializer and using slots:

For example, splitting out views into partials? Or the new ViewComponent feature that's becoming quite popular - https://viewcomponent.org/

I used to do "pure ruby" approach to that -- but basically wound up realizing I was re-inventing github's view_component. Their design goals were similar enough to what I was trying to do, that it made more sense just to use that, rather than try to re-invent it myself.

ViewComponent

The linked one is my Rails implementation, written for ViewComponent. The official version uses Nunjucks.