I've got a client who I optimistically (shortsightedly?) thought was perfect for a CMS.  However, after several years I have discovered that all desired changes on his website come through me.  That's good for me but because of the nature of some of the requests I'd like to move back to a plain html website (or aspx with masterpage to be precise).

Is there any way to minimize/automate the work involved in the this DNN to "HTML" conversion process?  The site has ~150 pages.

Have you really thought that idea thru? 

For starters - unless the site is made up of less than a couple of pages (150+ u sait) - you are going to be looking at having to create a new menu and workflow system - does your client like the menu drop downs etc?  Is there any need for login type access.

The thing that DNN brings to many sites is more than the sum of its CMS elements - its all that messy background stuff like dynamically generating menus, sitemaps, natural language urls etc.

Much of how a dnn page is rendered relies on all that background stuff - so JUST cutting and pasting html will not give you a working site.

Westa

Hi Wes/Sebastian,

I agree with your comments in general but the pages are all static and have now been that way for the past 8 years (I just looked it up).  The work involved in recreating the pages and menu system is just about the only thing stopping me from simplifying it.  I say simplifying because I do most of my work outside of DNN and so find it easier to re-use my own code if I don't have to convert it as much.

HTTrack might serve my purpose.  I'll have a look.  Thanks!

I only wondered if anyone else had looked at going backwards from DNN.  Or perhaps exporting content (separate from skins etc) for import into a different CMS system ... something that I could co-opt for my use.  If it had been done for a simple html back-conversion then it might have taken into account things like sitemaps and file/folder layout (to mirror existing paths).