Portlets are dynamic content units, used in corporate, educational and personalization-aware portals, that allow its users a unique and self-made experience of a visit or work session. Usually displayed within graphical containers (generally boxes), portles can be used throughout any portal or enterprise intranet and also packaged and delivered remotely through different standard protocols. The most noticeable use of these are those MySomething pages, because its object condition allows them to be arranged in different ways within a same page ( a.k.a. site personalization. ).
Current features CMFPortlets is a work in progress. In its current form is a layouting engine made out of skins for the current CMF (no hard-wires yet) that enable the display and layout configuration of portlets in pages. CMFPortlets currently allows:
Sample basic portlets features:
Desired features (some of them in the works)
The CMFPagelets Project
CMFPagelets is meant to be a layer of abstraction of all portal skins, by allowing to group important lines of DTML or PythonScript code in an identifiable unit named pagelet. A pagelet is renderable or not. A pagelet has plugs to page variables, and javascript and stylesheets repositories. A pagelet is ESI cacheable depending on its own properties. A pagelet is meant to be handled much the same as you can now handle boxes within CMFPortlets, with the only difference that what you get after performing modifications to your control skin is a clean DTML or PythonScript skin, even a ZPT, stored at the usual folders inside the portal_skins tool.
pagelet
control skin
Related links:
CMFPortlets 0.5.2 tour.
CMFPortlets 0.5.2 Readme
CMFPortlets 0.5 screenshots page
Comments and contributions page. I'd appreciate any feedback on this subject.