What project details would you like to see for each item on the list?
It's tough because :
1. There is a lack in uniformity: you have CSS solutions, jQuery extensions, node.js packages, articles, books, videos and so on.
2. Every bit of information you include makes the list bloated. I think it's enough to have the category, a link, and maybe a short description. If I need a template engine for a project, I will click on every link and look through them anyway.
Please make a suggestion how you would like this list to look.
Lists are useful because sometimes you don't know what to google, especially if you hadn't really noticed a problem enough to think that someone else might have already solved it for you.
If I have a specific task the workflow for me looks like that: 1. Search through Google, Github, Unheap, npm, bower, jster and so on. 2. Compile a list of useful packages and tutorials for every one of them. 3. Select the best package for the task.
So I created this list to not have to go through step #1 and #2 every time.
The benefit here is that most of these are at least somewhat usable in a project. Many of the resources that one finds online are not great. I found several things that I wish I had used on past projects.
Comments
The list is too massive and lacks projects' details to be useful.
I'd better use github's search.
What project details would you like to see for each item on the list?
It's tough because : 1. There is a lack in uniformity: you have CSS solutions, jQuery extensions, node.js packages, articles, books, videos and so on. 2. Every bit of information you include makes the list bloated. I think it's enough to have the category, a link, and maybe a short description. If I need a template engine for a project, I will click on every link and look through them anyway.
Please make a suggestion how you would like this list to look.
Agreed. There are way too many items on the list. This way, it is barely anymore useful than a google search for these tools.
Lists are useful because sometimes you don't know what to google, especially if you hadn't really noticed a problem enough to think that someone else might have already solved it for you.
If I have a specific task the workflow for me looks like that: 1. Search through Google, Github, Unheap, npm, bower, jster and so on. 2. Compile a list of useful packages and tutorials for every one of them. 3. Select the best package for the task.
So I created this list to not have to go through step #1 and #2 every time.
The benefit here is that most of these are at least somewhat usable in a project. Many of the resources that one finds online are not great. I found several things that I wish I had used on past projects.