Problem/Motivation

#3041924: [META] Convert hook_help() module overview text to topics for the admin UI-related modules: contextual, help, inline_form_errors, quickedit, settings_tray, shortcut, toolbar, tour module(s).

Proposed resolution

Take the information that is currently in the hook_help module overview section for the module(s), and make sure the information is in one or more Twig help topic files. Steps:

  1. Find the hook_help() implementation function in the core/modules/MODULENAME/MODULENAME.module file(s). For example, for the core Contact module, the module files is core/modules/contact/contact.module, and the function is called contact_help().
  2. Locate the module overview portion of this function. This is located just after some lines that look something like this:
      switch ($route_name) {
        case 'help.page.contact':
    

    And ends either at the end of the function, or where you find another case 'something': line.

  3. We want to end up with one or more topics about the tasks that you can do with this module, and possibly a section header topic. So, read the help and figure out a good way to logically divide it up into tasks and sections. See Standards for Help Topics for information on how to do this.
  4. See if some of these tasks are already documented in existing topics. Currently, all topics are in core/modules/help_topics/help_topics. Note that to see existing topics, you will need to enable the experimental Help Topics module (available in the latest dev versions of Drupal 8.x).
  5. For each task or section topic that needs to be written, make a new Twig topic file (see Standards for Help Topics) in core/modules/help_topics/help_topics. You will need to choose the appropriate module prefix for the file name -- the module that is required for the functionality. Alternatively, if the information spans several modules or if the information should be visible before the module is installed, you can use the "core" file name prefix. For instance, it might be useful to know that to get a certain functionality, you need to turn on a certain module (so that would be in the core prefix), but then the details of how to use it should only be visible once that module is turned on (so that would be in the module prefix).
  6. File names must be MODULENAME.TOPICNAME.html.twig -- for example, in the Action module, you could create a topic about managing actions with filename action.managing.html.twig (and "MODULENAME" can be "core" as discussed above).
  7. Make a patch file that adds/updates the Twig templates. The patch should not remove the text from the hook_help() implementation (that will be done separately).

Remaining tasks

a) Make a patch (see Proposed Resolution section).

b) Review the patch:

  1. Apply the patch.
  2. Turn on the experimental Help Topics module in your site, as well as the module(s) listed in this issue.
  3. Visit the page for each topic that is created or modified in this patch. The topics are files in the patch ending in .html.twig. If you find a file, such as core/modules/help_topics/help_topics/action.configuring.html.twig, you can view the topic at the URL admin/help/topic/action.configuring within your site.
  4. Review the topic text that you can see on the page, making sure of the following aspects:
    • The text is written in clear, simple, straightforward language
    • No grammar/punctuation errors
    • Valid HTML -- you can use http://validator.w3.org/ to check
    • Links within the text work
    • Instructions for tasks work
    • Adheres to Standards for Help Topics [for some aspects, you will need to look at the Twig file rather than the topic page].
  5. Read the old "module overview" topic(s) for the module(s), at admin/help/MODULENAME. Verify that all the tasks described in these overview pages are covered in the topics you reviewed.

User interface changes

Help topics will be added to cover tasks currently covered in modules' hook_help() implementations.

API changes

None.

Data model changes

None.

Release notes snippet

None.

CommentFileSizeAuthor
#77 3095739-77.patch9.02 KBjhodgdon
#77 interdiff-72-77.txt1.45 KBjhodgdon
#74 3095739-73.png98.23 KBkleiton_rodrigues
#74 3095739-73_patch_applied.png36.44 KBkleiton_rodrigues
#72 3095739-72.patch9 KBjhodgdon
#70 interdiff-63-70.txt2 KBjhodgdon
#70 3095739-70.patch9 KBjhodgdon
#63 3095739-63.patch8.91 KBjhodgdon
#63 interdiff-63.patch2.89 KBjhodgdon
#61 3095739-61.patch2.48 KBjhodgdon
#61 interdiff-60-61.txt8.89 KBjhodgdon
#60 3095739-60.patch8.86 KBandypost
#60 interdiff.txt2.88 KBandypost
#59 3095739-59.patch8.95 KBjhodgdon
#59 interdiff-52-59.txt3.16 KBjhodgdon
#57 dYlthRJ - Imgur.png43.85 KBilgnerfagundes
#52 3095739-52.patch8.79 KBayushmishra206
#52 interdiff_35-52.txt1.66 KBayushmishra206
#35 interdiff.txt3.21 KBjhodgdon
#35 3095739-35.patch8.87 KBjhodgdon
#33 interdiff.txt6.57 KBpratik_kamble
#33 3095739-33.patch8.88 KBpratik_kamble
#26 quick-edit-help-topics.png159.19 KBsenthilmohith
#26 help-topics.png254.7 KBsenthilmohith
#26 3095740-twig-files.png541.06 KBsenthilmohith
#26 3095740-patch-apply.png57.9 KBsenthilmohith
#24 3095739-24.patch8.87 KBjhodgdon
#18 interdiff_14-18.txt2.72 KBsiddhant.bhosale
#18 help_topic-3095739-18.patch8.37 KBsiddhant.bhosale
#14 interdiff_03-14.txt13.61 KBsiddhant.bhosale
#14 help_topic-3095739-14.patch8.32 KBsiddhant.bhosale
#4 help_topic-3095739-04.patch8.82 KBsiddhant.bhosale
#13 help_topic-3095739-13.patch8.41 KBsiddhant.bhosale
#11 help_topic-3095739-11.patch8.41 KBsiddhant.bhosale
#3 help_topic-3095739-03.patch0 bytessiddhant.bhosale

Comments

jhodgdon created an issue. See original summary.

siddhant.bhosale’s picture

Assigned: Unassigned » siddhant.bhosale
siddhant.bhosale’s picture

StatusFileSize
new0 bytes

I have made the patch for the above mentioned modules.
Please review.

siddhant.bhosale’s picture

StatusFileSize
new8.82 KB

I have made the patch for the above mentioned modules.
Please review.

siddhant.bhosale’s picture

Assigned: siddhant.bhosale » Unassigned
Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 4: help_topic-3095739-04.patch, failed testing. View results

snehalgaikwad’s picture

I tried this patch, here adding few suggestions.
1. Using the administrative toolbar
- The heading itself says about administrative toolbar it is making confusion with admin toolbar(contrib) and toolbar(core) modules. Need to be explained about toolbar module in detail.

2. How to use the settings tray
- More detailed steps need to be added with navigation

3. Using the quick edit module
- Quick edit file name is not correct, it should me same as module name. Currently it is quick_edit.overview it should be quickedit.overview

4. Managing the shortcut
- Write with goal and detailed steps for shortcuts

pratik_kamble’s picture

@siddhant.bhosale patch is failing. Please have a look at it.

jhodgdon’s picture

The current fail message is:

Topic shortcut.configure is either top-level or related to at least one other top-level topic

What that means is that every topic either needs to be labeled as "top level", or if not, it must be related to a "top level" topic. shortcut.configure is neither. It should probably be marked as "related" to core.ui_components.html.twig, which already mentions the Shortcut module.

A few other comments about the patch:

a) core.administrative_toolbar.html.twig -- this topic is only related to the toolbar module, so it should be in the toolbar namespace, not core (i.e., change the file name). Given that, it shouldn't need to mention that the Toolbar module needs to be enabled (because the topic will be hidden if the module is not on). Note that the core.ui_components topic already gives a one-line summary of this functionality (including mentioning the module).

b) Probably most of the other topics in this patch in the "core" file namespace also need to be moved to other namespaces. If they aren't already mentioned in the core.ui_components topic, you may need to add a line or two to that topic, as part of this patch.

c) Please read the page on help topic standards. This tells what we do and don't want to see in topics, how to divide help text into topics, and the allowed headings. For example, "About" is not an allowed heading in either a task or concept topic. Also, we are not looking for module overviews here -- topics need to either be about tasks or about concepts, not about modules. https://www.drupal.org/docs/develop/documenting-your-project/help-topic-...

siddhant.bhosale’s picture

Assigned: Unassigned » siddhant.bhosale

Thanks for the suggestions @jhodgdon and @snehalgaikwad. Will make the changes.

siddhant.bhosale’s picture

StatusFileSize
new8.41 KB

Hi, I have uploaded the patch with suggestions implemented.

siddhant.bhosale’s picture

Assigned: siddhant.bhosale » Unassigned
siddhant.bhosale’s picture

Assigned: Unassigned » siddhant.bhosale
StatusFileSize
new8.41 KB

Hi, I have uploaded the patch with suggestions implemented and fixed the coding standard.

siddhant.bhosale’s picture

StatusFileSize
new8.32 KB
new13.61 KB

Hi, I have uploaded the patch with suggestions implemented and fixed the coding standard. Also adding the interdiff of patches
help_topic-3095739-04.patch and help_topic-3095739-14.patch

siddhant.bhosale’s picture

Assigned: siddhant.bhosale » Unassigned
Status: Needs work » Needs review

The last submitted patch, 11: help_topic-3095739-11.patch, failed testing. View results

Status: Needs review » Needs work

The last submitted patch, 14: help_topic-3095739-14.patch, failed testing. View results

siddhant.bhosale’s picture

StatusFileSize
new8.37 KB
new2.72 KB

The test case failed as there was one string which was not encoded in {% trans %}. Adding the changes.

ravi.shankar’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 18: help_topic-3095739-18.patch, failed testing. View results

jhodgdon’s picture

It looks like one of the topics has enough of a syntax error that it cannot be viewed. I suggest applying the patch to a live Drupal site and trying to view all the topics in the patch, to figure out which one is the problem. It is always a good idea to do that before you upload a patch anyway. Sometimes viewing the topics inside a Drupal site and reading them will show you problems that you would not see in the code editor.

siddhant.bhosale’s picture

Assigned: Unassigned » siddhant.bhosale
jhodgdon’s picture

Assigned: siddhant.bhosale » jhodgdon

I'm going to make a new patch now, since there has not been a response in a few days...

jhodgdon’s picture

Status: Needs work » Needs review
StatusFileSize
new8.87 KB

Thanks for the patches! Rather than review again, I decided to make a new patch (saves time and is easier for me than explaining what needs to be done and waiting to see if my suggestions are understood). I made a few changes of note in this patch:

a) There is some confusion in the topics between Overview topics and Task topics, and which headings belong where -- see Standards for Help Topics. For example, an Overview topic should not have a Goal, and a Task topic (which has a Goal), needs to have Steps. So for example, the toolbar topic in the previous patch is a mixture of both... not so good.

b) Some of the topics probably we don't need as they are... For example, the topic "Using the toolbar" is actually just an overview of the administrative menu system headings. Which is useful to have, but it is not specific to the Toolbar module or the Toolbar at all. If you go to /admin you will see those same menu items, even if you don't have the toolbar module enabled. So, I think the information is better as a section of the core.ui_components topic, and I moved it there.

c) As stated in previous reviews, we do not want module overview topics or module overview sections. So please please please don't make sections called "What is the xyz module" or "Overview of the xyz module".

d) A core topic should never list as Related a topic that is not in the core namespace. It is better to put the Related link on the other topic.

e) Topic titles should be in "Sentence case" not "Title Case".

With all that in mind, here is a new patch. There were too many changes to make an interdiff file useful, sorry.

senthilmohith’s picture

Assigned: jhodgdon » senthilmohith
senthilmohith’s picture

Assigned: senthilmohith » Unassigned
Status: Needs review » Reviewed & tested by the community
Issue tags: +ContributionWeekend2020
StatusFileSize
new57.9 KB
new541.06 KB
new254.7 KB
new159.19 KB

I have reviewed the patch #24 and it's working fine as we expected in the 8.9.x version. Please find the attached screens.

jhodgdon’s picture

Status: Reviewed & tested by the community » Needs review

"Working fine" is not the review we are looking for (see issue summary for review instructions). I'm setting this back to Needs Review, because I don't think all of the items in the issue summary were probably checked by this reviewer, since they didn't mention what they did.

pratik_kamble’s picture

Assigned: Unassigned » pratik_kamble
pratik_kamble’s picture

@jhodgdon, Thanks for the patch. The patch covers help topics for inline_form_errors, quickedit, settings_tray, shortcut, toolbar, tour, contextual links. LGTM.

pratik_kamble’s picture

Status: Needs review » Reviewed & tested by the community
jhodgdon’s picture

Status: Reviewed & tested by the community » Needs review

Thanks for taking a look! Can you confirm that you followed all the review steps in the issue summary please (such as following all the steps, clicking the links, reading carefully for grammar, HTML validation, etc.)? They are listed in the issue summary at the top of this page, under "Remaining tasks", item (b).

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.

pratik_kamble’s picture

StatusFileSize
new8.88 KB
new6.57 KB

@jhodgdon, I have checked the patch in #24. I have verified the patch using the tasks mentioned for the review process against branch 9.1.

  1. The text is written in clear, simple and in straightforward language.
  2. Validated HTML, no issues found
  3. Links within the text works.
  4. Adheres to Standards for Help Topics.

Verified the grammar for the patch and found few minor issues for punctuation and grammar. Attaching a new patch with correction.

pratik_kamble’s picture

Assigned: pratik_kamble » Unassigned
jhodgdon’s picture

StatusFileSize
new8.87 KB
new3.21 KB

Thanks very much for the careful review! Most of your suggested changes look good. Two exceptions:
a)

-  <li>{% trans %}Find and click the pencil button for the content or setting you want to edit, to open the contextual links for that part of the page. For example, if you want to edit the settings for a block, the pencil button should be in the top-right corner of the block (top-left for right-to-left languages).{% endtrans %}</li>
+  <li>{% trans %}Find and click the pencil button for the content or setting to open the contextual links for that part of the page you want to edit. For example, if you want to edit the settings for a block, the pencil button should be in the top-right corner of the block (top-left for right-to-left languages).{% endtrans %}</li>

This change doesn't look good to me. I think the first sentence doesn't make sense now at all. Maybe we can change it to two sentences:

Find the pencil button for the content or setting you want to edit. Click the button to open the contextual links for that part of the page.

b)

-  <li>{% trans %}<strong>Extend:</strong> Update, install, and uninstall modules.{% endtrans %}</li>
+  <li>{% trans %}<strong>Extend:</strong> Update, install and uninstall modules.{% endtrans %}</li>

Taking the comma out here is incorrect according to the standards of the Drupal project. See https://www.drupal.org/drupalorg/style-guide/content#english and look for "serial comma" in that section.

So, here's a patch that fixes these two things.

pratik_kamble’s picture

Assigned: Unassigned » pratik_kamble
pratik_kamble’s picture

Thanks @jhodgdon for pointing out the issues. Validated both grammar and HTML. Language is also simple and straight forward. New suggested changes LGTM.

pratik_kamble’s picture

Assigned: pratik_kamble » Unassigned
Status: Needs review » Reviewed & tested by the community

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 35: 3095739-35.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

Unrelated test fail in Drupal\Tests\quickedit\FunctionalJavascript\QuickEditIntegrationTest::testArticleNode

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 35: 3095739-35.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

This fail was

Drupal\BuildTests\Framework\Tests\BuildTestTest::testPortMany
RuntimeException: Unable to start the web server.

Looks like a random infrastructure glitch.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 35: 3095739-35.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

Unrelated fail in Drupal\Tests\quickedit\FunctionalJavascript\QuickEditIntegrationTest

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 35: 3095739-35.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

Unrelated fail in Drupal\Tests\jsonapi\Functional\FileTest::testRelated this time.

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 35: 3095739-35.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

Drupal\Tests\media_library\FunctionalJavascript\WidgetUploadTest failed this time.

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.

jhodgdon’s picture

Issue tags: -Novice

This should not really be a Novice issue

catch’s picture

Status: Reviewed & tested by the community » Needs work
  1. +++ b/core/modules/help_topics/help_topics/core.quick_edit.html.twig
    @@ -0,0 +1,18 @@
    +---
    +<h2>{% trans %}Goal{% endtrans %}</h2>
    +<p>{% trans %}Edit content or settings in place on a non-administrative page.{% endtrans %}</p>
    +<h2>{% trans %}What is quick editing?{% endtrans %}</h2>
    +<p>{% trans %}Quick editing is editing either content or settings inline while visiting a non-administrative page. Content quick editing is provided by the core Quick Edit module, and settings quick editing is provided by the core Settings Tray module; both of them require the core Contextual Links module in order to expose the links that let you edit in place on a non-administrative page.{% endtrans %}</p>
    +<h2>{% trans %}Steps{% endtrans %}</h2>
    +<ol>
    

    I'm not sure we need to use 'non-administrative' here. If an entity is rendered normally on an admin page, it will have quick edit links, and it will be possible to edit inline there too. For example you could have a block that shows on admin pages, and quickedit would let you edit that block inline without going to admin/structure/block.

    What this is really trying to say is that you don't have to go to a separate page to edit. I think we could just drop 'while visiting a non-administrative page' and 'on a non-administrative page'.

  2. +++ b/core/modules/help_topics/help_topics/core.ui_components.html.twig
    @@ -4,15 +4,30 @@ top_level: true
    +<p>{% trans %}The administrative menu, which you can navigate by visiting <em>/admin</em> on your site or by using an administrative toolbar, has the following sections (some may not be available, depending on which modules are currently installed on your site):{% endtrans %}</p>
    +<ul>
    +  <li>{% trans %}<strong>Content:</strong> Find, manage, and create new pages; manage comments and files.{% endtrans %}</li>
    +  <li>{% trans %}<strong>Structure:</strong> Place and edit blocks, set up content types and fields, configure menus, administer taxonomy, and configure some contributed modules.{% endtrans %}</li>
    +  <li>{% trans %}<strong>Appearance:</strong> Switch between themes, install themes, and update existing themes.{% endtrans %}</li>
    +  <li>{% trans %}<strong>Extend:</strong> Update, install, and uninstall modules.{% endtrans %}</li>
    +  <li>{% trans %}<strong>Configuration:</strong> Configure the settings for various site functionality, including some contributed modules.{% endtrans %}</li>
    +  <li>{% trans %}<strong>People:</strong> Manage user accounts and permissions.{% endtrans %}</li>
    +  <li>{% trans %}<strong>Reports:</strong> Display information about site security, necessary updates, and site activity.{% endtrans %}</li>
    +  <li>{% trans %}<strong>Help:</strong> Get help on using the administrative interface.{% endtrans %}</li>
    +</ul>
    

    This seems out of scope?

ayushmishra206’s picture

StatusFileSize
new1.66 KB
new8.79 KB

Addressed #51.1 in this patch. Also added an interdiff to reflect that. Please review.

jhodgdon’s picture

Status: Needs work » Needs review

Thanks! The interdiff looks good to me.

Regarding #51.2, I think it is in scope. We are documenting the Toolbar module, and the core.ui_components.html.twig mentions that the Toolbar module displays the admin menu. I think that a section documenting what is in the menu needs to exist in order to document Toolbar fully (and it should be in the help topics somewhere)... We could delay this issue and do that documentation elsewhere (technically it is provided by the System module but we didn't document it when we wrote the system module help topics, so here we are)... I think we should do it here since I think it belongs in this topic that we are adding information to.

jhodgdon’s picture

Status: Needs review » Reviewed & tested by the community

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 52: 3095739-52.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Reviewed & tested by the community

Looks like a random database server error for this fail in Drupal\Tests\workflows\Functional\Rest\WorkflowXmlBasicAuthTest.

ilgnerfagundes’s picture

StatusFileSize
new43.85 KB

I applied the patch and for me everything is correct, rtbc +1

catch’s picture

Status: Reviewed & tested by the community » Needs work
  1. +++ b/core/modules/help_topics/help_topics/core.quick_edit.html.twig
    @@ -0,0 +1,18 @@
    +<ol>
    +  <li>{% trans %}Make sure that the core Quick Edit and/or Settings Tray module is installed. Also, make sure that the core Contextual Links module is installed, as well as a toolbar module (the core Toolbar module or a contributed replacement).{% endtrans %}</li>
    

    Quick edit and settings tray both have explicit dependencies on the contextual links module, so there's no need to make sure that contextual links is installed.

    Settings tray has an explicit dependency on core toolbar, and quickedit doesn't.

    Really the modules are responsible for making sure that they work with the correct dependencies, not the site admin, so I think this bullet can be removed.

  2. +++ b/core/modules/help_topics/help_topics/core.quick_edit.html.twig
    @@ -0,0 +1,18 @@
    +  <li>{% trans %}Find and visit a page on your site that has either content or settings that you would like to edit.{% endtrans %}</li>
    +  <li>{% trans %}Click the contextual links <em>Edit</em> button, which looks like a pencil and is usually located at one end of your toolbar. You should see pencil buttons appear all over your page.{% endtrans %}</li>
    +  <li>{% trans %}Find the pencil button for the content or setting you want to edit. Click the button to open the contextual links for that part of the page. For example, if you want to edit the settings for a block, the pencil button should be in the top-right corner of the block (top-left for right-to-left languages).{% endtrans %}</li>
    

    Can we show the pencil icon here?

jhodgdon’s picture

Status: Needs work » Needs review
StatusFileSize
new3.16 KB
new8.95 KB

Regarding the pencil icon, it is in the CSS for the contextual links module, so themes can override it. So probably we shouldn't call it a pencil icon or if we do, we should say it depends on the theme.

Regarding the modules, on #3121340: Fix up minor copy problems in help topics we will be adding a separate "Who can" section to topics, which covers permissions and modules that need to be installed, so I put this information there and rewrote the topic.

andypost’s picture

StatusFileSize
new2.88 KB
new8.86 KB

Fix url generation with help_topic_link CR https://www.drupal.org/node/3192582

jhodgdon’s picture

StatusFileSize
new8.89 KB
new2.48 KB

Thanks!

I think this needs a bit more thought though. Since the help_topic_link function will put in the actual topic name instead of custom text, we need to make sure the topic name makes sense in context of the sentence where the link goes. I think both of these changes fail in that regard and need to be adjusted. Here's a new patch.

andypost’s picture

Status: Needs review » Needs work

Mixed patch and interdiff names

+++ b/core/modules/help_topics/help_topics/core.ui_components.html.twig
@@ -9,11 +9,11 @@ related:
-  <li>{% trans %}{{ accessibility }}, to enable all users to perform administrative tasks.{% endtrans %}</li>
+  <li>{% trans %}Accessibility features, to enable all users to perform administrative tasks. See {{ accessibility }} for more information.{% endtrans %}</li>
...
-  <li>{% trans %}In-place or <em>quick</em> editing. In-place editing of content is provided by the core Quick Edit module, and in-place editing of configuration is provided by the core Settings Tray module. See the {{ quick_edit }} for more information.{% endtrans %}</li>
+  <li>{% trans %}In-place or <em>quick</em> editing. In-place editing of content is provided by the core Quick Edit module, and in-place editing of configuration is provided by the core Settings Tray module. See {{ quick_edit }} for more information.{% endtrans %}</li>

Looks better, meantime I find having suffixes like (_topic, _link) useful

EDIT For example s/{{ accessibility }}/{{ accessibility_topic }}

jhodgdon’s picture

Status: Needs work » Needs review
StatusFileSize
new2.89 KB
new8.91 KB

Sorry about the mixed-up file names. Not sure what I was thinking! Anyway, here's a patch with suffixes on the variables.

jhodgdon’s picture

I really shouldn't be making patches today apparently. Wrong extension on the Interdiff. ?!?

ankit maurya’s picture

Assigned: Unassigned » ankit maurya
Status: Needs review » Active
Issue tags: -ContributionWeekend2020 +Drupallover
andypost’s picture

Status: Active » Needs review

@jhodgdon thank you!

I think it rtbc again

@ankit1114 please check it

jhodgdon’s picture

Assigned: ankit maurya » Unassigned
Issue tags: +ContributionWeekend2020

Restoring tag that was removed. Please don't remove past event tags, thank you! Also in general, people are asked not to assign themselves on Core issues. Instead, please add a comment explaining that you plan to work on it and giving a time frame, something like:

I am reviewing this patch at the Drupallover event, and will report back within 1 day.

That way if you don't report back, we know that someone else can start working on the issue.

daffie’s picture

Status: Needs review » Needs work

Just 1 remark:
On the page using the administrative interface: Can we change "/admin" to a link in the sentence: "The administrative menu, which you can navigate by visiting /admin on your site or by using an administrative toolbar"

jhodgdon’s picture

Excellent idea -- thanks for reviewing! I can probably make a patch for this tomorrow, unless someone else has time before.

jhodgdon’s picture

Status: Needs work » Needs review
StatusFileSize
new9 KB
new2 KB

This should take care of making that link.

Status: Needs review » Needs work

The last submitted patch, 70: 3095739-70.patch, failed testing. View results

jhodgdon’s picture

Status: Needs work » Needs review
StatusFileSize
new9 KB

Fixed the mismatched em tag. Interdiff -- was:

<p>{% trans %}The administrative menu, which you can navigate by visiting {{ admin_link }}</em> on your site or by using an administrative toolbar, has the following sections (some may not be available, depending on which modules are currently installed on your site):{% endtrans %}</p>

now

<p>{% trans %}The administrative menu, which you can navigate by visiting <em>{{ admin_link }}</em> on your site or by using an administrative toolbar, has the following sections (some may not be available, depending on which modules are currently installed on your site):{% endtrans %}</p>
daffie’s picture

Status: Needs review » Reviewed & tested by the community

I followed the review process as described in the IS.
I all looks good to me.
For me it is RTBC.

kleiton_rodrigues’s picture

StatusFileSize
new36.44 KB
new98.23 KB

Tested the Patch #72 by @jhodgdon, applied successfully and looks good to me.

core.quick_edit.html.twig
core.ui_accessibility.html.twig
core.ui_components.html.twig

RTBC + 1

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.

larowlan’s picture

Status: Reviewed & tested by the community » Needs review
Issue tags: -
  1. +++ b/core/modules/help_topics/help_topics/core.quick_edit.html.twig
    @@ -0,0 +1,19 @@
    +  <li>{% trans %}Click the link to open the contextual links menu, and click <em>Quick edit</em>. An editing form for the settings or content should appear on the page.{% endtrans %}</li>
    

    This functionality relies on the quickedit module being enabled. Should we reference that?

    edit: we do that on the top level page, ignore

  2. +++ b/core/modules/help_topics/help_topics/core.ui_components.html.twig
    @@ -4,15 +4,31 @@ top_level: true
    +<p>{% trans %}The administrative menu, which you can navigate by visiting <em>{{ admin_link }}</em> on your site or by using an administrative toolbar, has the following sections (some may not be available, depending on which modules are currently installed on your site):{% endtrans %}</p>
    

    The items visible will also depend on permissions.

    Should we mention that?

jhodgdon’s picture

StatusFileSize
new1.45 KB
new9.02 KB

Good idea! Here's a very minor update to the patch (which I edited directly to make item 2 from the previous comment say:
... depending on which modules are currently installed on your site, and your permissions

I used the interdiff utility to make an interdiff file too.
[edited this comment to make it less confusing]

daffie’s picture

Status: Needs review » Reviewed & tested by the community

The point (#76.2) of @larowlan has been addressed. Back to RTBC.

larowlan’s picture

Adding issue credits, unchecking @ilgnerfagundes - there's no need to provide screenshots that a patch applies. Unchecking @kleiton_rodrigues who provided a screenshot of a patch applied as well as a screenshot of one of the three topics added in this patch, we already had screenshots at that point. If you disagree with my assessment, please comment and I'll review. Please note https://www.drupal.org/node/2888804 for how we assign credit.

  • larowlan committed 77c7724 on 9.2.x
    Issue #3095739 by jhodgdon, siddhant.bhosale, pratik_kamble, andypost,...
  • larowlan committed 0f7faa6 on 9.3.x
    Issue #3095739 by jhodgdon, siddhant.bhosale, pratik_kamble, andypost,...
larowlan’s picture

Version: 9.3.x-dev » 9.2.x-dev
Status: Reviewed & tested by the community » Fixed

Committed 0f7faa6 and pushed to 9.3.x. Thanks!

Backported to 9.2.x because help topics is experimental.

Status: Fixed » Closed (fixed)

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

quietone’s picture

Adjusting credit as described in #79. I happened to notice that @kleiton_rodrigues was not to be ticked.