I would agree. It&#39;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&#39;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">twitter.com/adamgregory</a><br>Skype: aagregory2<br>Cell: 706.761.7375<br>
<br><br><div class="gmail_quote">On Thu, Nov 19, 2009 at 9:40 AM, Josh Miller <span dir="ltr">&lt;<a href="mailto:JoshM@haanmc.com">JoshM@haanmc.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">










<div link="blue" vlink="purple" lang="EN-US">

<div>

<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Charbel,<br>
<br>
As I recall from over a year ago, my first two Drupal sites had custom and
contrib modules in the /modules/ folder. Then I had to upgrade and it was very
painful. I&#39;m sure there are other devs out there that have similar stories. My
point is that we shouldn&#39;t *<b>have</b>* to document, it should be *<b>very
apparent</b>* where things go.<br>
<br>
On a side note, this is definitely a D8 discussion.<br>
<br>
Josh</span></p>

<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>

<div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">

<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:development-bounces@drupal.org" target="_blank">development-bounces@drupal.org</a>
[mailto:<a href="mailto:development-bounces@drupal.org" target="_blank">development-bounces@drupal.org</a>] <b>On Behalf Of </b>Charbel Khadra<br>
<b>Sent:</b> Thursday, November 19, 2009 9:45 AM<br>
<b>To:</b> <a href="mailto:development@drupal.org" target="_blank">development@drupal.org</a><br>
<b>Subject:</b> Re: [development] Drupal Folder Structure</span></p>

</div><div><div></div><div class="h5">

<p class="MsoNormal"> </p>

<div>

<p class="MsoNormal" style="margin-bottom: 12pt;">i don&#39;t see what you are
posting is a major issue.<br>
any user who is going to deploy drupal application should a have a minimum
technical level to be able to read the basic insatallation step of a module<br>
<br clear="all">
<br>
Charbel Khadra<br>
<a href="mailto:charbel@ebizproduction.com" target="_blank">charbel@ebizproduction.com</a><br>
<a href="http://www.ebizproduction.com" target="_blank">www.ebizproduction.com</a><br>
<br>
</p>

<div>

<p class="MsoNormal">On Thu, Nov 19, 2009 at 4:40 PM, Ken Winters &lt;<a href="mailto:kwinters@coalmarch.com" target="_blank">kwinters@coalmarch.com</a>&gt; wrote:</p>

<div>

<p class="MsoNormal"> </p>

<div>

<div>

<p class="MsoNormal">On Nov 19, 2009, at 9:15 AM, Josh Miller wrote:</p>

</div>

<p class="MsoNormal"><br>
<br>
</p>

<div>

<div>

<div>

<p class="MsoNormal" style="margin-bottom: 12pt;"><span style="font-size: 11pt; color: black;">Is there anyone else worried
that the Drupal folder structure encourages users to drop modules or themes
into the wrong place? Wouldn&#39;t you like to have a folder structure that
separates core from the rest of the customizable sites folder?<br>
<br>
As this issue could blow up in the issue que (<a href="http://drupal.org/node/22336" target="_blank">http://drupal.org/node/22336</a>)
perhaps a short discourse on the mailing list is in order. It&#39;s weird that we
all care so much about coding standards and yet we let our folder structure look
so thrown together.<br>
<br>
Perhaps I&#39;m wrong. I have feeling the real reason we are putting up with such a
confusing structure is that moving files can introduce a big wtf and some might
think we should leave it well enough alone. On the other hand, I believe it&#39;s
broken and not at all grokable for 100% of the newbies.</span></p>

</div>

</div>

</div>

</div>

<p class="MsoNormal"> </p>

<div>

<p class="MsoNormal">I&#39;m all for moving the core modules into /core/modules,
themes into /core/themes (or anything equivalent) in D8.  It seems way too
late for D7.</p>

</div>

<div>

<p class="MsoNormal"> </p>

</div>

<div>

<p class="MsoNormal">What we could do in the immediate is put a text file
DONTTOUCH.txt or whatever in those folders, with instructions on what users
should actually be doing.</p>

</div>

<div>

<p class="MsoNormal"> </p>

</div>

<div>

<p class="MsoNormal">On a related note, some modules encourage users to place
custom code or plugin modules into [module folder]/modules, </p>

</div>

<div>

<p class="MsoNormal">which is bad because they can easily be deleted when the
main module is updated.  I think we should discourage this.</p>

</div>

<div>

<p class="MsoNormal"> </p>

</div>

<div>

<p class="MsoNormal"><span style="color: rgb(136, 136, 136);">- Ken Winters</span></p>

</div>

</div>

</div>

<p class="MsoNormal"> </p>

</div>

</div></div></div>

</div>


</blockquote></div><br>