[PLIP-Advisories] Re: [Plone] #9311: Clean up of user related actions UI

[plip-advisories at lists.plone.org]

#9311: Clean up of user related actions UI
---------------------+------------------------------------------------------
 Reporter:  dokter   |        Owner:  dokter  
     Type:  PLIP     |       Status:  assigned
 Priority:  minor    |    Milestone:  4.0     
Component:  Unknown  |   Resolution:          
 Keywords:           |  
---------------------+------------------------------------------------------
Description changed by dokter:

Old description:

> '''Proposer:''' Duco Dokter[[BR]]
> '''Seconder:''' Alexander Limi, David Convent[[BR]]
> [[BR]]
> == Motivation ==
> The user admin related actions, from the perspective of the user
> itself, are scattered over the user interface. The following ''actions''
> are available:
>
>  * access to the dashboard,
>  * user data
>  * preferences
>  * personal preferences
>  * profile (author info)
>  * user folder
>  * change password
>
> The several configuration sets are not uniform: name and email address
> are part of preferences for example, but are clearly user data, as
> opposed to wysiwyg editor setting or skin preference.  Also, the
> personal bar is really in the way of the overall design.
>
> == Assumptions ==
> It is hard for users to determine exactely what access to use to get
> to a specific setting.
>
> == Proposal & Implementation ==
> User related actions are moveed to new package '''plone.app.users'''.
>
> What should be available to the user is:
>
>  * public profile, based on tiles. The user can determine what to show
>    to the public, for instance a 'recently added' tile, or an overview
>    of specific user data.
>  * preferences, where a user can set favorite editor, skin, etc.
>  * user data, where a user can administer personal data, like email
>    address, surname, etc.
>  * dashboard
>  * change password
>  * user folder
>
> In the UI, there should only be a maximum of three accessors:
>  1. a clickable login name, that takes the user to his/her dashboard
>  2. ''Account'', that takes the user to user the, config panel. This
> panel
>     provides three tabs: user data, preferences and change password.
>  3. ''My stuff'', in case a user has a personal folder.
>
> Also, the user can set his/her start page for the site in the
> preferences. This should be the page the user is directed to after
> login. Default is the plone start page. Other options are dashboard,
> my stuff, etc.
>
> The personal bar will be moved to the top of the page, to remove it
> from overall design, and give it a clear place.
>
> The user data and preferences will be implemented using the same
> back-end as in the current situation, only the way to navigate there
> will be changed, and the forms will be implemented using zope.forms,
> located in tabs in an overall user admin screen.
>
> == Deliverables ==
>
> Personal bar moved to top, user data and preferences clearly
> separated, less entry points for user functionality, unit tests for
> all forms.
>
> Other than that, localization and unit tests are largely in place, but
> need to be
> adapted to the new situation and moved to plone.app.users. Documentation
> will be altered and moved whereever necessary.
>
> == Risks ==
> The new design is a deviation from the current situation; migration to
> Plone 4 will require adaptation of users to the new way of accessing
> functionality.
>
> == Participants ==
> Duco Dokter, dokter
> Kees Hink, khink
> Kim Chee Leong, kcleong
> David Convent, davconvent
>
> == Progress ==
> Some of the work has been done at the Baarn 2009 sprint

New description:

 '''Proposer:''' Duco Dokter[[BR]]
 '''Seconder:''' Alexander Limi, David Convent[[BR]]
 [[BR]]
 == Motivation ==
 The user admin related actions, from the perspective of the user
 itself, are scattered over the user interface. The following ''actions''
 are available:

  * access to the dashboard,
  * user data
  * preferences
  * personal preferences
  * profile (author info)
  * user folder
  * change password

 The several configuration sets are not uniform: name and email address
 are part of preferences for example, but are clearly user data, as
 opposed to wysiwyg editor setting or skin preference.  Also, the
 personal bar is really in the way of the overall design.

 == Assumptions ==
 It is hard for users to determine exactely what access to use to get
 to a specific setting.

 == Proposal & Implementation ==
 User related actions are moveed to new package '''plone.app.users'''.

 What should be available to the user is:

  * public profile, based on tiles. The user can determine what to show
    to the public, for instance a 'recently added' tile, or an overview
    of specific user data.
  * preferences, where a user can set favorite editor, skin, etc.
  * user data, where a user can administer personal data, like email
    address, surname, etc.
  * dashboard
  * change password
  * user folder

 In the UI, there should only be a maximum of three accessors:
  1. a clickable login name, that takes the user to his/her dashboard
  2. ''Account'', that takes the user to user the, config panel. This panel
     provides three tabs: user data, preferences and change password.
  3. ''My stuff'', in case a user has a personal folder.

 Also, the user can set his/her start page for the site in the
 preferences. This should be the page the user is directed to after
 login. Default is the plone start page. Other options are dashboard,
 my stuff, etc.

 The personal bar will be moved to the top of the page, to remove it
 from overall design, and give it a clear place.

 The user data and preferences will be implemented using the same
 back-end as in the current situation, only the way to navigate there
 will be changed, and the forms will be implemented using zope.forms,
 located in tabs in an overall user admin screen.

 == Deliverables ==

 Personal bar moved to top, user data and preferences clearly
 separated, less entry points for user functionality, unit tests for
 all forms.

 Other than that, localization and unit tests are largely in place, but
 need to be
 adapted to the new situation and moved to plone.app.users. Documentation
 will be altered and moved whereever necessary.

 == Risks ==
 The new design is a deviation from the current situation; migration to
 Plone 4 will require adaptation of users to the new way of accessing
 functionality.

 == Participants ==
 Wietze Helmantel, helmantel
 Kim Chee Leong, kcleong
 David Convent, davconvent

 == Progress ==
 Some of the work has been done at the Baarn 2009 sprint

--

-- 
Ticket URL: <http://dev.plone.org/plone/ticket/9311#comment:13>
Plone <http://plone.org>
Plone Content Management System