cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Cocoon Wiki] New: PortalTools
Date Fri, 28 Jan 2005 10:32:55 GMT
   Date: 2005-01-28T02:32:54
   Editor: JensMaukisch
   Wiki: Cocoon Wiki
   Page: PortalTools

   no comment

New Page:

= PortalTools =

== Introduction ==
There are two points of view for Cocoon Portal Tools. First the usability for an admin of
the Portal should be increased. The Cocoon Portal is a high configurable environment. By the
use of the complex file-based configuration the person needs a lot of time and an advanced
knowledge of Cocoon. Tools for an admin within the web application can improve the usability
by speed and clarity and can also increase the acceptance for the portal. 

On the other side new tools should be build for the user of the portal. Nowadays all people,
who use the portal, have only the possibility to watch the content. The idea is to give the
user a kind of reduced admin tool. For example with the use of the user profile environment
of the Cocoon Portal everyone can edit the layout and save it on the server for the next session.
The user can change the content coplets by selecting different ones. Another tool will provide
the ability to the user to create new coplets or change the whole layout. 

At the end the Cocoon Portal will have different tools, which will provide different functions
to users and admins. Thereby the idea is to build a simple framework with some sample tools,
where new tools can easily be added or removed. 

/!\ Please note: The provided Tools are just samples and maybe not ready for production use.
The samples are just Tools for the User of the Portal and not for the portal administrator.

== Concept ==
The intention to develop the PortalTools framework was the lack of tool-support in the new
portal and a growing need for tools as in the old portal. The main difference betwenn the
new tools an the the old ones in the portal-fw is that the new ones are not directly build
into the portal itself but they run parallel. So there is no need to have the tools if you
dont need them.

=== What should the framework/tools do? ===

 * Provide an easy way to integrate/add tools to the Portal
 * Provide a standard how to develop tools
 * Offer a userinterface for functions provided by the Portal

=== What should the framework/tools not do? ===

 * The tools should not add additional functions to the portal itself, they should just provide
a userinterface.

== Documentation ==

 * PortalToolsFramework
 * PortalToolsPlugins
 * PortalToolsSampleTools
 * PortalToolsCodingStandards 

View raw message