Contrib.social

UX review of the finished, semver-compliant update status report for how it presents the Drupal 8.9 and 9.0 updates for users on various versions

Open on Drupal.org →
Created on 29 April 2020, about 4 years ago
Updated 11 April 2023, about 1 year ago

Problem/Motivation

Core's Update Manager recently got a lot of love to prepare for Drupal 9:
- Contrib projects can potentially be compatible with multiple major versions of core.
- Contrib projects can now use SemVer version numbers.
...

Part of the 9.0.0 release blocking plans ( #3110198: [META] Beta targets following Drupal 9.0.0-beta1 and 8.9.0-beta1 → for more) included the line:

"UX review of the finished, semver-compliant update status report for how it presents the Drupal 8.9 and 9.0 updates for users on various versions"

That's what this issue is for.

Proposed resolution

Do a thorough UX review of the 2 main Update manager pages:

/admin/reports/updates ("Available updates" -- the main "Update status" report page).
/admin/reports/updates/update ("Updates" -- the form to install missing contrib updates).

Remaining tasks

  1. Get a bunch of screenshots together for both pages in various states of currently-installed and what's available.
  2. Do a formal UX review.
  3. Open child issues for anything that needs fixing / changing before 9.0.0 final.

User interface changes

TBD. Hopefully none. ;)

API changes

TBD, probably none.

Data model changes

TBD, probably none.

Release notes snippet

TBD, probably none.

📌 Task
Status

Active

Version

10.1 ✨

Component
Update  →

Last updated about 12 hours ago

  • Maintained by
  • 🇺🇸United States @tedbow
  • 🇺🇸United States @dww
Created by

🇺🇸United States dww

Live updates comments and jobs are added and updated live.
  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • Comment about 1 year ago →
    🇬🇧United Kingdom catch

    This would still be good to do, but it's a not a Drupal 9 release blocker any more given we've already released both Drupal 9 and Drupal 10 since it was opened. Moving down to major. It's possible this will get overhauled again via package manager and friends.

  • Comment about 1 year ago →
    🇺🇸United States dww

    FWIW, I don't think package manager, project browser or autoupdates will change the UI of the existing available updates report at all (AFAIK), and this issue is about that report (and related: any warnings on the site-wide status report page).

    That said, agree with the downgrade to major, since we're clearly "happy enough" with the current UI to have shipped 9.0.0 and 10.0.0. 😅

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024