categories

tj opened this issue 12 years ago · 8 comments

tj commented 12 years ago

from the wiki, some inspiration:

http://www.unheap.com/section/inputs-forms/input-sliders/

having images like that would be cool but we would have tons of unpopulated ones

wilmoore commented 12 years ago

👍

Answer 1 · 2013-03-10T23:29:26.000Z

That looks sexy.

So were doing sub-categories? How deep should we allow to nest? 2 levels?
Who will put the component into its respective category? The dev itself or a group of curators?
How is it going to be categorized (tech-wise)?

I propose a new key for the component.json.

{
  "name": "mah-component",
  "description": "Quite cool stuff in here",
  "keywords": ["ui", "form", "slider", "animated", "funky-stuff"],
  "category": "ui/forms/sliders"
}

When the category UI->Forms->Sliders does not exist, the bot could create an issue informing the dev about that.

Answer 2 · 2013-03-10T23:37:12.000Z

Do we want categories or do we want granular keyword navigation (i.e. facets). Kinda wish npm did this actually. Full text search on name and description, then fielded/faceted navigation on keywords. component.json has all the terms we need to make this useful.

Answer 3 · 2013-03-10T23:50:28.000Z

The other nice attribute of facets is that it can be used to do research to find under-served keywords. That isn't always the only type of research you want to do, but it can be helpful to some audiences.

Answer 4 · 2013-03-11T17:12:52.000Z

we have full-text already, I think that's fine personally, I just want to scrape the wiki categories for the site

Answer 5 · 2013-03-11T18:47:56.000Z

we have full-text already

Sounds good. I take it the keywords are also getting indexed then?

I just want to scrape the wiki categories for the site

Fair enough...that should work.

Answer 6 · 2013-03-11T18:57:55.000Z

yup keywords, the component name itself and descriptions

Answer 7 · 2014-04-07T01:11:00.000Z

meh, people should be using keywords instead