No major issues with the words in the UI here, but some suggested cleanups for brevity and clarity:
---
Current page help text:
These options control the default display settings for your entire site, across all themes. Unless they have been overridden by a specific theme, these settings will be used.
Proposed:
Control default display settings for your site across all themes. Use theme-specific settings to override these defaults.
---
First details section has a title of 'Toggle display' and 'Enable or disable the display of certain page elements.' as the description. Toggle display is not very descriptive and sounds more like an action instead of a label. The descriptions explains better what's going on. I think we can combine them into a meaningful title and get rid of the description:
Page element display
---
The next two sections for logo and favicon use 'settings' and 'default' unneccesarily. Maybe 'favicon' is the better known term instead of 'shortcut icon'?
Change 'Logo image settings' to 'Logo settings' and 'Shortcut icon settings' to 'Favicon'
---
If you choose to set a custom logo or favicon, the description for the 'Path to…' confuses me. The use of code tags seems unneccessary and adds visual irregularities. Why is the first example one for public, when the second example starts the url with 'public'?
Examples: logo.png (for a file in the public filesystem), public://logo.png, or core/themes/seven/logo.png.
Comment | File | Size | Author |
---|---|---|---|
#28 | Cleanup_in_appearance_settings_2048887.patch | 4.18 KB | Anul |
#21 | AfterApplyingPatch.png | 151.93 KB | Anul |
#20 | interdiff-2048887-16-20.txt | 796 bytes | pguillard |
#20 | appearance_settings-2048887-20.patch | 4.17 KB | pguillard |
| |||
#16 | appearance_settings_after.png | 60.17 KB | pguillard |
Comments
Comment #1
yoroy CreditAttribution: yoroy commentedScreenshot of the current UI.
Comment #2
yoroy CreditAttribution: yoroy commentedLets see…
Comment #3
jhedstrom+1 for this cleanup. Patch needs a reroll though.
Comment #4
rpayanmComment #5
jhedstromI'd say RTBC. Not sure if this needs more review since it is a UI change (is it even possible for 8.0.0 at this point)?
Comment #6
meeli CreditAttribution: meeli commentedNot 100% happy with this! I think we need to be more brutal with this cleanup.
This whole page is sort of spaghetti. We're at Drupal South and I've decided I want to fix it. Here's why:
As for the nitty-gritty:
So I've uploaded a bunch of hand-drawn wireframe prototypes and am currently working on a patch. Very keen for UX team input and excited about making this all better.
If we're keen to move forward with this I'm happy to either update the issue summary or make this a new issue.
Comment #7
Bojhan CreditAttribution: Bojhan commentedI am trying to review this - but struggling a bit. Are there before/after screenshots?
I love all the consistency and thought in this patch :)
Comment #8
yoroy CreditAttribution: yoroy commentedYep, all excellent points. Go for it meeli!
Comment #9
ifrikComment #10
greta_drupal CreditAttribution: greta_drupal as a volunteer commentedI'm finding many inconsistencies throughout all pages. Is there a better way to provide that feedback than a separate issue for each one? Maybe a master user interface text file that could be redlined?
Comment #11
Bojhan CreditAttribution: Bojhan commentedComment #13
yoroy CreditAttribution: yoroy commentedComment #14
ifrikComment #15
pguillard CreditAttribution: pguillard commentedComment #16
pguillard CreditAttribution: pguillard commentedAt least a rerool of #4, and screenshots.
Missing meeli's remarks.
Before :
After :
Comment #17
ifrikThanks pguillard,
the patch does clean up the existing text nicely by getting rid of unnecessary words. I also like the favicon change that still keeps the "shortcut icon" in the help text.
There are much more points raised in #6 but that means a much bigger overhaul of these pages, and beyond the scope of this issue.
So let's just get this in first so that users have a cleaner UI for now, and then proceed to the bigger task as a different issue.
Comment #18
pguillard CreditAttribution: pguillard commentedI'm not going to complain, thank you :p
Comment #19
xjmThanks everyone; all the string changes in this patch look great.
This is a great cleanup!
+1 for making these consistent; that makes the page easier to understand.
Looks like a newline was accidentally deleted here.
NW for fixing that last point.
Comment #20
pguillard CreditAttribution: pguillard commentedOops, new patch removing the newline
Comment #21
Anul CreditAttribution: Anul at Srijan | A Material+ Company commentedReviewed and tested after applying patch. It looks fine.
Comment #23
pguillard CreditAttribution: pguillard commentedThank you @Anul for your review.
Meanwhile, I guess the bot went crazy , I started a new test.
Comment #24
Anul CreditAttribution: Anul at Srijan | A Material+ Company commentedYou are Welcome @pguillard
Have you created a new issue for the same or shall i review it again n move it accordingly.
Comment #25
pguillard CreditAttribution: pguillard commented@Anul, no need to create a new issue, for some reason, the bot didn't launched an error.
Now, yes, you can set it to RTBC if you think it is fine! As I can't on my side.
Comment #26
Anul CreditAttribution: Anul at Srijan | A Material+ Company commentedReviewed and tested after applying patch #20 . It looks fine. Screen shot added in #21..
Comment #28
Anul CreditAttribution: Anul at Srijan | A Material+ Company commentedAs this patch #20 is failing automation testing. I am adding a new patch for the same.
Comment #29
hesnvabr CreditAttribution: hesnvabr commentedI test this patch.It looks fine.
Comment #31
xjmThis looks great now. Committed 43f4378 and pushed to 8.2.x. Thanks!