Hi:
After using Drupal 5, different installs for different sites, got one site in Drupal 6, plan to shift others, and aim for multi-site use.
To me, and maybe others, it's a bit odd having "modules" among various Drupal files and folders, and "modules" in folder for all or individual sites.
Yes, must read info, and clear once you know, but I think fresh naming might help, and help encourage people to use folders as intended (in Drupal 5, I was simply adding modules to main modules folder).
Maybe, then,
coremodules and modules [xtramodules?]
corethemes and themes [xtrrathemes]
- albeit I guess won't work for versions to D6, but possible from 7 onwards? (Naybe already done and dusted for this; maybe too complex given all the calls to modules and themes)
Also, for contributed modules like fckeditor, tinymce, it's odd to have both Drupal module and software package with same name.
Here, maybe oould ask module developers to name their modules something else, like
fckeditormodule
tinymcemodule
- or whatever. Guessing, that is, this would work ok.
Might also help a bit should someone just download module and expect it to work as is, without the extra software package.
Comments
modules in modules and modules in sites/*/modules
As folder name "modules" maybe important, can instead run check when listing modules; if find contributed modules in core modules modules folder, can have a note re contrib modules saying that best not to have them with core modules, best to put within sites. (GIve a few reasons, too.)
____________________________
CheungChauHK 長洲HK - South China Sea island in Hong Kong.
____________________________
DocMartin and Hong Kong Outdoors