skeleton VS Svelte

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!

the technical decision how Svelte should treat self-closing html elements was hindered by Prettier:

Svelte

React has introduced measures like batching state updates, background concurrent rendering and memoization to tackle this. My opinion is that the best way to solve the problem is by improving their reactivity model. The app needs to be able to track the code that should be re-run on updating a given state variable and specifically update the UI corresponding to this update. Tools like solid.js and svelte work in this manner. It also eliminates the need for a virtual DOM and diffing.

Similarly to Promises/A+, this effort focuses on aligning the JavaScript ecosystem. If this alignment is successful, then a standard could emerge, based on that experience. Several framework authors are collaborating here on a common model which could back their reactivity core. The current draft is based on design input from the authors/maintainers of Angular, Bubble, Ember, FAST, MobX, Preact, Qwik, RxJS, Solid, Starbeam, Svelte, Vue, Wiz, and more…

Svelte is a powerful web framework that offers a fresh approach to building web applications. Its simplicity, reactivity model, and built-in features make it an excellent choice for developers looking to create efficient and maintainable applications. By following this guide, you should now have a good understanding of how to get started with Svelte and build your first components, routes, and transitions. You can read more about svelte on the official Svelte website.

Use .NET features (especially dotnet watch) as a setup for a client-side Svelte application, starting from a simple C# console app.