I'd like to see the Help admin/help page:

  • Add a full-help-text search facility, so if I search for "tag" it will show the "Taxonomy" help page title for me.

    This is now a separate issue: #2359519: Make a search plugin for full text help searching

  • Show a summary page with the following information:

    Module name | Version | Link to Help | Link to settings page | Link to Module page at drupal.org | Link to documentation page at drupal.org

Finding Help is vital as it reduces the number of support requests, and the easier it can be done, the better.

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

Full text searching is interesting... unlikely to happen however, as a practical matter.

The second request sounds exactly like the information available now on the Modules page. Why would we want to duplicate it on the Help page? I don't think that is a good idea. These two requests should ideally be two separate issues anyway?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Issue summary: View changes

I've spun off the search question to its own issue, and left this one for the other proposal:
#2359519: Make a search plugin for full text help searching

iantresman’s picture

iantresman CreditAttribution: iantresman commented

Thanks for your comments. You said "Why would we want to duplicate it on the Help page?"

Ideally we wouldn't want to duplicate information, but currently we have several different pages where one page would do. I'm thinking of:

  • Module page
  • Update page
  • Help page

It bugs me that I have click between all three, when an improved layout would cater to all of them. I would find it much easier to have one module page, with icons to (a) Settings (b) Link to Module page at drupal.org (c) Link to documentation page at drupal.org (d) Version number (e) Icon indicating whether there is an update (f) Module name (g) Optional description (h) optional help.

Failing that, even if we duplicate information, it will help newbies, and hence reduce support requests.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

It would help your case for this if you made a proper issue summary, I think. If you click the big green "Update this issue" button, there is a link to the issue summary template. This helps to make an issue into having a more formal proposal, justification, etc. Please :)

iantresman’s picture

iantresman CreditAttribution: iantresman commented

Thanks for that, not seen it before. Thanks for the pointer.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

That link is also visible when you first file an issue. There's a big box at the top asking you to use issue summaries... do you have suggestions about how we could make that more obvious?

iantresman’s picture

iantresman CreditAttribution: iantresman commented

I don't recall how long the box has been there, but I would think a short bit of text at the beginning in red, would indicate that it is important. ie. "New" or "New guideline" or "Important".

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

It's been there for a long time... not new. But maybe we need to consider cutting it down to just the essentials.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Version: 8.0.0-beta1 » 8.1.x-dev

Feature requests are at this point frozen until 8.1.x.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now 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.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now 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.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now 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.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now 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.

JayKandari’s picture

JayKandari
Primary language Hindi
CreditAttribution: JayKandari as a volunteer and at QED42 commented

Any chance of getting this up?

cilefen’s picture

cilefen CreditAttribution: cilefen as a volunteer commented

See #4.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). 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.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now 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: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

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

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now 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.

smustgrave’s picture

smustgrave CreditAttribution: smustgrave at Mobomo commented
Status: Active » Closed (outdated)

Closing this out as outdated as the help module is actually moving to help_topics which offers new features.

Would recommend reviewing that module and see if you have any feedback there.