In IRC we were talking, and we figured it would be nice to have a Quick Start block enabled that included things like "Help" (admin/help) and "make this page the front page".

Initial hacking attached

CommentFileSizeAuthor
#1 help_block_0.patch1.51 KBdmitrig01
help_block.patch1.51 KBdmitrig01
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dmitrig01’s picture

dmitrig01 CreditAttribution: dmitrig01 commented
FileSize
help_block_0.patch1.51 KB

minor change

KarenS’s picture

KarenS CreditAttribution: KarenS commented

I think this is a good idea, and a nice name ;) Where would it be displayed exactly and how soon would it show up?

dmitrig01’s picture

dmitrig01 CreditAttribution: dmitrig01 commented

it would get displayed as soon as the installation is complete.

Pancho’s picture

Pancho
Location UTC+2 🇪🇺 EU
CreditAttribution: Pancho commented
Version: 6.x-dev » 7.x-dev

Awesome idea, needs some work though. Need to push this to D7, sorry...

KarenS’s picture

KarenS CreditAttribution: KarenS commented

Bump.

With all the discussion about usability improvements, I think this could be an easy win for getting new users started. Gets us away from "the help page disappears as soon as I create content" problem -- you can leave it there in a block as long as you need it and get rid of it when you don't. The block itself doesn't have to contain everything, just have links to places where you can get more help. It could even just be a great big gigantic 'Help' button that takes you to a permanent version of the help text we now put on the front page.

That alone would be helpful, but we could build in some simple logic. Check if they have created any users or not, and if not suggest they create a user. Check if they have created any user roles or not, and if not, suggest they create a role. Check if they have created any content, and if not, guide them to the 'Create content' page. Etc. Etc. The list could get shorter as they do things, or change to green checkboxes to indicate the task is done, or whatever.

We need to do more work thinking about exactly what would be on it. Looking at the usability studies to figure out the things that most confused people would be a good place to start.

KarenS’s picture

KarenS CreditAttribution: KarenS commented
Title: UI improvement: add a "Quick start" block » Usability improvement: add a "Quick start" block
Component: base system » usability

Changing title...

casey’s picture

casey CreditAttribution: casey commented
Version: 7.x-dev » 8.x-dev
Component: usability » base system

D7 is in alpha fase already.

yoroy’s picture

yoroy CreditAttribution: yoroy commented

Yes.

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.

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

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Issue summary: View changes
Status: Needs work » Closed (won't fix)

This hasn't been pursued in 11 years which indicates there isn't much demand for this change. This looks like something that could be done in the configuration management system.