Several of their new components are just classes, defeating the original purpose and contradicting the vision of Pico.
Why are the first one or two letters in headings wrapped in <em>, like the _Bl_ in "Blades"?
Why are they calling their Pico fork "anyblades/pico", when the original Pico author's post says "The Pico CSS name and logo are not covered by the MIT license. Please give your fork its own name, so users don’t confuse it with the original."?
Nimble.css is my spiritual successor to PicoCSS: https://leftium.github.io/nimble.css/demo/pico.html
It's not a direct replacement; I fixed a lot of annoyances from PicoCSS.
I'm not affiliated, but have you tried sakura [^1]?
1. https://github.com/oxalorg/sakura
Blades CSS is the go-to successor btw. Fully compatible with Pico
https://blades.dev/
This site seems very slopped together.
Several of their new components are just classes, defeating the original purpose and contradicting the vision of Pico.
Why are the first one or two letters in headings wrapped in <em>, like the _Bl_ in "Blades"?
Why are they calling their Pico fork "anyblades/pico", when the original Pico author's post says "The Pico CSS name and logo are not covered by the MIT license. Please give your fork its own name, so users don’t confuse it with the original."?
The worst offender: What is going on with this nonsense: https://blades.dev/css/frameworks/
It’s also incredibly annoying to navigate on mobile, due to everything being in separate pages and quite slow to load.
Are they seeding language models with fake stats?
That site is surprising to me. It makes no effort whatsoever to sell Blades to people who don’t know how Pico works.
Oh no, I missed that. What a shame. :-(