The field UI is really hard to use. Everyone knows it's a problem, but no one is actively working on it (no open issues). Let's revisit!
#521468: Redesign content type editing (after CCK UI is in)

Discussion around the field UI redesign stopped in 2009, but was happening over here:
UI-oriented summary of D7 Field API

Related issues for Drupal 8:
Scotch: Blocks & Layouts Everywhere Initiative
D8 UX Analysis: Design Assumptions and Principles
D8 UX Analysis – Layouts, IA Spaces and the Principle of Definition-Usage Pairs

Let's also keep in mind that the "display fields" tab may end up being replaced by Scotch / templates / something else - but we'll still need the add fields tab, and it still needs a lot of improvement!

Proposed resolution

This whole process probably needs a redesign from the ground up. Some frustrating things about the current system that could use to be changed in the new system (if not replaced entirely) are as follows:
- add step numbers to the process of adding a field so users know when they are "done"
- remove page 2 of the multi-step form, since the "questions" asked there are repeated on page 3
- send users to the display fields interface when they are done adding a field (not back to the add field screen)

Remaining tasks

- Design
- Implementation

User interface changes

Content Builder, step 1Content Builder, step 2Content Builder, step 3Content Builder, step 4

API changes

- unknown


Issue summary:View changes

suggest total redesign

Issue summary:View changes

more about display fields tab

Issue tags:+Usability
new169.26 KB
new345.11 KB
new234.01 KB
new202.43 KB

Attached is an example of how I actually want to build content. I've excluded the layout part of "display settings" since that will need to belong to scotch, but here's how I want to add and configure my fields (which, by the way, should not be called fields!)

After people get through step 4, they should be redirected to (step 5?) the layout manager - where they can position the element on the "page".

What I get from these is that we need multi-step forms to help people through picking and configuring individual fields, which is definately something we want to provide as a pattern.

The form builder approach is also outlined in #1472348: Fields UI improvements using form builder pattern - not sure yet which one to mark duplicate so we can focus in one issue.

Version:9.x-dev» 8.x-dev
Category:feature» task
Priority:Major» Normal

Very interesting!

...uploading the pdf files from #1 as images. All credits to Jennifer.

[Edit: moved images to issue summary]


Issue summary:View changes

link to D7 redesign issue

Issue summary:View changes

...screenshots of the proposed changes.

Version:8.x-dev» 9.x-dev
Category:task» feature

Don't really see this happening in D8 anymore.

Priority:Normal» Major

However, it's a pretty sub-optimal screen as far as UX is concerned, so escalating to major.

new96.73 KB
new162.41 KB
new134.87 KB
new109.04 KB

...the screenshots were not attached back in #5 for some reason :/