I would like to know if there is a best practices document or well known QA and deployment procedures for DotNetNuke.  I have looked in the Documentation section but don't see anything related to this.

Any suggestions?

For modules we maintain a parallel installation of DNN that matches our production site(s), and test new modules in it.  Usually it's done in a Virtual PC environment and easy to blow away and recreate.  For content, since we don't currently have a decent workflow setup, we kind of fudge it.  Content gets approved in various manners by different departments, then posted, then fixed when someone complains.  Neither of these processes has changed since we went to DNN, except that I'm no longer stuck reviewing and posting all content.  :)

Jeff

Thanks for the quick replies.

I am mostly concerned about modules because if database changes are needed to support the new version of the module then they can't be deployed on the production site without causing the current module to fail.  A side by side deployment seems the only safe way but if the module requires manual configuration I am concerned about consistency.  For content is it possible to script content changes between the environments to be more consistent or deploy resource files?

Thank you