This issue is separated from #472126: D7UX: Move buttons to right area, add content and meta selector so as to avoid putting the issue into a "giant, unreviewable patch" state. This patch changes the fieldsets on the "Meta" tab created in that issue to pseudo-collapsible fieldsets that give some information on the current state of the settings, and provides the user with an option to change the current settings. It does not fully represent the mockup created at http://d7ux.org/content - I tried to implement it as cleanly and simply as possible, without undo changes to the underlying code. I think that the interface I've created captures the essence of the idea presented at http://d7ux.org/content, but if the community feels I've left out an important component of the proposal, I would be happy to reroll a patch including it.

Disclaimer: I had to do some version control black magic to roll this patch, so I apologize if there are any mistakes in what is included or not in this patch.

Files: 
CommentFileSizeAuthor
#5 modified-fieldsets-02.patch4.74 KBcwgordon7
Failed: Failed to install HEAD. View
#2 491846-screenshot.png23.8 KBcwgordon7
modified-fieldsets-01.patch4.77 KBcwgordon7
Unable to apply patch modified-fieldsets-01.patch View

Comments

Gábor Hojtsy’s picture

It would probably be useful to present a screenshot of this functionality, so we can easier see what happens (without the need to apply two patches at once).

cwgordon7’s picture

FileSize
23.8 KB

Here's a screenshot:

Dries’s picture

Issue tags: +D7UX

Tagging for later review.

moshe weitzman’s picture

This is a UX improvement? I'm not seeing that at all.

cwgordon7’s picture

FileSize
4.74 KB
Failed: Failed to install HEAD. View

Removed a stray console.log() call.

Status: Needs review » Needs work

The last submitted patch failed testing.

cwgordon7’s picture

Status: Needs work » Needs review

...

Stefan Nagtegaal’s picture

And we are introducing another way of presenting options to a user...
Is it the meaning that we are going to introduce as much possibilities to let a user change things in D7?

We are using vertical tabs to unclutter things, we talk about flooded harmonica's to unclutter things and we are redesigning pages to unclutter things. The current workflow is just plain wrong imo.

- It would be better if we first got Drupal UI right, use the right form elements for the right job and keep those consistent. There were several idea's in the past to do this using a special form function.

- Then look at all the pages and write down the major shared problems. Think and try to make one solution for the problems, which could be re-used over and over again.

Really, not presenting options isn't a usability improvement. The key to succes is to use the right form-elements for the options and keep things consistent around every page.

Frando’s picture

In which way should this have a better UX than vertical tabs? It uses more space for the same information, introduces redundant controls ("change" and "more" are the same, right?) and makes it much much harder to quickly skim the summaries to see what you might want to change (with vertical tabs, the summaries are close to each other while with this approach they're all over the page).

Dries’s picture

@Stefaan -- your feedback is not helpful because it is not constructive. I'd love to see a mockup of what the right form elements are. It is easy to say 'no', but it is a lot more difficult to propose something that is better.

@Frando, it is more scalable than vertical tabs. When you click "more", we can expose more complex settings than would be suitable in vertical tabs. With the current options in the example (i.e. the default options in core) that is not clear because they are pretty simple, but imagine some of the contributed module settings. Some modules add reasonably big form structures, workflows or listings (random example: sign-ups, events, etc). Ultimately, I think this provides more flexibility over vertical tabs and it is going to make it a lot easier to keep the node edit page clean. For example, I'd hate to see modules add fieldsets to the node edit page after we introduced vertical tabs -- mixing them could be really ugly and inconsistent.

Status: Needs review » Needs work

The last submitted patch failed testing.

Bojhan’s picture

Issue tags: +Usability

@Dries I understand your comment, however we shouldn't focus to much on the concept of "write a patch". It's about trying to critize on design concepts so liesa is able to make more informed design decisions...

@Steef Let's not start a new D7UX Project, can you explain what the clutter it creates?

Obviously less should be close - like in the wireframes.

From the mockups I am trying to understand how we handle modules here. How do we? Do we have some examples of modules filling this thing in?

sun’s picture

Version: 7.x-dev » 8.x-dev
xjm’s picture

Component: node.module » node system
Issue summary: View changes

(Merging "node system" and "node.module" components for 8.x; disregard.)

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.