I’m designing the new web site using Umbraco 4.5 and I have
an issue that I am unsure how best to handle.The situation is this, my client has 47 web site for various regions
around the world. There will be a global site in which the client would
like to create content such as new releases, about us pages and photo
galleries, etc., then select any number of the other 46 sites on which they
would like to share this content. The content would then appear as
navigation items and content pages in the selected web sites.
Originally I was planning to create all 47 sites in a single
Umbraco instance. Each site would have a maximum or 300 content nodes, so
that’s 14100 content nodes in a single Umbraco instance. I did some
research and through an Umbraco forum post I learned that Umbraco can handle
hundreds of thousands of content nodes. The biggest limitation is the
node structure on the back end. Obviously having all nodes off the root
would be bad, but containing them in site folders should be ok.However, I later learned that hosting 47
sites in an Umbraco instance is a horrible idea, So now I’m back to hosting a
number of Umbraco instances each containing 10 – 15 Umbraco sites.
So the core issue is how can I easily share content from the
global site on the region sites, while maintain the region navigation and look
and feel within the shared content. I know that I can save content after
publishing to an external database, and that is my best approach at the moment.However this would also involve custom navigation
macros and content display macros which I would like to avoid.I’m trying to keep this as simple as possible
while allowing the client to share content.
So , I’m back to thinking that the best way to accomplish
this is to create a single instance of Umbraco to host all 47 site, then create
new content nodes in the appropriate sites as the shared content is
published. Unfortunately, Hosting 47 sites under one Umbraco
instance is probably not such a good idea, but I’m out of ideas.
I would love to hear any thought that you might have.
Input and suggestions are welcome and appreciated.
You might be able to used Courier to do this. I think that Courier can be used to migrate content to multiple websites (I think I saw that in the Courier config).
This would allow you to have a "global resources" umbraco instance which is only used to push the global data around. Then for the different sites you'd break down the sites into only 1 (or a small number) of sites within the one CMS instance.
If Courier can't achieve that I'd then build a custom web service set to achieve that.
Sharing content across multiple Umbraco instances
Hello everyone,
I’m designing the new web site using Umbraco 4.5 and I have an issue that I am unsure how best to handle. The situation is this, my client has 47 web site for various regions around the world. There will be a global site in which the client would like to create content such as new releases, about us pages and photo galleries, etc., then select any number of the other 46 sites on which they would like to share this content. The content would then appear as navigation items and content pages in the selected web sites.
Originally I was planning to create all 47 sites in a single Umbraco instance. Each site would have a maximum or 300 content nodes, so that’s 14100 content nodes in a single Umbraco instance. I did some research and through an Umbraco forum post I learned that Umbraco can handle hundreds of thousands of content nodes. The biggest limitation is the node structure on the back end. Obviously having all nodes off the root would be bad, but containing them in site folders should be ok. However, I later learned that hosting 47 sites in an Umbraco instance is a horrible idea, So now I’m back to hosting a number of Umbraco instances each containing 10 – 15 Umbraco sites.
So the core issue is how can I easily share content from the global site on the region sites, while maintain the region navigation and look and feel within the shared content. I know that I can save content after publishing to an external database, and that is my best approach at the moment. However this would also involve custom navigation macros and content display macros which I would like to avoid. I’m trying to keep this as simple as possible while allowing the client to share content.
So , I’m back to thinking that the best way to accomplish this is to create a single instance of Umbraco to host all 47 site, then create new content nodes in the appropriate sites as the shared content is published. Unfortunately, Hosting 47 sites under one Umbraco instance is probably not such a good idea, but I’m out of ideas.
I would love to hear any thought that you might have. Input and suggestions are welcome and appreciated.
Thanks
You might be able to used Courier to do this. I think that Courier can be used to migrate content to multiple websites (I think I saw that in the Courier config).
This would allow you to have a "global resources" umbraco instance which is only used to push the global data around. Then for the different sites you'd break down the sites into only 1 (or a small number) of sites within the one CMS instance.
If Courier can't achieve that I'd then build a custom web service set to achieve that.
I assume the Courier solution would result in duplicated content stored in regional websites with it being managed centrally?
I would also be interested in hearing from people who have actually achieved something like this and how they approached the problem!
What method did you go for in the end Greg?
is working on a reply...