anydigital

┣ A modern drop‑in successor to Pico CSS

┣ New https://blades.dev/css/dropdown/ via Popover API

┣ New https://blades.dev/css/compact/ version for both Blades & Pico

┣ New https://blades.dev/css/layered/ modules for SvelteKit, Next.js, Nuxt, Astro, etc.

┣ Merged color schemes via `light-dark()`

┣ Experimental https://blades.dev/css/ninja/ moved into separate repo

┣ Added exact https://blades.dev/css/pico/#diff vs. "canonical" Pico

┗ More https://blades.dev/css/pico/ issues resolved

well, we do our best to revive it under https://blades.dev/css/pico/

For Blades CSS, we also set up a dedicated page outlining key details and fixes made in underlying Pico fork: https://blades.dev/css/pico/

Yes, and the FastHTML team was very collaborative in switching to our underlying Pico fork (Blades core)

100%

We do: https://github.com/anyblades/blades

Already plain modern CSS instead of Sass, has Popover API, and CSS layers for individual components, OKLCH colors are on the way.

Drop-in compatible with Pico CSS (via underlying fork)

Thanks for sharing! Same spirit, new home.

We’re actively maintaining Blades CSS over on GitHub and Discord, and would love community feedback.

We also set up a dedicated page outlining key details: https://blades.dev/css/pico/

No fake stats or LLM seeding. The initial percentages were calculated against respondents who actively use CSS frameworks (~4.8k devs). They have been updated to reflect total State of CSS respondents (~9k–10k), including vanilla/CSS-in-JS users.

Appreciate the honest feedback, so here are direct answers and fixes:

Utility classes: Offloaded to a separate "anyblades/ninja" repo. Core Blades stays true to original Pico (which btw used some classes like .overflow-auto).

Fork naming: The main project is Blades at https://github.com/anyblades/blades. The "anyblades/pico" repo was just an early bugfix fork created months before Pico announced deprecation.

CSS Frameworks stats: The initial percentages were calculated against respondents who actively use CSS frameworks (~4.8k devs). They have been updated to reflect total State of CSS respondents (~9k–10k), including vanilla/CSS-in-JS users.

Good catch re navigation — added sticky breadcrumbs similar to original Pico's website.

The current focus is serving existing Pico users looking for a direct, compatible drop-in. General CSS framework materials will come later.

https://github.com/anyblades/blades — new home for Pico CSS

https://github.com/anyblades/pico — underlying fork

Will Ronaldo score +24 in '26/27 season to hit 1K?

Will Messi score +81 before his contract ends in 2028?

Can Mbappé catch up to Messi's pace? (behind over last 3 seasons)

Will Haaland & Yamal join the race? (outperforming Ronaldo, but trailing Messi & Mbappé)

you might want to try Blades CSS also, a fully compatible and actively maintained successor to Pico CSS (which was last updated >1 ago)

https://blades.ninja/

https://github.com/anyblades/blades

Brand new home for Blades CSS, a fully compatible and actively maintained successor to Pico CSS:

https://blades.ninja/

Key dependencies:

"@11ty/eleventy": "^4.0.0-0",

"@11ty/eleventy-fetch": "^5.1.2",

"markdown-it-deflist": "^3.0.1",

"@anyblades/eleventy-blades-base": "^1.0.0" sub-dependencies:

    "@11ty/eleventy-navigation": "^1.0.5",

    "@11ty/eleventy-plugin-rss": "^3.0.0",

    "@anyblades/blades": "^2.3.1",

    "@anyblades/eleventy-blades": "^1.0.0",

    "@uncenter/eleventy-plugin-toc": "^2.1.1",

    "markdown-it-anchor": "^9.2.0",

    "markdown-it-attrs": "^4.3.1",

Open-sourced here: https://github.com/anyblades/blades.ninja

we were focusing on Mobile and Desktop versions, are you somewhere in between?

to be tracked here: https://github.com/anyblades/blades.ninja/issues/7

We also moved away from Tailwind — Pico CSS. It feels like a breath of fresh, modern CSS air.

We actually loved it so much that we’ve taken over maintenance of a fork, and just released our Pico successor candidate: https://blades.ninja/

+1 for Pico CSS! It’s fantastic.

We actually loved it so much that we've taken over maintenance for a fork here: https://github.com/anyblades/pico

fixes: #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 #670 Slow website + #718 (box-shadow performance issues)

add-ons: https://blades.ninja/

Docs & demos: https://blades.ninja/css/pico/

---

Now including all features from Blades CSS, shipped as pico.blades.css — a drop-in compatible replacement for pico.css.

Also, it includes various fixes for original @picocss/pico issues:

#731: Allow to selectively unreduce motion like [aria-busy="true"] does #670: Slow website picocss.com | box-shadow performance issues & PR#718 #721: Possible duplicate of text-align property inside the same element selector #701: Nav dropdowns display error with Firefox #727: Fix dropdown summary ul offscreen | in Safari

Just upgraded our old-school CSS-only Float Label library to v2-alpha classless version introducing new `:has(*:placeholder-shown:not(:focus)) label` trick:

Repo: https://github.com/anydigital/float-label-css

Docs: https://blades.ninja/css/float-label/

Feedback is welcome!

Use Blades `<i>`-helper to wrap emojis, favicons, or simply drop Font Awesome icons inside links. It automatically handles sizing and alignment while preventing underline on icons.

How: `a:has(>i){ display: inline-flex }` and `a>i{ float: left }`

Code: https://github.com/anydigital/blades/blob/main/src/link-icon...

Demo: https://codepen.io/editor/anydigital/pen/019d2b94-5616-75dc-...

Docs: https://blades.ninja/css/link-icon/ (available via CDN/npm)