you can use portal templates if the contents are all new (http://www.dotnetnuke.com/Resources/Wiki/Page/Portal-templates.aspx), or export/import module contents (if the module supports IPortable) or else if you're using the Professional editon you can use the content staging suppoort - http://www.dotnetnuke.com/Resources/Wiki/Page/Content-Staging.aspx

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Hi Folks,

 Thanks for the replies - perhaps I have though too far ahead in my initial question..

 Is it a common approach with DNN to use a full staging environment or is it more common to use the version control / approval workflow features on the live instance?

 To provide a scenario Marketing might want to approve a press release - presently this is via an intranet version of the production site. In the 'hybrid' model DNN makes possible I guess page visibility control etc. allows me to give reviewer access.

 Is a more realistic approach to develop the initial layout, styling, copy etc. locally and then move this to production thereafter using workflows etc. to update and add content?

 When a site needs a branding update I guess I would need to again stage it locally, apply the new skin / modules etc and then follow the initial 'go live' process - potentially switching versions via a continuity server to ensure minimal downtime.

 With regards to backups do most people take nightlies of the application folder / SQL DB from the production server?

Thanks,
Ian