swentel's sandbox: Form Builder Field UI | drupal.org
Attempt to use Form Builder for a new Field UI starting as a Drupal 7 contrib. Maybe one day this can become D8 material.
Attempt to use Form Builder for a new Field UI starting as a Drupal 7 contrib. Maybe one day this can become D8 material.
Next time you find yourself thinking about using the words “click” or “here” on your links, remember the effects it’ll have on the user experience. The challenge is to make your links say “click here” without actually saying “click here”, and there are many ways to do this. It will take some thought and effort on your part, but in the end, your users will benefit with a better experience of your interface. You can take the easy way out and use “click here” on your links, or you can spend some time to find the right phrasing for your links that’ll click with your users.
Previewing is a big part of creating content, and people are currently very confused by preview being shown in the back-end instead of front-end.
The meta tools we present users; menu, revisioning, authoring information are cumbersome and often result to conflicting mental models.
Text formats are still somewhat of a mystery to most of our users, they miss a WYSIWYG editor.
The lack of a common workflows like save as draft is a disappointment.
Tools for moderating content are almost non existent, our filters are hard to use and search is non existent.
We organized the usability issues into four different layers: conceptual, flow, terminology, and interface. In this document we explain what each of these means, and provide key examples and quotes from users. We also propose a quick and concise up-to-speed aid that welcomes users on a new Drupal installation.
see also: http://drupal.org/node/1427940
* Introduce a new grouping pattern in the form of a sidebar, to allow for easier scanning of settings and avoid the space-consuming vertical tabs.
* Placing the primary publishing options closer to the action of saving.
* Update the look & feel of Seven to solve a number of visual design issues.
* Introduce a more consistent pattern for actions.
Multistep adds multiple-step functionality to content type editing forms. It does so by assigning a step number to each fieldgroup within the content type and hiding all the groups that do not belong to the current step. The user can then use different submitting buttons that will redirect to the previous, next, or current step.