Problem/Motivation

The help text of the Settings tray module does not follow the Help text standards as described in https://www.drupal.org/help-text-standards.
Also the description on the Extend page, does not follow the standard and it should not contain the word "Drupal"

Proposed resolution

Editing the text according to the standard.

Remaining tasks

  • Edit the headers in the Uses section
  • Edit the Uses descriptions
  • Add the relevant links is the Uses descriptions
  • Edit the module description used on the Extend page.

User interface changes

This is a UI text change

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ifrik created an issue. See original summary.

ifrik’s picture

Issue tags: +user interface text
sourabh.singhal’s picture

Assigned: Unassigned » sourabh.singhal
sourabh.singhal’s picture

Status: Active » Needs review
FileSize
2.92 MB

Hi ifrik,

I have updated the documentation. Please review. Find attached patch.

Thanks
Sourdrup

kiwimind’s picture

Status: Needs review » Needs work
Issue tags: +mssprintjan17
FileSize
2.3 KB

The previous patch file is enormous, including all sorts of seemingly unrelated things.

I've attached the parts of the patch that I think are relevant to this ticket, although I'm not 100% sure that I've got them all.

@sourdrup - was there anything else that you think needed to be captured here? There's more surrounding this text update, although doesn't fall under the documentation realm.

Thanks.

kiwimind’s picture

Status: Needs work » Needs review

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.

ifrik’s picture

Status: Needs review » Needs work

Thanks kiwimind,
for cleaning this patch up.

The help text needs some more work, to describe well what the module doing.

As far as I understand it: the Settings Tray gives users the option to edit some configuration from the frontend if something is placed in a block. The configuration is a mix out of the block configuration, and the configuration of what is "in" the block. I'm not sure how best to formulate that.

Block configuration: Everything with the exception of the visibility and the region. The "advanced options" link at the bottom brings the user the the block configuration page.
Other configuration: For example for the menus, the list of menu items can be edited, but not other configuration. Depending on what is in that block there are links that will bring users to the other admin pages.

Leaving the quick edit mode happens in a number of different ways, so that should be covered in as well.

The Use section should then follow the standard in https://www.drupal.org/docs/develop/documenting-your-project/help-text-s...

ifrik’s picture

Issue tags: +SprintWeekend2017
Pavan B S’s picture

Assigned: sourabh.singhal » Unassigned
Status: Needs work » Needs review
FileSize
2.69 KB

Added two more uses for the module in help text as suggested in #8, Please review the patch and give me suggestions if it is wrong.

dhruveshdtripathi’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
133.44 KB
50.47 KB

Patch Applied. Screenshots attached. PFA

ifrik’s picture

Status: Reviewed & tested by the community » Needs work

Sorry, this text does not follow the Help text standards https://www.drupal.org/docs/develop/documenting-your-project/help-text-s..., and it still needs the module description changed. (See issue summary.)

Pavan B S’s picture

Status: Needs work » Needs review
FileSize
2.85 KB

Modified the patch as per the comment #12, Please review.

dhruveshdtripathi’s picture

FileSize
108.35 KB

The patch applied successfully. The help page looks like this now. @ifrik If the content is OK, then RTBC.

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.

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.

ifrik’s picture

Status: Needs review » Needs work

Re-roll needed.
I'm working it during SprintWeekend 2018

ifrik’s picture

Status: Needs work » Needs review
FileSize
4.32 KB

I've changed the module description on the Extend page, and changed the Help text according to the Help text standards.

ifrik’s picture

Component: documentation » settings_tray.module

Does this describe the functionality correctly, or is there anything missing?

borisson_’s picture

  1. +++ b/core/modules/settings_tray/settings_tray.module
    @@ -21,15 +21,16 @@ function settings_tray_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<p>' . t('The Settings Tray module provides a sidebar to configure blocks directly without leaving the page. For more information, see the <a href=":online-documentation">online documentation for the Settings Tray module</a>.', [':online-documentation' => 'https://www.drupal.org/documentation/modules/settings_tray']) . '</p>';
    

    I don't think we should say sidebar here, as there's work done to make this show on the top of the page for workflow.

  2. +++ b/core/modules/settings_tray/settings_tray.module
    @@ -21,15 +21,16 @@ function settings_tray_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<dd>' . t('When you click the <em>Quick edit</em> link in the contextual links of a block, then a tray opens in the sidebar. Here you can directly edit and save the main block configuration options. See the <a href=":links_help">Contextual links module help page</a> on how to use contextual links.', [':links_help' => Url::fromRoute('help.page', ['name' => 'contextual'])->toString()]) . '</dd>';
    

    Same remark about sidebar.

  3. +++ b/core/modules/settings_tray/settings_tray.module
    @@ -21,15 +21,16 @@ function settings_tray_help($route_name, RouteMatchInterface $route_match) {
    +      $output .= '<dd>' . t('You can access more configuration options by clicking the <em>Advanced block ¶
    +options</em> link in the tray. This loads the default <em>Configure block</em> page. Depending on the block, other configuration options can be accessed by additional edit links in the tray, for example to configure an individual menu link in a menu block. You can also access the configuration page dicrectly by clicking the <em>Configure Block</em> link in the contextual links.') . '</dd>';
    

    The enter should be removed here, typo in directly.

dhruveshdtripathi’s picture

Made changes suggested comment #20. Please review and let me know if those changes are replaced with correct words or not.

Thanks!

Status: Needs review » Needs work

The last submitted patch, 21: 2830834-help-text-settings-tray-21.patch, failed testing. View results

yogeshmpawar’s picture

@dhruveshdtripathi - Can you provide interdiff so that we can check what exactly change from #18 to #21

kiwimind’s picture

There seem to be some reversions here that don't make sense. @ifrik's text has been changed in places so that it doesn't make sense grammatically.

IMO this needs to be redone, starting from #18, without changing too much text, while paying attention to the comments in #20, as some of them have been missed.

ifrik’s picture

Reroll required as well, so I'm woking on it.

ifrik’s picture

Status: Needs work » Needs review
FileSize
4.54 KB

Thanks Borrison for the comment about the sidebar. I've replaced that with "administrative region" both in the help text and in the module description. I've also fixed the typo and declared the url class so that the link to the other help page works.
There aren't any other changes.

I also have no idea what the patch #21 is supposed to be about so I didn't take that into account.
I couldn't do an interdiff because the patch needed a reroll, but there aren't any other changes.

kiwimind’s picture

+++ b/core/modules/settings_tray/settings_tray.module
@@ -18,15 +19,15 @@ function settings_tray_help($route_name, RouteMatchInterface $route_match) {
+      $output .= '<p>'  . t('The Settings Tray module provides an administrative region (tray) to configure blocks directly without leaving the page. For more information, see the <a href=":online-documentation">online documentation for the Settings Tray module</a>.', [':online-documentation' => 'https://www.drupal.org/documentation/modules/settings_tray']) . '</p>';

Got an extra space in here after your initial paragraph tag. (sorry)

+++ b/core/modules/settings_tray/settings_tray.module
@@ -18,15 +19,15 @@ function settings_tray_help($route_name, RouteMatchInterface $route_match) {
+      $output .= '<dd>' . t('You can enter the editing mode for a whole page by clicking the <em>Edit</em> link in the toolbar. The editing mode marks the outline of each blocks and displays the contextual link icons. You can leave it again by clicking on <em>Editing</em>.') . '</dd>';

"The editing mode marks the outline of each blocks" > "The editing mode marks the outline of each block"

Reads nicely like this, just a couple of very minor things.

Thanks.

ifrik’s picture

Fixed the minor things as well.

kiwimind’s picture

Status: Needs review » Reviewed & tested by the community

Nice work @ifrik, all looks good to me.

Patch applies fine, reads well and makes sense.

Happy to RTBC.

tedbow’s picture

Status: Reviewed & tested by the community » Needs review
Related issues: +#2897272: Fix module description, hook_help(), and document module scope in *.api.php file

Hi all thanks for the work on this so.
Sorry as the module maintainer I think I needs more info.

At first the issue seemed to be just about standards but now it is actually changing the help text and description.

In #2897272: Fix module description, hook_help(), and document module scope in *.api.php file we spent a fair amount of time updating the help text to stabilize the module so I think we would need reason to change from that.

I probably should have consolidated these 2 issue together before. I will review this issue and comment again.

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.

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

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.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

Status: Needs review » Needs work
Issue tags: +Needs issue summary update

Sounds like the maintainer needs more info.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.