KEkeepamovin·Sep 28, 2023Submission
Picnic CSS – A beautiful CSS library to kickstart your projects
3 points · Open discussionfranciscop
picnic
CSS2014–2023
franciscop / picnic
picnic
:handbag: A beautiful CSS library to kickstart your projects
5Distinct people
18Mentions
1Explicit recommenders
3.9KGitHub stars
What to know before exploring
What it is
:handbag: A beautiful CSS library to kickstart your projects
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
Hi there, I am the creator of Picnic CSS [1], a 5kb library similar to this one. I love the page and the logo, really minimalist and clean. A couple of tips for the library: -…
franciscop used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year18 dated mentions
Observed mentions: 2014-09-15 17:11:58 UTC to 2023-09-28 02:37:54 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 3 | 2 | 1 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 6 | 2 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
18 sourcesI've disabled Issues in some of my popular UI libraries and I couldn't be happier. Specially notorious was Picnic CSS[1] where many of the issues were on the level of "hey can you give me the code for X" or "how do you do X" where X was a general CSS question and not related to the library at all. I've also received unkind words when I closed some of my repos issues as a PR [2][3]:
> If you spot a bug or any other issue you may go to hell because this software is officially Bug Free(TM).
> part of offering these to the public through open software is maintaining them and allowing feedback from users.
> It seems umbrella.js project suffers the same desease.
I've noticed there was a strong push around 2016-2018 to recommend newbie programmers NOT to go to Stackoverflow, but instead to ask the questions straight in the Github issues. Turns o
Read the rest
ut, the problem was low quality questions all along, and that just converted an issue that StackOverflow had solved long ago into burnout for open source developers on Github.
Github needs to step up their game and give authors more powerful tools, there's so many entitled developers out there that will come and demand changes. It might make new devs feel less welcome, but the balance is tipped way too much to allow anyone to create massive spam for projects right now.
[1] https://picnicss.com/
[2] https://github.com/franciscop/picnic/pull/203/files
[3] https://github.com/franciscop/picnic/pull/202
I've had tremendous success by removing the "Issues" tab on a couple of my more popular and beginner-friendly Github repos[1] and just leave the "Pull Requests" open! Support tickets have gone down to almost 0 (I still get the odd email from time to time, to which I promptly quote a price and never get an answer), and most who contribute actually give back value.
As Alex says in this blog post though "it typically derails into a whiny tirade about me being a crappy two bit developer". Luckily this only happened twice for me, but it's funny because in here you can see it on the open[2] as someone opening a PR adding this text to the README:
> If you spot a bug or any other issue you may go to hell because this software is officially Bug Free(TM).
On a very perverse way I am kind of happy that happened, since it ratified my decision and I
Read the rest
became a lot more strict about when I help people. Any sense of "guilt" I had remaining after closing the Issues for not providing free support totally left after that incident.
[1] https://github.com/franciscop/picnic
[2] https://github.com/franciscop/picnic/pull/203
I don't know Francisco but I'm sure he deserves better than this
https://github.com/franciscop/picnic/pull/203/files
+If you spot a bug or any other issue you may go to hell because this software is officially Bug Free(TM).
+
In It’s OK for your open source library to be a bit shitty (2015)I made the grid of Picnic CSS very flexible to be able to do that, what do you think? :)
https://picnicss.com/documentation#grids
In exchange it makes the framework a bit heavy (~10kb), but if you use the CSS these can be modified and optimized as seen here: https://github.com/franciscop/picnic/blob/master/src/plugins...
Edit: this is the independent experiment I did before merging the grid system into Picnic, which I think it's still quite cool:
https://francisco.io/flexpoint/
In Spectre.css – A Lightweight, Responsive and Modern CSS FrameworkI'm the author of one of these independent CSS libraries that has been in the front page of HN several times. I normally use the libraries I write quite a lot, and it speeds things up for myself. This is mainly because of the deep knowledge I have for them, but if other people find them interesting so let it be.
Why would still make sense for skilled teams like yours? I can think several reasons:
- Prototyping: Probably not everything you do is detailed development and you might want to throw a quick prototype with not-too-bad styles. It won't be groundbreaking, but the ROI of using a CSS framework for those normally pays off.
- Cross-browser testing: an open source library will get bug reports from many varied places, and normally it's well tested cross-browser. Do you know about all of the flexbugs [1]? Do you even want to know? What ab
Read the rest
out the 2012 trick of Paul Irish for box-sizing [2]? Did you know it was updated in 2014 and how awesome this update is?
- Documentation: when onboarding a new member on the team, if you are using one of the more popular libraries there is a large amount of documentation, github issues, stackoverflow questions and general articles on the web. While you might put the work to do this internally, even with great teams the internal documentation is normally very much worse than the OSS docs.
- Other topics such as accessibility (color contrasts, keyboard states, etc) are normally polished in the libraries. It's not free, it comes after bug reports.
For these reasons it doesn't make any sense that an experienced team build the whole CSS utilities from scratch for each project. So the only sensible thing as a company is to reuse some of the CSS through projects. Then you got an internal library! Why not open source it? You got one of those!
Just look at the CSS [3] of "simple button" of my library, which already inherits half the style from a label. If I had to do buttons from scratch I'd forget at least 2 of those: the cursor pointer (because most links with .button would have it naturally, but not those with events and without href!) and the box-shadow to 0 (which only happens in some obscure combination of browser, device AND resolution). I just offloaded that knowledge long time ago into my library and now I focus on improving on other things :)
[1] https://github.com/philipwalton/flexbugs
[2] https://www.paulirish.com/2012/box-sizing-border-box-ftw/
[3] https://github.com/franciscop/picnic/blob/master/src/plugins...
This looks pretty great - I really like the look of Picnic, the author's lightweight (10KB) bootstrap alternative as well: https://github.com/franciscop/picnic
In Show HN: Umbrella JS, a 2.5kb jQuery alternativeYes! But please send it/them to http://github.com/picnicss/picnic , in my email it might slip away
In Ask HN: What did your 'Show HN' project turn into?I would call technical debt to writing it as you go, since there are many small bugs and inconsistencies that (hopefully) are fixed by these libraries. Just a couple of random examples:
- https://github.com/picnicss/picnic/issues/79
- https://github.com/picnicss/picnic/issues/64
So you can have a half-baked solution with 10 more minutes or use a tested and documented one and save 10 minutes.
In Pills: A simple responsive CSS grid for humans100% agree. Right now I'm deprecating the current grid based on ungrid in favor of a better float based grid [1]. I completely believe you, the most painful thing (maybe the only one?) for Picnic was definitely the grid, too many edges, no good model in css (and don't get me started on flexbox [2]).
[1] https://github.com/picnicss/picnic/issues/71
[2] https://github.com/picnicss/picnic/issues/58
In Ask HN: Best minimal CSS Framework for side projectAsk HN: Best minimal CSS Framework for side project
Hi,
I'm starting a small side project to learn web development and have fun.
Could you suggest a good CSS Framework for it?
My candidates are:
https://github.com/picnicss/picnic (it seems the most simple)
https://github.com/jgthms/bulma/ (very easy, but very minimal)
https://milligram.github.io/ (more complete)
Fot javascript I want to use Vue.js because it's easy, clean and I can control it.
Using Flask (Python) for backend.
12 points · Open discussionHi there, I am the creator of Picnic CSS [1], a 5kb library similar to this one. I love the page and the logo, really minimalist and clean. A couple of tips for the library:
- Subtle animations. It doesn't take many bytes, but it makes it look much better
- :active status gives visual feedback that you are clicking the element
- The grid doesn't accept gutter nor reversing order by css, which makes it not really mobile-friendly for alternating patterns in a page. There's not really a single good solution in css for both [2]
- <select> looks just like a normal input without down arrow in Firefox
Keep it up (:
[1] http://picnicss.com/
[2] https://github.com/picnicss/picnic/issues/58
In Milligram: A minimalist CSS frameworkAsk HN: GitHub thinks I'm a bot; what about my projects?
Github thinks that I'm a bot as they stated in big, red letters:
> One of our mostly harmless robots seems to think you are not a human.
> Because of that, it’s hidden your profile from the public. If you really are human, please contact support to have your profile reinstated. We promise we won’t require DNA proof of your humanity.
I get that, but then I open any of my projects in Incognito mode and they are all returning 404. Try it:
- Drive DB https://github.com/franciscop/drive-db 234 stars
- I Am Not A Lawyer https://github.com/franciscop/ianal 74 stars
Those two, for example, are listed in NPM. I have other projects listed in Bower. Fortunately I don't have anything in my personal account on jsdelivr, but I could. Does anyone know what happens to the NPM, Bower and jsdelivr when this happens?
I am waiting for resolution after conta
Read the rest
cting Github, but it can take any random number of hours from past experiences. This could happen to anyone. On the good side, the public "organization" repositories seem to be doing just fine:
- Picnic CSS http://github.com/picnicss/picnic 836 stars
Ask HN: Is SASS development stagnating?
I fell in love with SCSS on first sight and it has greatly helped me improve my front-end programming. From time to time I think of features that could make it even better. However, when I went to propose them I found that they are already proposed, like optional imports [1] and importing .css files (besides .scss) [2]. Some are closed, even though they are still planned for some point in the future.
While I understand that it's a large project and it should be not easy to manage it, the date is from 2011 and 2013. Further investigation[3] shows that from 2007-2011, the top contributor Natalie Weizenbaum (nex3) was really active (~4k commits) in the site but now she seems to work for Google[4] on Dart. The 2nd biggest contributor made ~494 commits, or 10%. Third one made 40 or 1%.
As a SCSS developer myself [5] I am interested in seeing S
Read the rest
ASS advance. I am of course not saying this in a negative tone, I am unable to contribute myself with ruby. I tried to contribute with some issues but as mentioned they are already filled.
Is SASS development stagnating? If so, what can we do to help it keep going? (for ruby but also non-ruby developers)
[1] https://github.com/sass/sass/issues/779
[2] https://github.com/sass/sass/issues/193
[3] https://github.com/sass/sass/graphs/contributors
[4] https://twitter.com/nex3
[5] https://github.com/picnicss/picnic
That's the whole Picnic CSS library, including the tab plugin. The plugin itself is 97 lines of SCSS (including spaces). The odd part, and I'm the author I think is that sometimes the html get a bit overcomplicated and not flexible.
You can see the source here: https://github.com/picnicss/picnic/blob/dev/plugins/tabs/_ta...
In Show HN: Pure css carouselShowing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.