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.