Introduction
The ftw.publisher packages provide tools for publishing plone contents from one instance
to another.
By providing a simple mechanism to invoke the publishing, it's possible to set up the
publisher in a variety of ways, such as workflow bound, manually invoked or automated
publication.
The ftw.publisher package library also provides a variety of surveillance and analysis
tools for making maintenance confortable.
Staging
The ftw.publisher is meant to be used in a environment where there are two seperate
plone-sites which do not share their database. The editors work on a editorial site and
the contents are published to a public site when they are ready. Setting up such an
environment with ftw.publisher let you have a powerful staging solution with completly
isolated instances.
Network security
Using an environment with two isolated installations makes it possible to protect the
editorial site with firewalls or to put it even in a private company network. This way the
editorial site is completly protected from the internet, which is in some use cases
mandatory for protecting other - unpublished - contents (for example when publishing the
internet contents from the intranet).
Component support
- Archetypes objects
Standard Archetypes field types
Topics: criterias are published automatically when topic is published
Backreferences - references are added automatically as soon both objects are published
Additional interfaces added on /manage_interfaces or by other products
Contextual portlets
Properties
With the publisher adapter structure it is as easy as creating another adapter to support
other components. For instance annotations are not supported by design, because you may not
want to publish all annotations but only certain ones. Therefore it is easyer to implement
custom adapters for those annotations which need to be published.
|