Staging Content in DotNetNuke

Introduction

If you’re designing a complex website, then it’s a best practice to establish a staging server on which all of your website changes are made before they go live. Read on for an overview.

What is a Content Staging Server?

A content staging server is any separate server that exists as a testing site for code changes. You can review the code and test the functionality of various features at any time. Clarity’s staging servers are behind a corporate Firewall for extra security. The content staging system also compares the two servers (staging and production) to identify missing components or pages that may still need to be published – so you’ll never have to worry about “forgetting” unpublished material on your content server.

Staging Content in DotNetNuke

Users of DotNetNuke Enterprise (now Evoq Content) have a built-in content staging module that will automate the process of content staging. If you’re developing in DotNetNuke Community or Professional, however, you still have options. At Clarity we use a variety of tools to push content from our servers to your website, and we perform database backups automatically. You can also point the connectionstring from their development copy to the staging database and update from there.

Content Staging at Clarity Ventures

At Clarity, we develop everything on a staging server before we push any updates to your site. The client has full access to the “dev site” at all times, so they can review progress, test functions, and provide feedback. We aim to keep our clients comfortable and confident in their website throughout the entire development process. Contact a Clarity representative today if you’re interested in starting your next development project with us.

Find out more about Clarity VenturesSee our Enterprise Web portfolio