1-888-365-2779
+1-888-365-2779
Try Now
More in this section

Forums / Developing with Sitefinity / Branding - Inheriting from an exisiting site

Branding - Inheriting from an exisiting site

2 posts, 0 answered
  1. Arthur
    Arthur avatar
    1 posts
    Registered:
    16 Jun 2009
    16 Jun 2009
    Link to this post
    Hi,

    First of all let me say that I am fairly new to sitefinity and my first opinion is that I am very impressed about the easy of use and extensibility of the system.

    The company I am currently working for is considering the use of Sitefinity as one of the building blocks of their web applications, and I am trying to find out whether the functionality the current CMS offers is portable to Sitefinity.

    The company creates websites for customers that in most cases want to present the web application to more then one of their own customers, so some customization is required.

    Basicly what we want is create a site for brand A, and create a "subsite" for brand B, with as little configuration as possible, so some "inheritance" would be nice here. Customization should be done for:
    • Style issues (themes)
    • Menus (Brand B might require one or more additional pages or might not want all pages required by A)
    • Pages / UserControls: disclaimers will have another text, and some other columns might by required in the usercontrols, so the "same page" might be showing another usercontrol.

    The "B" site will be on the same server as the "A" site, and will use the same backoffice application, and there can be up to 8 different brands for an application.

    What would you recommend us in order to keep this maintainable (subsites, site templates, ...?)

    Thank you very much in advance for your advice.

    Kind Regards,

    Arthur Dikken
  2. Georgi
    Georgi avatar
    3583 posts
    Registered:
    28 Oct 2016
    22 Jun 2009
    Link to this post
    Hi Arthur,

    I spent some time thinking about different approaches in your scenario, but I did not reach to a certain one. Basically everything that should be reused should be in form of:
    • User Controls
    • Masterpages
    • Site Template - there is an option the backend, to export the current web site as a template for another web site.
    Perhaps you can use the last approach. When you create site A, you can export the whole thing as a template for another web site, but the cons is that the second web site will be separated then the first one (which means it will have its own back-end as well).

    You might organize the first web site in a page group. Then, there is a API method which allows you to copy page trees within the same web site. Let's say you have a page group A, and you want to add a micro site for brand B - then you copy the page group a in a different location in the sitemap, then quickly change the images, the text, possibly remove some pages and you are done. As for the front end, you might create different UrlRewriteRules in order to resolve the group pages from the exact URLs that you want.

    Note that if you place a user control on the masterpage, you cannot edit it directly from the page editor. That is why, I guess, you should move everything to the User Controls and add them to the pages later.

    I hope you find this helpful. Please follow up if you are wondering on something.
    Best wishes,
    Georgi
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
2 posts, 0 answered