The user experience of projects has improved significantly in D7 with the introduction of update manager. However we failed to fully integrate it in terms of the opportunities it brought.

For Drupal 8 the focus is on closing the gaps between finding, installing and updating projects.

Installation

Currently we require the user to go onto d.o and search for the correct project, for many of our users this feels like finding a needle in a hay stack. For Drupal 8 we want to make the final step in making project installation truly easier by introducing a "market" like functionality that users have come to expect.

  1. http://drupal.org/project/project_browser
  2. #1243332: Deploy Project Browser Server and drupalorg_pbs on d.o
  3. #1262774: Suggested modules
  4. #538904: D8UX: Redesign Modules Page

In addition to a more awesome project search model. We would like to fine tune the current installation process, while improvements to the module screen could make a immense impact - we would like to make the experience even better through the market.

  1. #1254128: Unify update pages
  2. Enable projects in the installation process
  3. Install dependencies when they are required
  4. Show database updates
  5. Allow for backup of website

Updating

The process for updating your projects has improved significantly in Drupal 7. But we do not clearly communicate this functionality. The outstanding issues for this are therefor almost only design ones.

  1. #1254128: Unify update pages
  2. Simplify security warnings
  3. #964568: Too many ways to reach the available updates report leads to confusion
  4. #606592: Allow upgrading core with the update manager

Battle plan

All the issues are prioritized by the UX-team its view on how it impacts the overall UX. Given that the list above is quite a lot, we hope to tackle one topic at a time, but also keeping progress on technical hurdles that we need to overcome.

We are looking for feedback on the technical strategy to get this moving and keep it moving, feel free to add new issues and/or structure how to tackle this.

Comments

Bojhan’s picture

Issue summary: View changes

ey

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.

dawehner’s picture

Component: base system » extension system

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.