I have a client with 30+ organization units that operate independently. Currently all the OUs have websites managed by the client's IT department in seperate instances of a different CMS product. They decided to go with Sitecore because of its advertised multi-site features.
Unfortunately, the current (6.5/6.6) default implementation does not work for the following reasons:
/sitecore e.g. /sitecore/OU1, /sitecore/OU2, etc.../sitecore/Templates. We would prefer to create "Templates" folders under each organization unit e.g. /sitecore/OU1/Templates, /sitecore/OU2/Templates, etc.../sitecore/Layouts/ and also in the same file system directory. This definitely gets messy as the sites increase in number. /sitecore/OU1/Layouts/ and /sitecore/OU2/Layouts are definitely preferableAt the recent Sitecore Symposium, Tim Ward presented on the different ways to implement multiple sites in Sitecore. Unfortunately, there is no way of knowing which products he is referring to. I wasn't there, but my boss attended. I have tried to get in touch with Sitecore, but haven't received a response yet.
I also contacted Sitecore requesting information on whether Sitecore Foundry is meant to address this need, but no response.
Anyone know of a way to implement such multiple sites Sitecore?
Sounds like Tim's multi-site solution is indeed something for you. It's meant for large scale multi-site platforms that require isolation and need to be fit for independent vendors developing for it.
Sitecore Foundry is not for you, it's meant for much smaller type of websites and does not offer any kind of isolation.
Tim's solution can be found here at github (which you probably already got from the slides):
You can e-mail him at [email protected] and he's usually pretty quick to reply.
He's also active on the SDN forums, assuming your have access to that.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With