Creating an additional site using data from original
My company has used Umbraco on 2 large sites now and have found it to be a very flexible cms product.
We are currently working on a reasonably large project. Our client company has requested a second "sister" site which should make use of the same products as the main site, however some structure and design will differ on the new site. We are looking to somehow transfer product information from the master site to the second one - transferring data from the sql server database to the new database in some form of segmented replication might make sense. The question I suppose is: can the node data and templates related to that data be easily separated from other data in the database?
The sister website has the same products as the main site but the company doesn't want to maintain two administrative sections to edit the products.
Is there a way that we can use some section of the content for the both the websites?
Not coming from a c# background, here's a stab at this problem using only what is available out of the box with umbraco.
You could have the two sites under one umbraco installation, and a 3rd top level node of "products" or similar. You could then create e.g. a category page on one of the sites and use a picker to select the correct category from your product tree. This would allow for sharing data between two sites with different content structures and design, whilst maintaining only one instance of a "catalogue". Your content tree would look something like the following
WidgetsRUs.com
- page - page - products
Widgets4U.com
- page - page - products
PRODUCTS
- category - category - category
Of course, editors given access to only "widgets4U" would be unable to edit the products, and vice versa. So there'd need to be some trust and responsibility on the part of the editors/admins.
Cheers for the detailed reply. The main site is pretty much there now so they are reticent to alter the node structure in any appreciable way (which has caused various headaches recently!). I think this solution would definitely be a good one if we were not constrained so much. I will put in a reply to say what we finally end up doing for this!
Creating an additional site using data from original
My company has used Umbraco on 2 large sites now and have found it to be a very flexible cms product.
We are currently working on a reasonably large project. Our client company has requested a second "sister" site which should make use of the same products as the main site, however some structure and design will differ on the new site. We are looking to somehow transfer product information from the master site to the second one - transferring data from the sql server database to the new database in some form of segmented replication might make sense. The question I suppose is: can the node data and templates related to that data be easily separated from other data in the database?
The sister website has the same products as the main site but the company doesn't want to maintain two administrative sections to edit the products.
Is there a way that we can use some section of the content for the both the websites?
Any help would be greatly appreciated!
Not coming from a c# background, here's a stab at this problem using only what is available out of the box with umbraco.
You could have the two sites under one umbraco installation, and a 3rd top level node of "products" or similar. You could then create e.g. a category page on one of the sites and use a picker to select the correct category from your product tree. This would allow for sharing data between two sites with different content structures and design, whilst maintaining only one instance of a "catalogue". Your content tree would look something like the following
Of course, editors given access to only "widgets4U" would be unable to edit the products, and vice versa. So there'd need to be some trust and responsibility on the part of the editors/admins.
is this close to what you had in mind?
Dan
I like Dan's idea... def the way I would go on a clean build.
As you already have a site, you might want to think about just re-skinning the site based on the incoming domain name.
There was a discussion on this forum about changing the masterpage programatically. I think you have to extend the default.aspx to acheive this.
Chris
Hi Dan,
Cheers for the detailed reply. The main site is pretty much there now so they are reticent to alter the node structure in any appreciable way (which has caused various headaches recently!). I think this solution would definitely be a good one if we were not constrained so much. I will put in a reply to say what we finally end up doing for this!
Mike
is working on a reply...