Document Actions
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.
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.
Page
6
of
6.
EnSimpleStaging is, as its name suggests, quite simple. It helps you move content from the staging sandbox to the public site, and it can filter what it stages based on workflow state. By not being more restrictive, EnSimpleStaging allows you to manage your site and authoring process using other Plone tools more easily.
Here are some suggestions for how you may want to configure your system:
- Unstaged content
- Let's say you wanted an issue tracker in your site. Staging that makes no sense. Luckily, EnSimpleStaging is clever enough to leave unstaged content in the
public_sitealone. Hence, you can simply add your issue tracker object to the public site manually, and it will be left alone. - Multiple workspaces
- You can add several staging areas, and use different permissions on each via the
sharingtab. Hence, different groups in your organisation can use different workspaces to manage different parts of the site. - Multiple workflows
- With CMFPlacefulWorkflow you can even have content different workflows for each workspace.
- Multiple stages
- You can make one stage deploy into another. For example, you could let several teams each have their own workspace, all deploying into a single staging area. This area would be used to view the site as a whole, before being deployed to
public_website. Permissions and workflows would probably be different in each workspace.
by
Martin Aspeli
—
last modified
December 30, 2005 - 00:09
Contributors:
Alan Runyan, Martin Aspeli
All content is copyright Plone Foundation and the individual contributors.
deploying documents in one state without deleting others
when i deploy "published" documents of a stage, documents in public stage that are in an other state ("pending", etc) are deleted in public_stage so, i can't deploy a stage unless all documents have been validated is there any solution to this problem ?
thanks