Posted by kika on March 10, 2012 at 1:37pm
I started working on add / edit flows in Drupal. It's about unification add / edit interactions in Drupal, harmonizing their forms, layout, flows and language; creating and implementing universal UI patterns.
http://kika.trip.ee/files/d8ux/add.html
is the first rough draft of analysis / proposal. The idea is to let it mature a bit and then bring it to D8 issue queue.
Comments
Sounds Great keep us posted.
Sounds Great keep us posted.
Head Dragon Kid Stevens
Of Web-DrupalDesign .com
The doc is taking shape. It
The doc is taking shape. It contains three parts:
Please give feedback: is the terms / language / concepts understandable?
Do not worry about the structure and formatting too much -- the idea is to move half of it to d.o issue queue as a meta-issue, create sub-issues and leave the background part to the original doc or post it here as a wikipage.
Great work Kika
We need to do more of this. I recommend you put the Compact UI proposal directly under the small add. Here's why. As I read this (it's a long doc), I was first on the defense thinking "that's not the pattern we'd want for a small add." Thankfully, I kept reading and realize you too felt the same way.
In short, for readers who drop in and leave, it would be good to make sure they see this information.
Thanks for this. I think I
Thanks for this. I think I had a similar feeling as Noyz expressed, in wanting to see examples where you start introducing the 3 types of 'add'. Maybe anchor link to examples section or just a little text, for example with small add – "like adding a new forum or feed".
Regardless, very valuable inventory of things here. How do you think to open this up for wider feedback? There are many moving parts in this. It's always tough to balance between giving the whole big picture and getting specific, concrete feedback. Maybe a similar approach as the 'empty table' pattern we introduced: do one solid implementation of the new pattern, then create followups to convert other instances of same to the new pattern.
Keep us updated. What kind of help would be most effective at this stage?
Thanks
Vocabulary. I am no native speaker. How to call those different add / edit flows etc.
EDIT: putting roll-out plan to separate comment
Here's the plan
1) Simplify and migrate my doc to g.d.o/usability
2) Create following meta-issues on d.o issue queue:
2.1) "#xxxxxxx [meta] Unify add form confirmation messages and labels
This post contains quick reasoning and proposed unified messages and labels.
Links back to g.d.o/usability reference document
Post sub-issues (and link them back to meta issue):
"#xxxxxxx Convert form x labeling to a new pattern" etc
..
2.2) Create "#xxxxxx [meta] Unify redirection after add / edit form submissions"
This post contains quick reasoning and proposed redirection flow. Links back to g.d.o/usability reference document
Link to old issues:
"#??????? Take user back to term listing after term add"
etc.
Post and link to dependecies:
"#xxxxx Figure out how to provide additional follow-up actions after successful add / edit"
Post sub issues:
"#xxxxxxx Convert form x to unified redirection" etc
2.3) "#xxxxxxx [meta] Introduce "compact add"
Introduce compact add idea, link back to g.d.o/usability reference document.
Post and link to dependecies:
"#1175830 Research and implement accessible / reusable modal dialog"
"#xxxxxxx Implement popover control
"#xxxxxxx Allow text fields to be #collapsible"
"#xxxxxxx Collapse description fields
"#xxxxxxx Remove weight form item from add / edit forms
Post sub issues:
"#xxxxxxx Convert form x to compact add" etc
…