I think a tag system instead of a directory system may be better for categorizing libraries. For example, is D3 is "data / undefined". Arguably it could exist in multiple categories.
This is probably the hardest problem to solve in building a tool like this. Ive thought a lot about this, and here is my thinking:
Its not an either-or scenario. Tags are great at grouping similar libraries together, but it doesn't work very well when you look at all the tags together, since there is no clear hierarchy.
Categories are good, on the other hand, for creating a clear structure for looking for libraries. If a user is confused about where to find something specific, they can just search it.
My plan is to combine the two approaches in jsdb: have a clear and very general category system, and a tag system for finding inter-related js libraries.
Its not an either-or scenario. Tags are great at grouping similar libraries together, but it doesn't work very well when you look at all the tags together, since there is no clear hierarchy.
Categories are good, on the other hand, for creating a clear structure for looking for libraries. If a user is confused about where to find something specific, they can just search it.
My plan is to combine the two approaches in jsdb: have a clear and very general category system, and a tag system for finding inter-related js libraries.