Attention

This document was written for an unsupported version of Plone, Plone 2.1.x, and was last updated 1240 days ago.

For more information, see the version support policy.

To learn how to upgrade to the current version of Plone, read the upgrade manual.

Creating public websites with staging and custom skins

In this tutorial, Martin Aspeli plays investigative journalist, deciphering Alan's ramblings to find out exactly how Enfold deploy real sites with staging and different authoring and public skins.

Warning: This item is marked as outdated.

  1. Introduction Why would you want to do this?
  2. Pieces of the puzzle Several technologies are involved in this set-up. It is important that you understand what each of them does.
  3. Setting up Plone With the server set up, a Plone instance created and products installed, we must configure the Plone site to work with staging.
  4. Configuring your web server With Zope and Plone set up, you need to set up Apache or IIS so that the public site and the private site are on separate URL
  5. Trying it out With all the pieces in place, you can try out your new staged site.
  6. Taking it further The solution we have outlined is fairly flexible. However, not all content makes sense to stage. There are also many other ways of using EnSimpleStaging to stage content.

All content on one page (useful for printing, presentation mode etc.)

 

Contribute

Something wrong or out of date? Anybody can edit or create a new article in the knowledge base. Simply create an account on this site, log in, and click the Edit button to contribute.