consider other mechanisms of categorization

[Stefan Penner]

these are just ideas for discussion

• project of the week (featured project)
• projects by problem they solve (we can define additional meta data such as "component" "mixin")
• ... ?

[Giovanni Collazo]

@jpadilla @stefanpenner

At the moment we are saving all the information the user enters in package.json under the emberAddon key. We could use this for anything specific to the emberaddons.com site including categorization.

// package.json
"emberAddon": {
  "categories": ["mixin", "adapter", "serializer", "component", "helper"]
}

Having this data for most of the packages we could make a "Browse" page similar to what pypi has.

If we agree that this is the best mechanism for categorization I will go ahead and open PRs on as many published modules as I can to add this metadata and get the ball rolling.

[Giovanni Collazo]

emberobserver.com solves this