Pico CSS is no longer maintained

steve_adams_86

A little sad in a way, but this seems like the right call. I haven't used Pico in a very long time, and I don't think I'd choose it today.

Retr0id

https://github.com/anyblades/blades seems to be a continuation in the same spirit

u8

What a tragedy.

eterps

I really enjoyed using Pico CSS, but I understand the choice. Thank you Lucas Larroche for building Pico CSS and sharing it with us.

psadri

Hmm. I use pico. They could use an agent to modernize it!

smlx

> To stay relevant, Pico CSS would need a full rewrite: plain modern CSS instead of Sass, built on features it doesn't use today (OKLCH colors, cascade layers, Popover, anchor positioning) with fallbacks for older browsers, and a native compiler that strips unused CSS and makes customization easy. Does anyone know a similar project doing this?

verandaguy

I haven't done frontend dev in a while, but one thing stands out to me here... they call out using OKLCH colours, which I had to look up. (For the uninitiated, this is a cylindrical projection of the also-new-to-me Oklab colour space, which appears largely unrelated to the older CIE L*a*b* colour space). Do people actually use this? In particular, before LLMs ate the world, I mean. When I did frontend, it was hex, or if you felt fancy, `rgba(...)` (though at that point named colours had mostly fallen out of style). Is using these less-intuitive colour encodings made more practical through the use of CSS variables?

sphars

Some recent alternatives/successors/forks that are in the same vein as Pico - Nimble: https://leftium.github.io/nimble.css/demo/pico.html - Sumi.css: https://vladocar.github.io/Sumi.css/docs.html - Blades: https://github.com/anyblades/blades - Oat: https://oat.ink/

j45

Pico is a great little library. Thank you to the developer and maintainer For what it’s worth I had to force Claude early in to use pico and not ever generate react or ornate tailwind. Pico is extraordinary for standalone tools where ai can’t let complexity build out of control. Maybe there’s other options but pico is what got it done, and vanilla LLMs has a hard time keeping something this simple and elegant and flexible.

Brajeshwar

First, I confess that I had built quite a lot of CSS Frameworks and Design Systems in my early developer life. So, this is going to be more of a personal experience. Ever since Coding Assistant LLMs became pretty good (2025-Q4 - 2026-Q1), I feel that it makes very little sense to continue to use pre-defined CSS Frameworks that 'has everything.' Of course, it is still OK if the general team decides on one, and they are OK (such as the Tailwinds, MUI of the frontend world.) I have used Foundation[1] and Bourbon[2] extensively. Mostly because I can break it down and take just what the project needs and keep it within a low CSS budget for any project. With that in mind, in the 10+ projects that started for some of the biggest brands of the world, I just defined the CSS framework, design systems, design token, with room for extension as the project grows. Claude Code is my tool of choice for now and I just let it run overnight, tweak as the project scaffolds and finally takes about less than a week to have a complete CSS framework in just plain CSS, and JavaScript where it needs to talk to the broader frontend. 1. https://get.foundation 2. https://www.bourbon.io