Contrib.social

Rethink the add view/form mode buttons on the view/form modes pages

Open on Drupal.org →
Created on 29 October 2023, about 1 year ago
Updated 30 October 2023, about 1 year ago

Problem/Motivation

During the usability meeting 📌 Drupal Usability Meeting 2023-10-27 RTBC (for the record, the attendees were @AaronMcHale, @anmolgoyal74, @benjifisher, @rkoller, @shaal, @simohell, and @worldlinemine) we've discussed 📌 Allow user to add display modes from respective field UI's. Needs work as well as the preceding changes to the view and form modes pages. Those changes entail 📌 Give display modes a description Fixed , making the add view mode links at the bottom of each entity type section a button , plus the fact that the columns aren't really aligned across entity type sections for a long time it looks like (see the screenshot)

The latter lead to the creation of ✨ Improve the readability of the view mode and form mode page Active . The question about the buttons we've considered a separate but related issue and therefore wanted to create a dedicated issue. There were three points noted during the discussion:

  • the buttons are listed within an entity type section like a row of a form or view mode. visually they differ but functionally they are completely different but still they are listed in the context of such section lists
  • those add buttons for an entity type are listed at the end of the section instead of at the beginning. at the same time there is a dedicated add button for all entity types at the top of the page. the section's add buttons might go unnoticed for screenreader users that way?
  • the micro copy for the buttons is rather long. the goal should be two or three words max, while the ideal goal for button copy should be single worded labels.

I've labeled the issue as a task since it is not a real bug nor a new feature from my point of view.

Steps to reproduce

Proposed resolution

There were two ideas:

  1. In case the add view/form mode buttons should be kept for each entity type section then move them out of the lists. at the moment the button is positioned in the name column within the list, instead move it outside of the list, vertically in the same row as the title of the entity type section at the same position it horizontally in line with the edit buttons in the operations column.
  2. The other option might be to remove those add buttons for each entity type section entirely and just rely on the single add view mode button for the creation of view/form modes for the different entity types.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Closed: outdated

Version

11.0 🔥

Component
Field UI  →

Last updated about 2 hours ago

Created by

🇩🇪Germany rkoller Nürnberg, Germany

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Field UX

    Usability improvements related to the Field UI

Sign in to follow issues

Comments & Activities

  • Issue created by @rkoller
  • Comment about 1 year ago →
    🇩🇪Germany rkoller Nürnberg, Germany
  • Comment about 1 year ago →
    🇫🇮Finland lauriii Finland

    There's an issue in the RTBC queue 🐛 Duplicate "Add view mode" buttons RTBC for the fact that having two different buttons for the same task was something some users found confusing. On that issue, the proposal was to remove the buttons for the individual bundles but I'm personally not really 100% sure if it's the right solution.

  • Comment about 1 year ago →
    🇩🇪Germany rkoller Nürnberg, Germany

    ohhh there is already an issue for, i've missed that one. thank you for the link!

    what the users found confusing about the two buttons? what was their train of thought? or was it solely about the fact that there were in their eyes two "identical" actionable items?

    and i agree. i am kind of drawn between the two options i've added to the proposed resolutions. i've applied the patch from the issue you've linked now. with the patch applied things are way more clear and self explanatory on the page (in particular removing the buttons made the bundle section structure more clear - those buttons always felt like a foreign matter flanged on). the only minor downsides that comes to mind you have an extra click for creating a new form or view mode. and if you've edited a view mode in the user bundle section for example and now want to add a new view mode you have to scroll all the way up until you reach the add button. not sure how much of nag those two minor downsides might become for experienced users in their daily usage in the long run.

    on the other hand how often do you create new view or form modes - meaning if you have a clear and actionable interface without any ambiguity it probably still outweighs those two minor downsides?

  • Comment about 1 year ago →
    🇫🇮Finland lauriii Finland

    what the users found confusing about the two buttons? what was their train of thought? or was it solely about the fact that there were in their eyes two "identical" actionable items?

    IIRC it wasn't a major challenge but more along the lines of "Hmm, I'm not sure what's the difference between these two buttons, I'll try to click both of them to see how they are different", concluding that they probably do the same thing.

  • Comment about 1 year ago →
    🇫🇮Finland lauriii Finland

    I don't think there's much of a downside to removing the individual buttons once we have done 📌 Allow user to add display modes from respective field UI's. Needs work because in our testing, vast majority of the users navigated to this page through manage display / manage form display. Maybe we should close this one, and postpone 🐛 Duplicate "Add view mode" buttons RTBC on 📌 Allow user to add display modes from respective field UI's. Needs work ?

  • Status changed to Closed: outdated about 1 year ago
  • Comment about 1 year ago →
    🇩🇪Germany rkoller Nürnberg, Germany

    thanks for the brief summary in #5 📌 Rethink the add view/form mode buttons on the view/form modes pages Closed: outdated .

    and i completely agree with #6 📌 Rethink the add view/form mode buttons on the view/form modes pages Closed: outdated . i'll close this one as outdated (or would duplicate more appropriate not sure but probably doesn't matter much) and also a +1 for postponing 🐛 Duplicate "Add view mode" buttons RTBC on 📌 Allow user to add display modes from respective field UI's. Needs work .

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024