The help text in "Promotion Options" is not user friendly.
It currently says
Promote
A boolean indicating whether the node should be displayed on the front page.
Sticky
A boolean indicating whether the node should be displayed at the top of lists in which it appears.
Change the help text to say
Promote
Show this content in featured regions or lists.
Sticky
Show this content at the top of lists.
OR
revert to D7 wording which simply had labels with no description.
Yes.
Possibly?
| Issue category | Bug because introduces confusing terminology. D7 had a very simple checkbox. This adds technical programming or search terminology to a simple flag. |
|---|---|
| Prioritized changes | The main goal of this issue is usability. |
On the node form, within Promotion Options the description for the Promote checkbox is "A boolean indicating whether the node should be displayed on the front page." and similar for the Sticky checkbox.
Boolean in particular is not a word we should expect content creators to know. I'd also argue that as a content creator followed a link to 'Add Content' that we should use the word content rather than node throughout the interface text on node forms.
| Comment | File | Size | Author |
|---|---|---|---|
| #20 | PromotionOptions-fixed.png | 48.35 KB | kattekrab |
| #16 | Screen Shot 2015-01-20 at 3.32.49 pm.png | 63.44 KB | kattekrab |
| #11 | 2350013-promotion-options-11.patch | 3.19 KB | David_Rothstein |
| #5 | 2350013-promotion-options-5.patch | 3.14 KB | kattekrab |
| #1 | boolean.png | 15.42 KB | kattekrab |
Comments
Comment #1
kattekrab commentedI agree the help text in the "Promotion Options" Tab when adding content could be more user friendly.
Currently, it says
PROMOTION OPTIONS
Promote
A boolean indicating whether the node should be displayed on the front page.
Sticky
A boolean indicating whether the node should be displayed at the top of lists in which it appears.
Whilst that's probably the most accurate description... perhaps we could try
Promote
Show this content on the front page.
Sticky
Show this content at the top of any lists in which it appears.
Comment #2
dawehnerAdding a related issue
Comment #3
kattekrab commentedAhaa! Given the related issue suggests removing "front page" terminology, then I'm changing my suggestion to
Promote
Show this content in featured regions or lists.
Sticky
Show this content at the top of lists.
Comment #4
kattekrab commentedComment #5
kattekrab commentedAnd... a patch!
And... an "after the patch is applied" screenshot.
Comment #6
kattekrab commentedComment #7
kattekrab commentedComment #8
kattekrab commentedUpdated IS with screenshot, link to patch, and more details about the issue.
Comment #9
jibranWell code changes looks good. I like the updated text. Let's see what @webchick thinks about it.
Comment #10
jibranAnd thank you @kattekrab for so much detailed issue summary, screenshots and patch.
Comment #11
David_Rothstein commentedI don't think the "front page" wording should be removed (at least not just in this one single place - I seem to recall that #987242: The "Promoted to front page" checkbox doesn't do anything if the /node front page listing isn't used discusses removing it everywhere but that's a separate issue).
Why not just use the same wording that Drupal 8 already uses at admin/structure/types/manage/article (and that Drupal 7 uses in both places)? That is, no description at all, but with more information in the checkbox label itself.
The attached patch implements that.
Comment #12
kattekrab commentedThat could work.
Was there a reason these had been changed from what they were in D7 to a single word with a description?
Comment #13
David_Rothstein commentedGood question. I used git bisect (http://webchick.net/node/99) to find out when that text was removed from Drupal 8. Looks like it happened in #2226493: Apply formatters and widgets to Node base fields... As far as I can tell that issue was not intending to change the UI text, so I think it was just a mistake.
Comment #14
rootworkI'd support either #11 or #5 over what we have now. I could see arguments for either.
Comment #15
kattekrab commentedEither is fine. What we have now isn't good. I reckon we just need someone to make a call and do it. :)
Comment #16
kattekrab commentedI'd probably err on the side that less is more. Here's the two approaches side by side.
Comment #17
kattekrab commentedComment #18
kattekrab commentedComment #19
kattekrab commentedComment #20
kattekrab commentedoops - got the numbers in the comparison screenshot round the wrong way. fixed!
Comment #21
gábor hojtsy#11 looks much better, thanks!
Comment #22
berdirYes, this is one of the issues that I mentioned in #2363099: Using translated field definition descriptions in entity schema results in different schema definitions, resulting in update.php changes, which remove those descriptions from the schema.
In HEAD, we would also lose the description in the schema, but with that patch, we never add them like that anymore, so it doesn't matter.
Comment #23
alexpottCommitted a801764 and pushed to 8.0.x. Thanks!
Thank you for adding the beta evaluation to the issue summary.