I had done that, with
Root -home -homeCry -homeCryDev
Without changing anything else, assuming that I could view the default farcry (home) after an app refresh. The site ended up just outputting the DOCTYPE header, and nothing after that. If I used Preview from the admin, it went as far as to apply CSS and part of 'containerhead' depending on the node (homeCry, HomeCryDev have cascading styles), but failed to get to the HTML object. Perhaps I had a done something else bad? I'll try again!
I am working on something similar (a site planned to be released in a couple weeks). This client wanted different locations (each has their own site and stylesheets, but a lot of dynamic information is shared amongst the iste like News & Events).
I did mine like: home basic.css Advanced.css Print.css -Location1_homepage homepage.css (not used on any descendents) location1Colors.css -Location2_homepage homepage.css (not used on any descendents) location1Colors.css -Location3_homepage etc...
Then when I have shared static content (say Privacy Policy in the footer) I make that page in root-utility (and give it an alias) and I place all of the static content in there. To navigate to this new page I make a "Privacy Policy" navigation node somewhere under my location_home (for each site) and use a symbolic link to point to the alias in the utility-Privacy Policy.
In the end I have one content spot for the shared static content and I get the page to think it still resides in the site I came from (thus keeping stylesheets etc).
By the way. In order to know which site I am under I created a CFC that gets info like my site's homepage alias name and more. I'd share it, but its likely too customized.
-Jeff C.
--- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
