- Provide "click dummies" or clickable mockups of future plone UI that'll be used for user testing. Ideally, we can start hasing out the best possible UI for the various complicated UI parts plone is adding.
- Improve various bits of Plone's existing UI failings.
- best ways to separate global from context actions
- cmsui is a pretty good starting place for this
- Unified editing experience
- How can we mix deco with editing regular plone content
- Toolbar styles
- perhaps we shouldn't use the black toolbar since it's popular to use black toolbars is themes already
- Toolbar placement?
- should we try and get evidence that putting the toolbar up top is best?
- Keeping toolbar on top might be an implementation requirement...
Start writing a UI guidelines document. Use UCLA doc as a base.
Make sure to include guidelines on overlays.
Use one awesome reference browser widget for all content selection.
Start with archetypes.referencebrowserwidget and make that better after we have it all integrated
- Use it for plone.app.collection too.
- What about plone.formwidget.contenttree?
Integrate content rules mockup. https://dev.plone.org/ticket/13152
I can give access to the original balsamiq mockup if anyone wants to modify. Otherwise, it's a pretty decent place to start.
Please someone, just fix this with something decent.
I have plenty of other tasks we can do if we have the people.
- provides information on sprint
- will house all created click dummies and base click dummies to work with