It seems like hook_help() is probably still appropriate for the Module Overview type of help, which explains in general what a module is/does. Assuming we want such help to exist (and I think we do?), text is an appropriate presentation, in my opinion.

This is being used on the admin/structure/block/add page to note the purpose of the page (which may or may not be necessary, but there it is), and on admin/structure/block/list/* to give a quick overview of the purpose (again, text is good if it's necessary at all), explain how to use the page (Tour could be better for that but concise text is quicker to scan -- maybe need both?), and to provide a link to the demonstrate block regions page (not appropriate for Tour at all).

So... maybe we need both? I don't think Tour sounds like a replacement for Help to me.

I believe we are going to need them both. But that's not to say that we can't use the documentation that is provided in help module to produce some great tips and elevate some of the work that help module does.

The Tour API allows for general introductions to be included in the tour. In the config file they look like this:

tips:
introduction:
id: introduction
plugin: text
label: Adding or Editing a container
body: <p>This form can be used to edit an existing container or add a new container to your site.</p><p>Containers are used to group forums together. For example if you ran a Drupal forum you might create a 'Support' container and include forums for 'Installing Drupal' and 'Getting started' inside the 'Support' Container</p>
weight: "1"

This introduction is not bound to any element and is shown at the start of the tour (I suppose) when a user clicks the help icon.

This introduction could be a good place to move the hook_help information to, although sometimes hook_help tends to be a bit longer than you would wish for the start of a tour, but we could work on that.

I did some tests with the tour introduction tips but could not manage to get it to work, but that may be the subject of another issue.

I doubt if we should allow these two competing help systems together in core.

a) The module overview pages. I don't see exactly how these would be done in tours, since they don't apply to a particular admin page, and I don't think they are really "tours" but really background information. I think this still belongs in hook_help().

b) Help explanations for particular admin pages. These would probably be good as Tours.

By implementing hook_help(), a module can make documentation available to the user for the module as a whole, or for specific paths. Help for developers should usually be provided via function header comments in the code, or in special API example files.

which I read as system level and partly task oriented as module path can have help explained too.

Having a multipage tour on the other hand could make a task oriented guide.

But both lack skill level support like "I'm a novice". Let alone task based skill level as in "I have done this before so now I'm an expert".

Actually, I think this issue has pretty much served its purpose. We've clarified that hook_help() is still needed to provide a textual overview of each module, and to provide summary text at the top of admin pages. Tours are also useful, to provide an interactive introduction to doing tasks. Let's just close this issue, because I think we all agree that tours and help are different, and they don't really duplicate each others' functionality.

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.

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.

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.)

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.)

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.)