Domain Access vs. Multi-Site vs. Sections -- Secondary Sites using Directories rather than Subdomains
I've got what seems to be a unique situation (based on searching the site for the past day or so) and am hoping someone can point me in the right direction.
I'm setting up websites for an organization that will have an umbrella site at site.org, and needs two additional sites at site.org/site2 and site.org/site3. We don't have the option of creating subdomains. These separate sites need unique themes and content, but would ideally share content types and users.
I was planning to use a multi-site install with prefix-based user table sharing, but found several posts that seemed to indicate this was not advisable behavior (the phrase "you're on your own" was mentioned I think). Since all sites would be on the same domain, this would effectively create SingleSignOn behavior.
Now that I've read more about Domain Access, I like the idea of being able to share specific content across all three sites while still keeping certain pieces unique, but it doesn't look like DA allows the use of subdirectories rather than subdomains to differentiate between sites.
Can anyone suggest the cleanest method to minimize redundancy across the three sites while maintaining the system's integrity? I'll be leaving this project in the hands of a PHP novice and don't want things to break in the future because I used incorrect methods.

Not so hard
If the requirement is path-based theme switching, that is not at all difficult, and can be coded in an afternoon.
_
iirc, there's also a module or two that can do this as well.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Not quite the whole picture.
As I said above, the content of the three sites needs to be kept separate. Thus, path-based switching is only a part of the equation. There also has to be a way to ensure that only the content for a particular site/theme combination is seen in that site/theme. Preferably, there would be an easy way to indicate when creating new content which area it belonged to.
I'm open to the idea of using site.org/site1, site.org/site2, and site.org/site3 as the addresses, and using the site# pattern to regulate the theme display, but there's got to be a way to ensure that site.org/node/# can't be viewed with a default theme and preferably not viewed at all due to the ambiguity the node term would introduce to an observant user. The branding for these sites has to stay distinct.
_
You could probably do this with a single site and some access control. You can use the http://drupal.org/project/themekey or http://drupal.org/project/sections modules to control the theming, http://drupal.org/project/tac_lite or http://drupal.org/project/taxonomy_access for the access control (setup a "site" vocabulary with terms for "site1" and "site2"), and pathauto to set up the site.org/site2 and site.org/site3 path convention.
For some documentation on how to do this see Controlling Access to Content by Configuring Groups as Roles (it's for d5, but the concepts are the same). Substitute the word "site" for "groups" and it pretty describes what you're trying to do.
Another option might be the http://drupal.org/project/og module also.
_
Don't be a Help Vampire - read and abide the forum guidelines.
If you find my assistance useful, please pay it forward to your fellow drupalers.
Thanks.
I just discovered the taxonomy access idea a few minutes ago and it looks promising. Glad to know I'm on the right track.
Thanks!
Is there a way to have just
Is there a way to have just one domain address (www.example.com) and multisites in Drupal (hosted on my local) but redirecting to each site with www.example.com/site1 , www.example.com/site2 ?
I've got it running by changing the port in the url www.example.com:800, www.example.com:900 and sites folders called 800.www.example.com, 900.www.example.com, so that's not a 'clean' solution.
Single site with access control is not a solution for now because my sites have same modules but are for different clients.
Thank you