3 ms·
Couple of suggestions: * Add categories (by language, software integration, accessibility, whatever) * Add links to the package website and/or Github url * Add
by Jemaclus 13y ago
Couple of suggestions:
* Add categories (by language, software integration, accessibility, whatever)
* Add links to the package website and/or Github url
* Add screenshots for every package, especially themes. Nothing worse than clicking on "Uber Theme VIII" only to see that it says "Here's a new theme called Uber Theme VIII" but I'd have to install it to find out what it looks like. No thanks.
- stphnclysmth 13y agoThere's a small link to the repository in the meta line below each project description, next to the last modified date. It's hard to find. I was coming here to suggest that on package detail pages, the package name should link to the project repository, and not recursively to the detail page. That was my instinctual expectation.
- 0k1n 13y agohey, site author here I'm planning to add these features in the upcoming days/weeks: - load package infos from other sources than github - st 2/3 version compatibility - supported platform - faceted search right now the website is as minimal as possible, I wanted to ship something as quickly as possible to have the fastest possible feedback. I wasn't expecting someone to post on HN though — nor my poor ec2 micro instance did ;) > links to the package website and/or Github url It's always there :) > Add screenshots for every package, especially themes Lots of theme developers already put theme in their README, though I agree some don't and it's painful. I'll see what I can do.