Just a heads up for anyone interested. I've been working on a very significant revamp of the Package Control site that coincides with all of my work on Package Control 2.0. I've been pushing hard the past couple of weeks, with a hopeful launch in the next couple of days.
The benefit of an online listing is easy access to package descriptions and repositories. When there are multiple packages for a given task, I'd like to know which is more heavily updated and supported. Correct me if I'm wrong, but I don't believe there's a way to open the Github page from that menu.
When I middle-click on a link, I expect it to open in a new tab. When browsing lists of things I tend to scroll through the list and open a bunch of tabs, then peruse them at my leisure later on, and I can't do that on your site.
* 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.
There'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.
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.
A bit off topic, but it's better to ask here than to create another thread.
I'm teaching myself HTML, and CSS and JS (jQuery). Are there any essential Sublime Text packages that I have to install? I searched it on DDG but it wasn't very helpful (most of the articles were outdated).
Thanks for the tip on Quick File Creator. I'm a pretty heavy Sublime Text user and that just solved a pain point for me.
Another one that's useful for me in web-related work and not specific to any particular language is the Web Encoders plugin: https://github.com/revolunet/sublimetext-web-encoders -- I often use it when I need to test URL encoding/decoding stuff.
http://wbond.net/sublime_packages/community
One suggestion to bring it to at least feature parity: It is useful to display the operating systems that each package supports.