I did a usability study recently.

5 of 5 thought the Finished/completed screen was anticlimactic. "It's a little sad to see congratulations in a tiny font. It should be more "Yay look what you did!'"

Possible quick solution: skip this page; redirect them to their new site

CommentFileSizeAuthor
#4 commons-skip-last-step-1866832.patch2.14 KBwebchick

Comments

ezra-g’s picture

Issue tags: +user experience

Thanks - adding the UX tag.

lisarex’s picture

Another solution: style the final screen to be a little more interesting: make sure the 'visit your site' link is easier to spot.

Topcheese’s picture

Yes, it is kind of funny. First, you have to squint and lean in closer to read a small link, then after having already stopping twice for input ... you more or less stop again just to shoot the breeze. A redirect for now would be nice, but it wouldn't hurt to plan on adding other options someday, such as

  • Visit Site
  • Import Content
  • Backup site
  • Security Review
webchick’s picture

Status: Active » Needs review
StatusFileSize
new2.14 KB

Here's a patch. Unlike the approach at #1869468: During installation, users were mildly annoyed they immediately had to skip past default English language; streamline this?, it's not possible to simply skip this task of the installer, because that last step is doing all kinds of clean-up stuff. So I overrode the default install_finished() callback to one that does a drupal_goto() at the end and doesn't show any text.

WARNING: This patch includes that one, because they both touch the same area of code.

webchick’s picture

Also, since this really is talking about core's installer, not Commons's, I filed an upstream issue as well: #1870820: Ditch the last page of the installer?

damien tournoud’s picture

We do the same thing in Commerce Kickstart, but we do have some code to not redirect if there are some errors or warnings.

ezra-g’s picture

Status: Needs review » Fixed

I looked into what Commerce Kickstart does and followed their approach so that error messages will be displayed. I incorporated that change along with:

- Removing the deprecated "double feature revert" in commons_revert_features()
- #1869468: During installation, users were mildly annoyed they immediately had to skip past default English language; streamline this?
- #1869442: During installation, users were unsure about including demo content; needs clarification.

Thanks, everyone!

http://drupalcode.org/project/commons.git/blobdiff/a770bc30927685d3a5217...

ezra-g’s picture

One additional change in this commit was putting an array_filter() around the list of Acquia modules specified, since the Acquia Search was being enabled even when that module wasn't checked.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ezra-g’s picture

Version: » 7.x-3.x-dev

Restoring 7.x-3.x version property.