[xwiki-devs] [Discussion] Customize button for the dashboard

Vincent Massol vincent at massol.net
Tue Mar 22 17:16:28 UTC 2011

On Mar 22, 2011, at 5:26 PM, Luca Anca wrote:

> Hi all,
> I've got some suggestions that the current way of editing the dashboard
> is not really intuitive (Edit -> Inline Form), and mainly because users
> wouldn't necessarily look under "Edit" for a method to change the
> dashboard. Also, other users that I've observed, forgot that they need
> to go in some edit mode before changing things.
> I also agree that without documentation no user would figure out that
> editing a dashboard is under Edit -> Inline Form. While editing will
> still remain "in inline mode", from the technical pov, we need to
> provide a easier way for users to discover this. 
> Let's look at the following options:
> 1/ Add a "Customize" menu entry under edit, in the page menu, as
> proposed in the mockups from Cati, a long time ago:
> http://incubator.myxwiki.org/xwiki/bin/view/Improvements/GadgetsDashboard .
> 2/ Add a "Customize this dashboard" button in the dashboard in view
> mode, in the top right corner, something like
> http://dev.xwiki.org/xwiki/bin/download/Design/GadgetIntegration/oldDashboardCustomize.png but styled better to integrate with the current dashboard.
> 3/ Define and implement a mechanism to allow the inline form edit to be
> triggered for a document without that document having to include a
> document which has an object in it. E.g. as Vincent proposed at one
> point, trigger inline mode when an object is present in the current
> document.

I'd like to have an XObject that tells what is the default edit mode. Then add it to the home page and make that page a full dashboard, possibly with the welcome message as a gadget.

Whether we also need 1/ or 2/ is debatable but independently of this I'd like to implement this 3.


> I should note that solutions 1 and 3 still assume that the user will go
> to "Edit" to try to customize the dashboard, which can also be
> problematic (I cannot figure it out for sure right now, we need fresh
> users or proper UX expertise which I don't have).
> Thanks,
> Anca

More information about the devs mailing list