Publish as 'flat' HTML from EPiServer site

Vote:
 
We have a rather strange requirement from a prospective customer as follows: The customer absolutely doesn't want database access involved in a live site - site must consist of 'flat' HTML only, due to concerns over performance. We were thinking of intercepting Page Publish events within an EPiServer 'authoring' site, and identifying both this page, and any pages that reference it, and any pages that reference those pages etc. This would give us a list of changed pages, that we could periodically use to generate flat HTML files to be uploaded to the live site. Does this approach seem workable? Has anyone else done anything like this? Mark Bagnall
#12215
Mar 25, 2008 18:34
Vote:
 
We have had this requirement recently in New Zealand with EPiServer and in the past when working with Microsoft CMS (the 2001 version used to provide the ability to stage a static site as a standard feature). Our standard approach now is to recommend using a 3rd party tool such as Offline Explorer to crawl the site and create a static version. These tools can be automated to create scheduled versions of the dynamic site, or you can use publishing events to fire the process off. This is useful for archiving, super security conscious sites, or clients with no internet access who want to put the site on a CD (like people on ships in the middle of an ocean). Main thing is to know this upfront and ensure you build the site interface so it can be easily sucked by the tool, so go easy on the fancy JavaScript and flash stuff.
#13852
Mar 25, 2008 18:43
Vote:
 
The 4.50 release will contain a feature called content mirroring (or staging) that will include the option to export pages to html. You can read more about it on the following page: http://www.episerver.com/templates/PageWithRightListing____3168.aspx
#13853
Mar 25, 2008 18:43