Is this project abandoned?

[coezbek]

I love the simplicity of Picocss, but am curious to learn if @lucaslarroche is still around to maintain this project (no Github activity since August, no commit to Picocss since 10 months).

[Tyler-Keith-Thompson]

I had the same concern and switched to a fork that looks well maintained

[Yohn]

I had the same concern and switched to a fork that looks well maintained

Thanks for the mention!

I'm not sure what happened with the original author of Pico CSS, I hope he's ok and comes back sometime.

In the meantime I have forked the project a few weeks ago and corrected a bunch of errors that some people mentioned here, or that I've found. I've also merged a bunch of pull requests that are open here, and added some that features that I needed. Here's an updated demo of what I've added.

[bemyak]

I was considering switching to PicoCSS for a while now, but the absence of the main developer leaves me hesitant.

The fork raises some concerns as well, since I can see JavaScript is being introduced. It shouldn't be a requirement for such things as accordion or navBar now that we have the popover api.

[Yohn]

I was considering switching to PicoCSS for a while now, but the absence of the main developer leaves me hesitant.

The fork raises some concerns as well, since I can see JavaScript is being introduced. It shouldn't be a requirement for such things as accordion or navBar now that we have the popover api.

Understandable, and the JavaScript is not needed for the accordion to still function as expected. The reason for bringing the JavaScript in for the accordion was to have it slide when opening, and with just css I believe it only did the slide on the first time it was opened.

And there's no JavaScript for a navbar.

The theme switcher might be what your referring to for the JavaScript in the navbar? That JavaScript and the modal JavaScript is from the original Pico examples pages.

The file validator JavaScript makes it nicer to view the files when selected, and validate the files selected since native browser does not validate files via the attributes, but is not needed if you don't want it.

The last JavaScript added is the notification which was from an open pull request.

[bemyak]

Oh, I see, probably I misread the code. I'll give it a go then :)

[Yohn]

Oh, I see, probably I misread the code. I'll give it a go then :)

Let me know if you find any issues or if you can think of anything you'd possibly like to see added!

[mediaformat]

I'm not sure what happened with the original author of Pico CSS, I hope he's ok and comes back sometime.

Same!

[marko878]

I had the same concern and switched to a fork that looks well maintained

Thanks for the mention!

I'm not sure what happened with the original author of Pico CSS, I hope he's ok and comes back sometime.

In the meantime I have forked the project a few weeks ago and corrected a bunch of errors that some people mentioned here, or that I've found. I've also merged a bunch of pull requests that are open here, and added some that features that I needed. Here's an updated demo of what I've added.

The hero we didn't know we needed, but a hero nevertheless! I just used a fork to update one of the older projects, went rly smoothly.

On the other side, I did abandon any kind of CSS framework for personal projects in the meantime, overhead is just too big, with not too many upsides. With the recent (last few years) CSS updates, most of the scss stuff that I used for last 10+ years (nesting, vars, basic functions etc) is (I can't belive I say this) available natively in browser, plain old unprocessed .css file baby. GL with fork and hope everything is fine with MIA authors.

[tomcon]

Just noticed @lucaslarroche made a commit to picocss two weeks ago on Jan 28, 2025

[4levels]

Let's all help @lucaslarroche by providing some feedback on the open PR's and/or create new ones and get this amazing project back on track. This is imho by far one of the nicest CSS libraries out there at the moment and to offload some of the chores related to maintaining a public repository can sure help.

Keep up the great work!

[coorasse]

Love this project! Just got here and saw a release last week. I think this issue could be closed.

[cboecking]

The website still references ***@***.*** from https://picocss.com/docs#usage-from-cdn Should this be changed as well, or all the existing sites automatically update with the new release? I hope the answer is we will create a ***@***.*** (or something similar) to prevent changes to existing sites.

…

On Sat, Mar 22, 2025 at 3:35 PM Alessandro Rodi ***@***.***> wrote: Love this project! Just got here and saw a release last week. I think this issue could be closed. — Reply to this email directly, view it on GitHub <#640 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2IKFQ54Y2RJU2ZPQIHTV32VXCRDAVCNFSM6AAAAABS3OKQN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBVGYYTQNBTGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> [image: coorasse]*coorasse* left a comment (picocss/pico#640) <#640 (comment)> Love this project! Just got here and saw a release last week. I think this issue could be closed. — Reply to this email directly, view it on GitHub <#640 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD2IKFQ54Y2RJU2ZPQIHTV32VXCRDAVCNFSM6AAAAABS3OKQN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBVGYYTQNBTGQ> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[erutan]

Considering this as a starting point for a side project, and have similar single maintainer concerns as posted earlier in the thread.

While it's not abandoned, it's not very active either. It seems like the maintainer mostly works on this in the winter a bit, then in early spring puts out some releases. There's a number of fairly straightforward bug fix PRs sitting here again.

It'd benefit from another maintainer or a more active fork - I haven't dug deeply into @Yohn's code, but the additions seem reasonable and someone could always just chose to not import certain components. I like the no-JS approach of Pico, but realistically there are multiple components that don't function without JS, so bundling some simple JS with them makes sense to me. :)

[erutan]

I'm using Yohn's fork on a side project, so far things are working well. I don't think the bootstrap style grid "rows" is appropriate for this project's scope and intent, but otherwise I haven't come across anything I disagree with.

It seems like he stopped working on his fork when this project briefly saw some attention again (which makes sense), but now both are a bit in limbo. It does feel PicoCSS could use another maintainer, but since the creator doesn't seem to have time to keep up with it, they probably don't have time to coordinate with someone else.

[vardumper]

@lucaslarroche I'd like to offer some help with maintenance here, too.

I have also emailed Lucas and would report if I get some relevant info.