Get started Inspired by Pico ✨
[!NOTE] As you might already know,
Pico CSS is officially no longer maintained — but:
Development continues under Blades CSS 🎉 #
| Homepage: | |
|---|---|
| Documentation: | |
| Source code: | |
| Underlying Pico fork: |
What's fixed? #
Blades focuses exclusively on the pico.css version, similar to how simple.css is maintained (for Sass version check
@Yohn's fork instead).
Pico issues resolved in Blades:
#751 🛠️ Button focus ring measures 1.77:1 (light) and 2.01:1 (dark), where SC 1.4.11 asks 3:1
#744 🧩 Proposal: Classless Dropdown component leveraging Popover API
#740 🛠️ Remove nonessential npm-run-all dependency to reduce supply chain attack surface
#738 🐞 Submit button margin affecting siblings within .grid
#734 🐞 RTL breadcrumbs add weird backslashes
#733 🐞 Fix for datetime input width within groups within grids on medium breakpoint
#731 🛠️ Allow to selectively unreduce motion like
[aria-busy="true"]does#727 🐞 Fix dropdown summary ul offscreen (Safari)
#721 🛠️ Possible duplicate of text-align property inside the same element selector
#701 🐞 Nav dropdowns display error with Firefox
#696 🛠️ Missing styling for
<var>element +#695
#670 🐞 Slow website picocss.com ↗ (
box-shadowperformance issues)#513 🐞 Image element attribute height is overridden
#482 🧩 Pico CSS Scale
See fixes in action:
- Demo:
@picocss/pico issues reproduced (where applicable)
- Demo:
@anyblades/blades running without issues (on exact same markup!)
Every Blades build includes the actual .diff with exact changes against "canonical" pico.css:
What's new? #
See /#docs marked with NEW.
All shipped as blades.css — a drop-in compatible replacement for pico.css.
How to migrate? #
Just switch pico.css to blades.css— and voilà!
blades✨
Same spirit, new home. #
🥷