Hmmm...<br><br>Is there anything better?<br><br>If codebase is a problem, in that say, it's technically wrong, then perhaps 'where drupal is installed' is just as good.<br><br>I've never heard installation tree, and it's not really tree like in structure, since it suggests that the baby sites branch off the main site, whereas in reality, they often have nothing to do with each other.
<br><br>An image problem?<br><br>Anisa.<br>starting to understand the code is gold proverb...<br><br><div><span class="gmail_quote">On 10/12/06, <b class="gmail_sendername">Gary Feldman</b> <<a href="mailto:dpal_gaf_doc@marsdome.com">
dpal_gaf_doc@marsdome.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Anisa wrote:<br>> Now that I have my own multisite (yay!), I started working on those
<br>> multi site docs again. My rough drafts are here:<br>Getting back to the "codebase" question, my preference is "installation<br>tree." It's a concrete reference to the directory tree where Drupal is
<br>installed.<br><br>The term "code base" connotes, in my mind, the original source code at<br>the <a href="http://Drupal.org">Drupal.org</a> site. It's a more abstract term, so that one might say<br>"CivicSpace is built on the Drupal code base." See the Wikipedia entry
<br>(<a href="http://en.wikipedia.org/wiki/Codebase">http://en.wikipedia.org/wiki/Codebase</a>) for another example (and no, I<br>didn't submit the Wikipedia entry).<br><br>Gary<br><br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/">
http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/">http://lists.drupal.org/pipermail/documentation/</a><br></blockquote></div><br><br clear="all">
<br>-- <br>*********************************<br><a href="http://www.AnimeCards.Org">www.AnimeCards.Org</a><br><br>16,000 scans and counting!<br>*********************************