As you may have read in the past, with the release of PostNuke .8 Final, we plan to have a new downloads interface. We will use Axel's EasyDist module (see a demo here) - enabling you to build a custom package from the ground up, automatically building a compressed archive containing any modules and themes from our extensions database.
Part of this work will involve changing and expanding the extensions database to include new fields. One of these is a category field, which we will use in EasyDist's interface. We could use some help from you defining our category tree - what's the best way to categorise all the modules and themes PostNuke currently has, or might have in the future? We'd like your suggestions; a forum topic to start the discussion is here.

3 Comments so far
(Latest comments
)
1. alarconcepts wrote on Oct 31, 2007 at 04:24 PM
2. mumuri wrote on Nov 17, 2007 at 05:13 PM
If possible, will it be possible to have a "distribution" category, indeed, you ve said in a precedent post that, we will able to build an broadcast our own distribution of PostNuke.I think it could be a good idea to centralize all this distribution in one root category (in the same level as theme/module/plugins/blocks)
http://community.postnuke.com/Article2860.htm
More over, is it possible du had a "mod" category (for modification), indeed, for me , this is a mod for bbcode, not a plugin http://community.postnuke.com/module-Database-viewpub-tid-8-pid-21.htm
Thanks
I thinks the actual version
* Modules
* Themes
* Blocks
* Plugins
is a good version, there is no need to have a separation between core and 3rd Party Addons . (or only an other field in Pagesetter).
3. mumuri wrote on Dec 03, 2007 at 08:40 PM
more over, a field with the license(creative common .GPL ) could be a good idea