Formerly titled "The options under the Add field drop-down describe the data you want to store, but the user was imagining the widget it would produce".
During the usability sessions, some participants struggled to figure out how to add fields. For example, they where given the task to add a select box to choose from available countries. As the field UI asks for the data type first, without knowledge of the way that Drupal stores field data it was hard to find out that "List (text)" was the data type to choose.
Add a visual UI to cover the 80% use case and make it as easy as possible to add a field, for the more advanced users or the exceptional fields, link to the current UI.
- Decide which fields are in the 80%
- Decide which settings they need
- Provide a thumbnail, label and description for each
- A new UI will be added and will be the entry point for "Add a field", we can add an option so the site admin can decide which UI is the default one
None
None
Needs work
Proposed Plan
Makes Drupal easier to use. Preferred over UX, D7UX, etc.
It is used to alert the product manager core committer(s) that an issue represents a significant new feature, UI change, or change to the "user experience" of Drupal, and their signoff is needed. If an issue significantly affects the usability of Drupal, use Needs usability review instead (see the governance policy draft for more information).
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.