Now that we have an OpenCollective we should add all sponsors' logos (i.e. folks who contribute 200$+) to the homepage, probably at the bottom below the introductory explanation.
OpenCollective has an API that gives you all the members: https://opencollective.com/styled-components/members/all.json?tierId=3278
I will be happy to do this 馃槑
Awesome, looking forward to the PR!
I'm thinking about the design like this, just adding the logos linked:

this photo is just a design not actual implementation, forget about margins and these stuff.
or should we make it like backers version ?
No I like that! 馃憣
This is done just couple of things need your opinion on them:

Also, OpenCollective API doesn't have Access-Control-Allow-Origin header within styled component API, take a look at this https://github.com/opencollective/opencollective/issues/342
Looking great! I assume most sponsors will be companies, I think we should filter out the core team from those.
/cc @xdamman
Looking great! This API endpoint only returns the members of the given tier. So team members won鈥檛 show up unless they are also part of the tier.
But why is the core team part of the Sponsor tier then? :thinking: None of us sponsor styled-components
I think a config should be there to categorize the sponsors.
Take a look at babel open collective, they have sponsors categories and if you take a look at their API, they have tier key in the sponsor object and in styled component API doesn't have.
We have a "Sponsor" tier and a "Backer" tier: https://opencollective.com/styled-components/

I want to display the Sponsors on the homepage.
It's because it should be TierId and not tierId as the query parameter.
I would like to contribute to this. Could you tell me where I can access your homepage on the GitHub?
@adaynit unfortunately, @osamajandali is already working on this in #230!
@adaynit Actually, this is the repo for the homepage 馃槄 Feel free to grab any of other open issues! 馃憤
@osamajandali need any help with #230 ?
@mckernanin Thank you ! I have finished it out back then but @kitten have issues on it that I need more details on it.
Maybe the reviewers are busy with some other stuff that's why I was on holding state.