Problem/Motivation

In user testing, after creating a page without a menu link, three participants did not know how to find it or place it.

Most did (eventually) find the "Find Content" page.

Eyetracking showed users were drawn to the filters on the find content page, even though the content was most important.

Suggestion is to reduce the prominence of filters on that page, making the visual focus of this page the content rather than the filters.

Steps to reproduce

Proposed resolution

TBD

Remaining tasks

Postponed on #3070558: Implement bulk operation designs.
Re-evaluate the need for a change when that above issue is committed.

User interface changes

API changes

Data model changes

Release notes snippet

Comments

naught101’s picture

What does "Reduce filter prominence of content overview page" mean?

droplet’s picture

It's the right way, doesn't it ?

There are some issue about redesign the content filters.

naught101’s picture

Status: Active » Postponed (maintainer needs more info)

No, it makes no sense. Please restate your recommendation more clearly.

webchick’s picture

Yeah, sorry. This was in our spreadsheet from the UMN usability testing and these got entered in a hurry. :)

Here's what's meant:
Eyetracking was drawn to the filters on the find content page, even though the content was most important

"Reducing filter prominence" means make the visual focus of this page the content, not the ways to filter it.

webchick’s picture

Status: Postponed (maintainer needs more info) » Active

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.

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

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

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

catch’s picture

The filters still take up a lot of space on admin/content, so this is likely still valid.

pameeela’s picture

Title: When creating a page without a menu, users do not know how to find it or place it. » Reduce prominence of filters on admin/content page
Issue summary: View changes

Updated title and IS for clarity but I give this a big ol' shrug (because I have no idea how to fix it).

longwave’s picture

Version: 8.9.x-dev » 9.3.x-dev
Component: menu.module » node system

This also somewhat depends on the admin theme I think.

I don't think this is anything to do with menus as such, this is node.module's responsibility.

longwave’s picture

Two simple fixes here that might help, but would need usability review:

- put the filters into a collapsible fieldset
- move the action dropdown to the bottom and remove the top action button

pameeela’s picture

I would be strongly opposed to the collapsible fieldset, because I hardly ever use the page without needing the filters and that would be a very annoying extra step. That feels like sacrificing usability of regular/frequent users for the sake of new/unfamiliar users. (Again I don't have a better idea, I just would argue against making it worse for regular users.)

Moving the actions would much less disruptive.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

longwave’s picture

rkoller’s picture

@smustgrave posted the link to this issue over in the #ux channel. I've read through the issue. The two current suggestions were to make the filter section collapsible and to move the action drop down down to the bottom. For the latter there is an issue i've already linked as an related issue (#3070558: Implement bulk operation designs). The issue is actively worked on and is close to the finish. From my perspective perspective it would make sense to wait (aka postpone this issue) until the bulk action lands, and then revisit and see + discuss if the problem of prominence is still relevant or if moving the bulk action was enough.

quietone’s picture

Issue summary: View changes
Status: Active » Postponed

@rkoller, thank you for the prompt reply.

Per rkoller's comment I am postponing this on #3070558: Implement bulk operation designs.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.