Problem/Motivation
The explanation texts on the Configuration page invite the user to do something, for example to manage or configure something.
Some of these texts are somewhat convoluted or confusing.
In some cases, extensive reviewing of the hook_help text of a module has come up with explanations of Uses that are more to the point then the existing link descriptions.
Ban: unclear whether IP addresses are banned within the site (instead of the ban of visits from IP addresses)
Filter: unclear when the filtering happens (help text even explains that wrongly). Plus wrong format
Editor (when Filter is enabled): Confusing and convoluted)
Actions: Description doesn't add anything, so users who don't know what Actions are learn nothing from the description
Locale: not clear that it's both the import of existing translation and custom translation
Proposed resolution
Change the descriptions in the *links.menu.yml files that they are correct, consistent, and follow a common format.
Remaining tasks
Update the link descriptions of the listed modules.
User interface changes
This are UI text changes.
API changes
None.
Data model changes
None.
Beta phase evaluation
| Issue category | Task to improve the link descriptions of a few modules |
|---|---|
| Issue priority | Minor |
| Disruption | None |
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 2578991-link-description-configuration-page-confusing-9.patch | 3.44 KB | ifrik |
| #9 | interdiff-6-9.txt | 477 bytes | ifrik |
| #6 | 2578991-link-description-configuration-page-confusing-6.patch | 3.44 KB | ifrik |
| #6 | interdiff-2-6.txt | 1004 bytes | ifrik |
| #2 | 2578991-link-description-configuration-page-confusing-2.patch | 3.47 KB | ifrik |
Comments
Comment #2
ifrikI've updated the link description for the following modules: Action, Ban, Filter, Editor and Locale.
The Editor change is in the module file because it changes the existing text provided by the filter module.
Comment #3
jhodgdonifrik says we should credit: mairi, snehi, rachel_norfolk for this patch as well as herself.
I think this patch is all good changes. Very straightforward improvements in wording. Thanks!
Comment #4
Bojhan commentedWondering if we can drop all references to "site" throughout Drupal. Also here "for your site"? Kinda obvious.
Comment #5
jhodgdonGood idea. Looking at these specific changes in the patch:
I'm not sure how to reword this to remove "by the site" here... needs an "actor" to mention to execute the actions?
Here I agree we could remove "to the site"
Agreed we could remove "for your site" here.
Comment #6
ifrik1. I agree that for the Actions module "the site" is the actor, and therefore it needs to stay.
2. and 3.: Always happy to remove unneeded words.
Comment #7
Bojhan commentedHow do you feel about referring to the "system" rather than "site" ?
Comment #8
jhodgdonI think for Actions the "system" makes good sense. I think the module description uses the word "system", or at least it does in a patch on a related issue #2570985: Update the module descriptions on the Extend page. Though actually, in my last review there I suggested for the module description:
Allows configuration of tasks to be executed in response to events
This is passive voice; maybe it should be:
Allows configuration of tasks for the system to execute in response to events.
So maybe here we could say:
Create tasks that the system can execute
Thoughts?
The rest looks good.
Comment #9
ifrikSounds good.
I'm offline in the next days, so if this needs more work it would be good if somebody else does the changes.
Comment #10
snehi commented@ifrik thanks for helping. Looks good now.
Any Suggestion anybody.
This is RTBC Now.
Comment #11
webchickLooks like @Bojhan's comments were addressed. Love that we are no longer defining the term with the term itself in most of these. ;P
Committed and pushed to 8.0.x. Thanks!