Revamp descriptions of items in handler listings

Created on 5 November 2012, over 12 years ago
Updated 30 January 2023, about 2 years ago

Problem/Motivation

Text in the Views interface doesn't follow suggestions and guidelines documented in User interface guidelines: Interface text. Most of this originates from the desire to have descriptions for everything. Ideally there is only a description where its truly needed. I suggest at large we evaluate this help text.

This text can be found when you for example "Add fields", "Add contextual filters". "Relationships". Its the text in those UI's we are trying to solve.

  • Display all taxonomy terms associated with a node from specified vocabularies.
  • The date the content was posted.
  • Appears in: node:article, node:recipe. Also known as: Content: Image, Content: Picture of recipe.
  • Date and time of when the last comment was posted.

Proposed resolution

Evaluate and write new descriptions for all of this, we should quickly analyze what trends are going wrong. For example:

  • Post date:The date the content was posted. -> Remove description
  • Appears in: node:article, node:recipe. Also known as: Content: Image, Content: Picture of recipe. -> Appears in content types Recipe and Article.

At large it should remain within 140 characters a rule of thumb we use for most descriptions to make sure people read them and in this case also to make sure the table doesn't wrap.

Remaining tasks

This issue needs to be split off in achievable novice tasks. For example evaluating per category.

📌 Task
Status

Needs work

Version

10.1

Component
Views UI 

Last updated 4 days ago

Created by

🇳🇱Netherlands Bojhan

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

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

  • VDC

    Related to the Views in Drupal Core initiative.

  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

  • 🇮🇳India kkalashnikov Ghaziabad, India

    Patch #54 is working fine for Drupal version 10.1.x

  • Status changed to Needs review about 2 years ago
  • 🇮🇳India kkalashnikov Ghaziabad, India
  • Status changed to Needs work about 2 years ago
  • 🇫🇷France nod_ Lille

    It does not apply with git apply, which is what the bot uses to check.

  • Assigned to bhanu951
  • Issue was unassigned.
  • Status changed to Needs review about 2 years ago
  • Status changed to Needs work about 2 years ago
  • 🇺🇸United States smustgrave

    Was previously tagged for tests which still need to happen.

  • 🇳🇿New Zealand quietone

    This was tagged for a test in #14 for an error case. That change is no longer in the patch, so there is no need to test it, removing tag.

    Since this is changing the UI it should have before/after screenshots, available from the issue summary.

  • Pipeline finished with Canceled
    4 months ago
    Total: 141s
    #353257
  • Pipeline finished with Canceled
    4 months ago
    Total: 126s
    #353260
  • Status changed to Needs review 4 months ago
  • 🇮🇳India bhanu951

    Rebased against latest head and moved changes oops hook files

  • Pipeline finished with Failed
    4 months ago
    Total: 597s
    #353262
  • 🇺🇸United States smustgrave

    Probably needs usability sign off

  • Status changed to Needs work about 2 months ago
  • 🇺🇸United States benjifisher Boston area

    When you tag an issue for usability review, please make it easy for the usability team to review the issue. Update the issue summary:

    • The "Proposed resolution" section should describe all the changes made in the issue.
    • The "User interface changes" should show the existing UI and the proposed UI.
    • The "Remaining tasks" should include one explaining the usability issue(s).

    Most of the time, I prefer to have plain text in the "Proposed resolution" section and screenshots in the "User interface changes" section.

    You can also attend the weekly usability meeting to present an issue.

    I am adding the tag for an issue summary update and setting the status to NW.

Production build 0.71.5 2024