Learn from 350 other Umbracians at the annual Umbraco Conference - CodeGarden '13.
More than twenty high quality sessions, open spaces, hackathons and social events you'll remember. Not to be missed! Less than 25 tickets left - get yours now!
This place has been bombarded with packages which is apsolutely fantastic, but how should we move forward in categorizing these items?
My suggestion is that site admins move the packages into the proper categories after they get created. This way we know items will be placed correctly and in case we decided to create sub categories we can easy move items around without involving the package authors.
This ofcourse will result in changing urls for the different packages, but as brilliantly suggested by warren buckley, we could allow package authors to have vanity urls for their packages. So instead of: /packages/wesite-starterkits/Creative-Website-Wizard-By-Warren-Buckley , it could be /packages/cws
Per, we had a discussion at cg09 around the three repositories (our.umbraco, store and traditional package repository) and I do believe that Tim G was actioned to come up with some categories that would be used across all three to maintain consistency...
Breaking it down into a structure of categories would be ok. Allowing project owners to tag their projects would imo be better and more along with the nature of the site. Tag cloud could filter out noicy tags (tags used less than x times).
I also think there's a need to be able to browse/filter packages on the following properties:- Umbraco version:- NET Framework:- Other requirements: (like runway)- Stable: beta/production?- Type of project (package)- Is docs avail- Can be installed by: webmaster, developer, ...
I can easily imagine clicking on "starter webs" and then filter for Umbraco version and stable=production.
I think a mixture of the above will work perfectly.
1. our.umbraco.org site admins create main categories and move the packages into the categories2. Add some more meta data fields to a project, such as Jesper's suggestions3. Vanity URLs such as cws.packages.umbraco.org or whatever domain/format
With these combined I think it will work great.