Hi Anthony and Mark,
@Anthony: We haven't recorded our this demo, unfortunately.
@Both: There are plenty of options to achieve, what Jeff described in his post. For instance you can use different Sitefinity projects for the different regions. Let's imagine we have one Sitefinity license with the registered top-level domain: domain.com
and 2 different regions and want each of those to run on a separate Sitefinity application. In this case www.domain.com could resolve our homepage, region1.domain.com and region2.domain.com could resolve the homepages of the respective region. Needless to say that you can redirect www.region1.com to region1.domain.com afterwards.
Another option could be, that we want all region homepages to run on a single Sitefinity application, but the different sub domains should resolve different homepages. In this case we could create different nodes in the sitemap of Sitefinity and use the PagesConfig.config file to specify the homepage for each sub domain. There is a workaround in IIS for this purpose. We could create, for instance, 3 different Web Sites in IIS (let's say Home, Region1, Region2) pointing to the same Sitefinity application. The only difference is the PagesConfig.config file of the three IIS Websites, where the home page is set.
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items