#152: Dashboard
We want to create a page where the user can add portlets/widgets showing summaries with content of the portal. The idea is to provide an overview/summery over the content. The criteria which content and wich portlettype can be set/chosen by the user. The personal google page is a very good example.
- Proposed by
- Christof Haemmerle
- Seconded by
- Alexander Limi
- Proposal type
- User interface
- Assigned to release
- State
- completed
Definitions
- The layouts of the Dashboard should be usable by the user but predefined. (like layouts in CompositPack)
- The user should be able to customize the criteria of the content to show. (SmartFolder as a ContentProvider)
- widget/portlets can be installed as products/packages and are available through the add menu.
- widget/portlets can be draged and dropped between slots in the Dashboard layout
- widget/portlets can be draged and dropped in the existing slot to reorder it.
- widget/portlets have a configuration section (personalized google page or attached image
- portal admin should be able to enforce portlets to exist on users Dashboard based on User Role or Group.
Position can still though be defined by the user. - The user should be able to drag and drop the portlets in a predefined layout (for example 3 colum layout). Maybe we can push this so far that we can also provide a plugin functionality so portaladmins could create their portlets/widget very easily and install them as zope products/packages into the plone site. That would make them available as a addable portlet/widget on the dashboard.
Motivation
As complexity and amount of content grows we want to ensure that it's easy to display user definable content on a central place. We want to provide an overview on the activity of the content and the content itself.
Proposal
- We relay on the new PlonePortlet (Plip 118) and the need to integrate a viewlet/layout concept in CompositePack.
- Create Viewlets for contenttypes
Implementation
The Implementation should be based on Plone Portlets (Plip 118) without adding any more logic to a special Dashboard product.
Deliverables
Since we relay on existing functionality there should not be any tests. Documentation will be very short cause this is already a very wellknown way of dislpaying content overviews.
Risks
none
Participants
Christof Haemmerle
<put your name here>
Danny added the following
In our company, our most common workflows all begin with the draft state. There is a worklist that is called Work in progress that lists all objects in this state. Also, it is possible to show the worklist in the context of a folder and subfolders. Then the user can quickly see e.g. in the context of a team folder, which items require attention.