Problem/Motivation
"Local tasks" is jargon. The local tasks menu is exposed to a wide variety of users with varying levels of technical knowledge. It would be better to use a term which would be more easily recognized by users at all levels of knowledge.
While challenges for user use of the current term can be remediated through training, it adds to cognitive load for editors as they have to confront this unfamiliar term each time they want to do something with content or their user record.
I will disclose that I was totally mystified by this label when the administrator added this module to our website (and hid the on-page view/edit/delete/revisions menu items). I consider myself technically knowledgeable. However, I tend not to be the sort of person who clicks things that appear meaningless to me just to find out what they do.
Steps to reproduce
1. Go to https://simplytest.me
2. In the entry field, type admin_toolbar
3. Choose Admin Toolbar
4. Click Launch Sandbox to create the site
5. Login as admin
6. From the top menu, click Extend
7. In the search field, type toolbar
8. Check Admin tool bar extra tools
9. Click Install
10. From the top menu, choose Configuration, then User interface, then Admin Toolbar Tools
11. Check Enable/Disable local tasks display
12. Click Save configuration
13. From the top menu, choose Admin, then View
Expected result: The newly added menu containing View, Shortcuts, and Edit has a label that would be meaningful to a non-technical person
Actual result: The newly added menu containing View, Shortcuts, and Edit has a label "Local tasks"
14. From the top menu, choose Manage, then Content, then Add content, then Basic page.
15. Type title "Test content"
16. Click Save
Expected result: The newly added menu containing View, Edit, Delete and Revisions has a label that would be meaningful to a non-technical person
Actual result: The newly added menu containing View, Edit, Delete and Revisions has a label "Local tasks"
Proposed resolution
Replace "Local tasks" with something less technical, perhaps:
For user entity, "This User"
For content entity, "This Content"
This would carry through to whatever type of entities are supported by this module. I did not use the word "entity" in the proposed resolution because that too is jargon.
If it has to be a single term, I would recommend "This Content" since it is all some kind of content, just not necessarily published website content.
Remaining tasks
User interface changes
See Proposed resolution
API changes
Data model changes
Issue fork admin_toolbar-3436899
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
charles belovComment #3
charles belovComment #4
charles belovComment #5
charles belovComment #6
yannickooFYI I just created another issue to adjust Local tasks to allow editors faster editing of content – #3495223: Link "Local Tasks" button directly to entity edit form if available to improve UX
Comment #9
vasantha deepika commentedReplace "Local Tasks" with "Quick Links" to make navigation more intuitive and user-friendly for non-technical users as well. Raised an MR #108
Comment #10
charles belovThank you for that suggestion. However, as with "Local Tasks," "Quick Links" does not imply it relates to the currently-displayed node.
What about "This Node"?
Although "node" is also jargony.
"This Page" if it's content?
"This User" if it's a user page?
Comment #11
arijit acharya commentedComment #12
arijit acharya commentedHi @charles belov, I have thought to rename the display of 'Local tasks' to 'Contextual Tools', raised the MR as well for it.
The reason for selecting this name is that it clearly conveys that the menu provides tools specifically related to the current context.
Please review and share your opinion on it.
Comment #13
charles belov@arijit acharya Thank you for your suggestion. Again, "Contextual" strikes me a jargony and not meaningful to the average content editor. The simpler, yet meaningful, language the better. I don't think of pages as being a "context", I think of it as being the current page. I don't think of users as being a context, I think of it as being a user.
I'd really like to see something simple and straightforward like:
This page
This user
I also don't think of the various actions available as "tools".
Comment #16
dydave commentedThanks a lot everyone for all the contributions!
Created a new merge request at #15 as an attempt to implement the changes suggested in the issue summary and the previous exchanges.
See resulting screenshots:

Node page:
/node/NIDUser page:

/user/UIDI personally think this is a very good idea and should definitely make things clearer for less tech-savvy users.
Therefore, I wouldn't be opposed to getting something like this included in the module, if this issue could get enough interest.
Any comments, testing feedback or questions would be greatly appreciated.
Thanks in advance!
Comment #17
dydave commentedComment #18
yannickooThanks for your effort @dydave! I had to think about this for a longer while and also asked other people what they could easily understand to navigate around easily.
New suggestions that I really like and never saw in Drupal before:
Comment #19
charles belovI like Page Actions, as that most closely describes what the menu contains and will allow editors to accomplish. It says that the menu pertains to the current page and will allow you to do things with that page.
Page Tools would be my second choice.
"Quick Actions" and "Actions" don't work for me because it is not clear that they apply to the current page.
Comment #20
divyansh.gupta commentedTested the patch and it works well. The label updates appropriately based on the type of page you're viewing and falls back to "Local Tasks" when needed. This is a nice improvement for usability and should make things clearer for non-technical users. Marking this RTBC.
Comment #21
charles belovTested the patch on simplytest.me, and I'm not seeing the local tasks menu, either with the old or new wording.
Steps:
1. Go to https://simplytest.me/
2. In the project name Field type admin
3. Choose admin_toolbar from the auto suggest
4. In the version drop down, choose 3.x–Dev (I also tried 3.6.1, with the same result.)
5. Click advanced options
6. Leave Drupal core at 11.2.1
7. In the patch field, paste https://git.drupalcode.org/project/admin_toolbar/-/merge_requests/127.patch
8. Click Launch Sandbox
9. Copy log before it redirects to the site
10. Locate 127.patch in the log
Expected and actual results:
11. Log into the site as admin
Expected result: I am on the admin user page /user/1. I see the following menus, not necessarily in this sequence:
Actual result: I am on the admin user page /user/1. I see the following menus:
12. Go to /admin/config/user-interface/admin-toolbar
Expected and actual result: I see the default options for the admin toolbar module, indicating to me that the admin toolbar module is active.
13. Create a new basic page (Content, Add content, Basic page, type "test" in title field, Save)
Expected result: /node/1 has the following menu items:
Actual result: /node/1 has the following menu items: