However, I see the following room for improvement (incomplete):1) As an anonymous coming from zikula.org user the overview of modules and themes has a very short description and no images. This isn't really appealing. Coming from community.zikula.org there's more info and it loos much nicer. This seems more an issue with the main site I guess, the main site should use another link?
2) The search-button on the "ctmain"-page (landing from zikula.org) leads to the general ZK-search while one would expect it to lead to the search for extensions.
3) On both pages there's a general search-field and a search-button, which is confusing. I have'nt figured out what would be the best use here. I guess the general search-field should default to the extdb when viewing extdb-pages and in the extended search one could point to other parts of the site. The same holds for other pages, they should default to the general site with extended search having an option to search in extdb.
4) From the overview-page it should be possible to download an extension directly or to put it in a download-pack directly. Now one has to click a lot to get an extension, then go back to the starting point, search once more etc etc. Also, putting an extension in a download-pack should be done with an Ajax-call for easy browsing.
5) In an overview of an extension (ie Multihook) it looks like the extension isn't supported for ZK1.2.1 and ZK1.2.2. Yesterday someone pointed out this means these versions of ZK aren't supported. This should definitely be changed IMHO. In general a module which works in 1.2.1 should also work in 1.2.8, shouldn't it (that's the meaning of maintainance-releases)? If this is not the case, the "not supported" should be dropped here, for every maintainance-release it should be noted if the module works or not. I know this asks extra input from the maintainers, I guess there should be three options per offical version (yes, no, probably) with a default to "probably" whenever a new version of core is released.
6) It should be possible to limit searches to certain versions of core. Also, it should be possible to give an overview of modules, themes, plugins etc limited by version of core. Now there's a sorting option "targetgroup" which IMHO can be dropped. This limitation should default to 1.2.8, the stable-release for now. In the overview for 1.2.8 all extensions which have a "yes" of "probably" for the supported version should be shown.
7) When landing on the default-pages for modules, theme's, block's and plugin's, there should be one of two lines of descriptive text.
8) On the main ext-db page something is said about legacy-components being in an old database. Which database? If (5) and/or (6) have been included, old extensions can be included in the extdb without getting things confused.
Edited by bvdbos3 on Oct 22, 2011 - 07:28 PM.
