Ektron CMS400.NET Setup Manual

Moving Content from Staging to Production Server
Moving Content from Staging to
Production Server
Overview
Best Practice
Before Ektron CMS400.NET, HTML files were deployed to a Web
site in a three-stage process.
1. An author updates content on a staging server, which has a
copy of the Web site.
2. A reviewer checks and possibly modifies the content.
3. The approved content is moved to a production server, which
hosts the live Web site.
An Ektron Content Management System (CMS) provides a virtual
staging server, which lets authors work directly on a production
server yet prevents site visitors from viewing modifications until
they are approved.
Here’s how it works. An author edits one or more content blocks
and submits them for approval. Authorized reviewers preview the
changes and decide to publish or reject them. Reviewers can also
edit the content then publish. All of this can occur on a single
server, which acts as a virtual staging and a production server.
Ektron CMS400.NET also supports the traditional model of separate
staging and production servers. This section describes options for
managing servers and suggests best practices for a successful
deployment.
Ektron’s suggested best practice is a combination approach, using
both a virtual and a physical staging server.
Ektron CMS400.NET Setup Manual, Version 5.0, Revision 9 150