You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’ve been using Pico CSS in several projects and appreciate its clean, minimalistic approach to semantic HTML styling. However, I noticed that the main branch appears to have had no commits since March 2025 (latest release v2.1.1 is dated March 15 2025). GitHub
Before investing further into Pico or recommending it more broadly, I’d like to ask:
Is Pico CSS still actively maintained by the core team or community?
Are there future plans (road-map) for upcoming versions (e.g., v3), new features, bug-fixes or community contributions?
If maintenance is entering a maintenance-mode (bug-fix only) or stoppage, would you consider adding a note to the README/status page to reflect that?
For users like me, what is the recommended long-term usage strategy: continue adopting new Pico versions, fork/maintain ourselves, or migrate to an alternative framework?
It would be really helpful to get clarity on where the project stands so that users can plan accordingly.
Thank you for your time and for all the work done so far — looking forward to hearing from you.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Pico CSS maintainers and community,
I’ve been using Pico CSS in several projects and appreciate its clean, minimalistic approach to semantic HTML styling. However, I noticed that the main branch appears to have had no commits since March 2025 (latest release v2.1.1 is dated March 15 2025).
GitHub
Before investing further into Pico or recommending it more broadly, I’d like to ask:
Is Pico CSS still actively maintained by the core team or community?
Are there future plans (road-map) for upcoming versions (e.g., v3), new features, bug-fixes or community contributions?
If maintenance is entering a maintenance-mode (bug-fix only) or stoppage, would you consider adding a note to the README/status page to reflect that?
For users like me, what is the recommended long-term usage strategy: continue adopting new Pico versions, fork/maintain ourselves, or migrate to an alternative framework?
It would be really helpful to get clarity on where the project stands so that users can plan accordingly.
Thank you for your time and for all the work done so far — looking forward to hearing from you.
Beta Was this translation helpful? Give feedback.
All reactions