<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Jun 24, 2006, at 4:11 PM, Anisa wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><A href="http://drupal.org/node/43816">http://drupal.org/node/43816</A><BR> <BR>...<BR></BLOCKQUOTE><BR><BLOCKQUOTE type="cite"> So, some possibilities:<BR> 1. Same codebase, completely different content and users<BR> 2. Same codebase, different content, same users<BR> 3. Same code base, same configuration, different content, same users<BR clear="all"><BR> Each configuration should cover:<BR> settings.php<BR> database prefixes<BR> and whatever else changes, though I can't think of what.<BR></BLOCKQUOTE><BR></DIV><DIV>I'll help when I get a better grasp of this. I'm about to embark on a large-ish project that could go multisite or og. I'm leaning towards multisite because then each sub-site is more unique and distinct. I'm leaning towards og because we need to have a unified user base and content that can cross to the "main" site.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I figure I'm going to have to just dive in and make a mess to find out. But it will be either scenario 2 or 3 from the list above, plus different admins (i.e., different user roles for each site).</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Option 3 is that I will do a single sign on solution and just put together over a dozen sites with shared modules but separate databases.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Either way, it will make for an interesting case study and food for enriching the handbooks by topic.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Laura</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>