Portlet

This page is not final, yet. See Forum Discussion

A portlet is component, with a defined scope of application. It's may be also called a widget.

To use a portlet, you can either place it hardcoded in your template, or you can dynamically add portlets to containers (or slots).

Contents 1 Requirements 1.1 Not to have 2 Directories 3 Conventions

Requirements

• Add/update of components by the author.
• Register and approve new authors
• Categorize or tag components
• Search for components by name, tag, author
• Keep multiple version of the same component, no SVN or CVS
• A wiki style doc system + comments for each component
• Contact author,
• Listing of components via html, rss

Not to have

• CVS or SVN, because it is complicated to setup I think
• bug tracking, use the email to author
• a build system, should just upload zipped files.
• Something simple and easy to find components is all we need. We don't want the components to scatter around the forums.

Directories

Inspired by PradoPortal ©

• PortletName
  • PortletName.php
  • PortletName.tpl
  • install/
    • PortletName.php
    • db/
  • admin/
  • edit/

Conventions

• a portlet may not contain pages