Ticket #13140 (confirmed Feature Request)
UI Revamp
Reported by: | vangheem | Owned by: | vangheem |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | User Experience and Interface | Version: | 4.2 |
Keywords: | Cc: | davilima6, spereverde |
Description (last modified by vangheem) (diff)
Revamp Tasks
- Provide obvious fixes and improvements to plone's existing UI failures
- Provide guidelines to developers in user testing new UI. The work that martin and the developers at UCLA did is valuable in this respect.
- Make decisions and implement new widgets, js libraries and testing infrastructure.
Current Plone UI Issues
- content rules
- Confusing UI and too many page loads. Various areas this can be improved.
- Ticket with mockups found at: https://dev.plone.org/ticket/13152
- folder contents
- drag and drop rarely works and pisses many users off, no easy way to move items in a large folder. I ended up writing wildcard.foldercontents to address some of these issues. If we can integrate this or something similar, I think it'd be a big help.
- widgets
- keyword/tag widget
- even the new one isn't very good. I like eea.tags or using the chosen widget(j
- date/time
- in and out widget
- one of the biggest widget failures. This could also be a chosen widget. Some work to this has been played around with on plone.app.widgets
- creators/contributors widget
- should be able to choose actual users, maybe display this info somewhere on the content in a viewlet
- keyword/tag widget
- Control panel
- could use better organization
- users/groups control panel
- maybe use http://datatables.net/ or http://www.flexigrid.info/
- html filtering
- terrible widgets here again...
- types
- not bad but could use a bit of love
- workflow manager
- plip'd for 4.3 but needs testing
- Dexterity TTW editor
- keyboard shortcuts
- formlib reference widget
- maybe just adapt archetypes.referencebrowserwidget to work with formlib?
- review plip: https://dev.plone.org/ticket/9057
Providing UI Guidelines
- Include user testing guidelines and questionaires
- Guidelines for addon developers on where the correct places are to hook into plone
- Write documentation in http://buildoutcoredev.readthedocs.org/en/latest/ or plone.org?
Long term solutions
- plone.app.toolbar(and cmsui)
- bootstrapification
- maybe namespace bootstrap css rules so we can iteratively apply new rules to it
Contributors
- Timo Stollenwerk
- Martin Aspeli
- Jean-Michel FRANCOIS
- Elizabeth Leddy
- John Hren
- Kim Paulissen
- Thijs Jonkman (thijs.jonkman@…) - THijs, github(TH-code)
- Vilmos Somogyi (vilmos@…) - plone.org: vilmoss, github(vsomogyi)
Change History
Note: See
TracTickets for help on using
tickets.