<story><title>Shoelace 2.0 release: UI toolkit that works with all frameworks or none at all</title><url>https://shoelace.style/</url></story><parent_chain><item><author>claviska</author><text>Shoelace author here.&lt;p&gt;A couple days ago, I released Shoelace 2.0, an open source library of common UI components.&lt;p&gt;These components work with any framework, can be loaded via CDN, are fully customizable with CSS (no preprocessor required), and install easily with a simple script + stylesheet. They were built with Stencil.js, which is a fantastic tool. The end result compiles down to vanilla web components.&lt;p&gt;Each component was designed from scratch to be lean, customizable, and easy to use. Accessibility is a common question folks have about component libraries. I’m definitely not an expert here, but I&amp;#x27;ve spent a lot of time trying to get it right. I would like to echo the experts and say that accessibility only starts with components, but hopefully having a good foundation to build on will encourage others to think about it more at higher levels.&lt;p&gt;I hope you&amp;#x27;ll take a second to check it out! I&amp;#x27;m happy to answer any questions you have about the project, how it&amp;#x27;s built, etc.</text></item></parent_chain><comment><author>manjalyc</author><text>Longtime user of bootstrap &amp;amp; tailwindcss for pet projects. I&amp;#x27;ve looked at the &amp;#x27;What Problem Does This Solve&amp;#x27;, but I&amp;#x27;m not sure where Shoelace could fit into my workflow.&lt;p&gt;Bootstrap is great for when I just want to quickly prototype and build a decent looking interface, but it feels confined when I start wanting to style things myself. When designing MPAs I typically use Bootstrap.&lt;p&gt;Tailwindcss is great for styling anything and everything, but I find sometimes I waste too much time styling little things that other CSS frameworks already have nice defaults for (and I am a terrible designer so this compounds my dificulties). I often use tailwind for SPAs.&lt;p&gt;Forgive me if my question is a little naive, but where could I fit Shoelace in for pet projects? Do you see it as being a suitable replacement for one of these usecases? Complementing them? Does it lie somewhere in the middle?</text></comment>
<story><title>Shoelace 2.0 release: UI toolkit that works with all frameworks or none at all</title><url>https://shoelace.style/</url></story><parent_chain><item><author>claviska</author><text>Shoelace author here.&lt;p&gt;A couple days ago, I released Shoelace 2.0, an open source library of common UI components.&lt;p&gt;These components work with any framework, can be loaded via CDN, are fully customizable with CSS (no preprocessor required), and install easily with a simple script + stylesheet. They were built with Stencil.js, which is a fantastic tool. The end result compiles down to vanilla web components.&lt;p&gt;Each component was designed from scratch to be lean, customizable, and easy to use. Accessibility is a common question folks have about component libraries. I’m definitely not an expert here, but I&amp;#x27;ve spent a lot of time trying to get it right. I would like to echo the experts and say that accessibility only starts with components, but hopefully having a good foundation to build on will encourage others to think about it more at higher levels.&lt;p&gt;I hope you&amp;#x27;ll take a second to check it out! I&amp;#x27;m happy to answer any questions you have about the project, how it&amp;#x27;s built, etc.</text></item></parent_chain><comment><author>iCarrot</author><text>The &amp;quot;in&amp;quot; animation on components like dialog or drawer doesn&amp;#x27;t seems to work on Firefox (78.0.2 on Windows). Very abrupt in, smooth fade&amp;#x2F;slide out.&lt;p&gt;Also there are small version of buttons but none for other form controls which is quite odd.&lt;p&gt;Seems nice and lightweight overall. I would love to see a dark version too.</text></comment>