Personal tools
You are here: Home Products Plone Roadmap #1: Plone Control Panel
Navigation
Log in


Forgot your password?
New user?
 
Document Actions

#1: Plone Control Panel

Contents
  1. Motivation
  2. Proposal
  3. Implementation
by Alexander Limi last modified June 11, 2006 - 00:21
Proposed by
andym
Proposal type
State
completed

Motivation

The configuration information for a plone site is scattered all over the ZMI and can be in unintuitive places. The current plone setup form is too simple and unstructured to cope with the addition of many more options. The ZMI itself isn't directly accessible TTP and so can lead to confusion with its different and slightly clunky interface, its inaccessibility and its unintuitive organisation.

The Plone Controller (seen in the Windows Installer version of Plone) relies on physical access to the machine Zope is running on. Since this is often impossible, a TTP system is the best solution.

A last motivation is to provide a modular configuration system so that products can supply their own configuration properties without destroying the user-interface or overriding core files in the CMF or Plone.

Proposal

Plone aims to be an easy-to-use CMS for Zope 2 and the CMF. Currently, however, most configuration has to be done through unintuitive places in the Zope Management Interface (ZMI) or a short, unstructured plone setup form that duplicates a few of these properties. This proposal is for the addition of an extensible control panel system that would allow the creation of configuration applets to group together various properties logically and allow a more usable set of management tools.

This control panel would exist as a CMF tool implementing useful API functions and views and a "configlet" registry. Configlets would be implemented as standard Zope products, though instead of registering with Zope or CMF, they would register with the control panel tool.

Configlets would typically contain a set of configuration options and (perhaps) processes that are logically related. A number of configlets would come with the tool by default (such as skins, users, content types and syndication) but products will be able to register their own configlets for universal options.

Implementation

No notes given in original PLIP


For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by