<div>If we move sites/all/modules to /modules people are never going to realize they can do sites/<a href="http://mysite.com/modules">mysite.com/modules</a>. Then it doesn't also fit into the standard paths for other things like sites/all/libraries and sites/all/images, etc. In all honesty people are going to not read documentation and hunt for where to install their modules. People will still find /core/modules and put contrib modules there anyway. How this is solved is via the new module install interface in D7 and being able to select modules to include when downloading from <a href="http://drupal.org">drupal.org</a> so it automatically packages things correctly.</div>
<br clear="all">Dave Reid<br><a href="mailto:dave@davereid.net">dave@davereid.net</a><br>
<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 8:59 AM, Adam Gregory <span dir="ltr"><<a href="mailto:arcaneadam@gmail.com">arcaneadam@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I would agree. It's not incredibly apparent to a new user that they need to create different modules and theme directories in the various sites folders when they install Drupal. If we are trying to advance the project to the next level then this should definitely be something we look at. I think Kens idea of creating /core/modules and /core/themes is a good idea. In addition why not just remove the sites/all folder and by default use /themes and /modules as the equivalent of /sites/all. That's more intuitive to someone who has no idea about Drupals multisite capabilities. I think that would make it easier for first time users to set up and use Drupal, which is one of our objectives for making Drupal the best CMS out there.<br clear="all">
<br>-----<br>Adam A. Gregory<br>Blog: AdamAGregory.com<br>Twitter: <a href="http://twitter.com/adamgregory" target="_blank">twitter.com/adamgregory</a><br>Skype: aagregory2<br>Cell: 706.761.7375</blockquote></div>