Filter by stars about headlesscms.org

[erquhart]

Brief requirements (updated from conversation below):

• Borrow concept and layout from staticgen.org (can't reuse code, that's Ruby and this is Go)
• Left dropdown is a filter:
  • "View all" - default, placeholder
  • "Open source" - filters to show only open source
  • "Proprietary" - filters to show only propietary
  • "Git-based"
  • "API-based"
• Right dropdown is for sorting:
  • "Sort by GitHub stars" - default, projects without a GitHub repo are alphabetized at end of list
  • "Sort by GitHub forks" - projects without a GitHub repo are alphabetized at end of list
  • "Sort by GitHub issues" - projects without a GitHub repo are alphabetized at end of list
  • "Sort by Twitter followers" - projects without a Twitter account are alphabetized at end of list
• Additional info on cards:
  • GitHub repo link
  • GitHub stars count
  • GitHub forks count
  • GitHub issues count
  • Twitter link
  • Twitter followers count

[ChrBach]

I think left filter can be just open source (default) and All. Right filter just like staticgen: Stars (default) Forks Issues Title Agree w additional info on cards.

…

On Jan 19, 2018, at 12:26 PM, Shawn Erquhart ***@***.***> wrote: Brief requirements: Borrow concept and layout from staticgen.org (can't reuse code, that's Ruby and this is Go) Left dropdown is a filter: "View all" - default, placeholder "Open source" - filters to show only open source "Proprietary" - filters to show only propietary Right dropdown is for sorting: "Sort by GitHub stars" - default, projects without a GitHub repo are alphabetized at end of list "Sort by Twitter followers" - projects without a Twitter account are alphabetized at end of list Additional info on cards: GitHub repo link / stars count Twitter link / followers count — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[erquhart]

Hiding proprietary solutions by default sounds rough. I thought we agreed to just sort by stars and allow proprietary to show at bottom?

[yourfrienderin]

I like @erquhart 's suggestion to show open source and proprietary because it lines up with how we message and differentiate Netlify CMS.

[erquhart]

Also, if we add forks and issues as sorting options, we'll need to show the counts for both on each card as well.

[ChrBach]

They aren't hidden. It's just sorting? I think we all agree here, but maybe I'm misunderstanding

[ChrBach]

Btw, a gitbased vs api based filter / sorting would be awesome.

[erquhart]

The left side on staticgen (and proposed for headlesscms) is a filter, it hides everything that doesn't match your selection. So what I put in requirements is exactly what you're thinking - show everything by default, sorted by stars (proprietary at end of list).

Totally agree, adding Git-based and API-based to the filters makes sense for sure. Updating requirements.

[erquhart]

Just noticed that staticgen also shows the number of stars gained in the last week. This is an interesting stat that helps surface cool projects like react-static, which is lower on the list because it's new, but is actually very hot right now.

I'm thinking staticgen and headlesscms should both have "sort by stars total" and "sort by trending" (which is really just stars in last week).

[tech4him1]

What about some general "popularity" sort as well, that uses the highest number from each (GH stars, Twitter, etc.)?

[erquhart]

That makes sense, we'd just need to figure out the logic behind it, e.g. how to determine what's more popular, 4k stars or 4k followers?