svelte-logoipsum VS skeleton

Hey all! I'm frequently using logo placeholders from https://logoipsum.com/. The procedure their designed though makes it difficult to use the SVG directly in code rather than a design app. I created this component library so I could use all the logos directly from Svelte. https://github.com/srmullen/svelte-logoipsum All the logo components have‍ properties for changing the colors to fit whatever design you're working on. If there are other features that would be useful let me know or open a pull request!

Hi everyone, I'm so happy I can finally share the project I've been working on for the past few months. Ato UI is a themeable component UI library built with UnoCSS (with the Tailwind + Windi preset) and offers both styled and headless components, since the library is build on top of other fantastic headless libraries like Headless UI and Grail UI. Skeleton was also a big inspiration, as you'll be able to see in the designer page and the token system.

Vue 3 (with is quite close to Svelte in terms of DX, but Svelte has the edge here. Svelte is so simple, elegant and concise.<p>The biggest advantage of Vue is the ecosystem. However, Svelte is catching up. Some interesting UI component libs have recently arisen, e.g. <a href="https://skeleton.dev" rel="nofollow noreferrer">https://skeleton.dev</a>.<p>Performance wise, both are super fast.<p>Make sure to check out Sveltekit, even for building pure SPAs. The routing and data loading are worth it alone.

Should I use a framework independent library like DaisyUi or something related to svelte like flowbite-svelte or skeleton? Do I need svelte components? Should I build them by myself with DaisyUi?

I am using https://skeleton.dev for a dashboard and it is pretty amazing!

Hi, I've created a project with the skeleton.dev scaffolding tool: