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.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

yoroy’s picture

FileSize
205.3 KB

Screenshot of the current UI.

yoroy’s picture

Status: Active » Needs review
FileSize
4.48 KB

Lets see…

jhedstrom’s picture

Status: Needs review » Needs work
Issue tags: +Needs reroll

+1 for this cleanup. Patch needs a reroll though.

rpayanm’s picture

Status: Needs work » Needs review
Issue tags: -Needs reroll
FileSize
4.36 KB
jhedstrom’s picture

I'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)?

meeli’s picture

Not 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:

  • Field label names are weird, as described in this issue. But they're not weird because they're just "not right", they're weird because the whole UX of this page is weird. We're trying to put lipstick on a pig here and I think we should change the UX properly. This page has needed some love for years.
  • Under "Toggle Display" we have a mish-mash of different things that seem to be in the wrong order and not all configurable from this screen. eg. Logo, site name, site slogan and favicon seem like they should be grouped and then user pictures in posts, user pictures in comments, user verification status in comments seem like they should be grouped (and also probably do not belong on this page because I may not have users, posts or comments so considering how top-level this page is I think it's a bit out of date.)
  • I can un-check logo and I am able to configure my custom logo. But if I uncheck site name, I can't configure a site name. I have to go to the Site Information section to configure my site name and slogan. Surely the pattern for turning on logo display configuring my logo and turning on the site name display and configuring my site name should be the same. Especially because there is literally nowhere on this page that tells me that I should go to Site Information to configure site name and slogan.
  • User settings should be in at least a different fieldset from logo/name/slogan/favicon settings but possibly even on a different form. Is this "appearance" section trying to do too much? Is this really an aggregation of all things we can turn on and off in the Drupal UI? I highly doubt that. It seems like this form is trying to do too much for too many different little use cases but has ended up just being a bit confusing.
  • Why are all these fieldsets collapsible? What purpose does it possible serve to collapse any of these fields? They are all un-collapsed by default anyway. Surely it would be easier for people to understand what is happening on this page if they could see that they could add their logo right at the start rather than having to check a box to see that functionality is available to them.

As for the nitty-gritty:

  • Need to make it clear that linking to an icon and uploading an icon won't both work. Should be radio buttons, they shouldn't be both available.
  • No point in calling it both a "shortcut icon", a "favicon" and a "favicon image". Choose one, I choose "shortcut icon" because that's apparently the standard and not biased towards Microsoft.
  • I actually think the text at the top of the screen was better before this edit. The edit has assumed knowledge about "theme-specific settings" which is a bit developer-y and might confuse someone new.
  • Choose "logo" or "logo image" but not both. I'm choosing just "logo".
  • Not convinced that "Page element display" is a good phrase. How about "Site branding"? Then underneath, the labels for the checkboxes can be
    • Show a logo - which pops down options to upload your logo, etc.
    • Show a site name - same as above.
    • The description can be modified to actually describe where these things are being "shown" - for Branding, these things are being shown on every page.

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.

Bojhan’s picture

I am trying to review this - but struggling a bit. Are there before/after screenshots?

I love all the consistency and thought in this patch :)

yoroy’s picture

Yep, all excellent points. Go for it meeli!

ifrik’s picture

Issue tags: +Barcelona2015
greta_drupal’s picture

I'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?

Bojhan’s picture

Issue tags: -Needs usability review

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

yoroy’s picture

Version: 8.1.x-dev » 8.2.x-dev
Issue tags: +ux-interfacetext
ifrik’s picture

Issue tags: +DevDaysMilan
pguillard’s picture

Assigned: Unassigned » pguillard
pguillard’s picture

Assigned: pguillard » Unassigned
Status: Needs work » Needs review
FileSize
4.23 KB
74.4 KB
60.17 KB

At least a rerool of #4, and screenshots.
Missing meeli's remarks.

Before :
Before

After :
after

ifrik’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +String change in 8.2.0

Thanks 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.

pguillard’s picture

I'm not going to complain, thank you :p

xjm’s picture

Status: Reviewed & tested by the community » Needs work

Thanks everyone; all the string changes in this patch look great.

  1. +++ b/core/modules/system/src/Form/ThemeSettingsForm.php
    @@ -152,9 +152,8 @@ public function buildForm(array $form, FormStateInterface $form_state, $theme =
    -      '#title' => t('Toggle display'),
    +      '#title' => t('Page element display'),
           '#open' => TRUE,
    -      '#description' => t('Enable or disable the display of certain page elements.'),
    

    This is a great cleanup!

  2. +++ b/core/modules/system/src/Form/ThemeSettingsForm.php
    @@ -210,10 +209,9 @@ public function buildForm(array $form, FormStateInterface $form_state, $theme =
    -        '#title' => t('Shortcut icon settings'),
    +        '#title' => t('Favicon'),
    
    @@ -223,7 +221,7 @@ public function buildForm(array $form, FormStateInterface $form_state, $theme =
    -        '#title' => t('Use the default shortcut icon supplied by the theme'),
    +        '#title' => t('Use the favicon supplied by the theme'),
    
    @@ -242,7 +240,7 @@ public function buildForm(array $form, FormStateInterface $form_state, $theme =
    -        '#title' => t('Upload icon image'),
    +        '#title' => t('Upload favicon image'),
    

    +1 for making these consistent; that makes the page easier to understand.

  3. +++ b/core/modules/system/src/Form/ThemeSettingsForm.php
    @@ -210,10 +209,9 @@ public function buildForm(array $form, FormStateInterface $form_state, $theme =
    -        '#description' => t("Your shortcut icon, or 'favicon', is displayed in the address bar and bookmarks of most browsers."),
    -        '#states' => array(
    +        '#description' => t("Your shortcut icon, or favicon, is displayed in the address bar and bookmarks of most browsers."),        '#states' => array(
    

    Looks like a newline was accidentally deleted here.

NW for fixing that last point.

pguillard’s picture

Status: Needs work » Needs review
FileSize
4.17 KB
796 bytes

Oops, new patch removing the newline

Anul’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
151.93 KB

Reviewed and tested after applying patch. It looks fine.

AfterApplyingPatch

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 20: appearance_settings-2048887-20.patch, failed testing.

pguillard’s picture

Status: Needs work » Needs review

Thank you @Anul for your review.
Meanwhile, I guess the bot went crazy , I started a new test.

Anul’s picture

You are Welcome @pguillard
Have you created a new issue for the same or shall i review it again n move it accordingly.

pguillard’s picture

@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.

Anul’s picture

Status: Needs review » Reviewed & tested by the community

Reviewed and tested after applying patch #20 . It looks fine. Screen shot added in #21..

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 20: appearance_settings-2048887-20.patch, failed testing.

Anul’s picture

Status: Needs work » Needs review
FileSize
4.18 KB

As this patch #20 is failing automation testing. I am adding a new patch for the same.

hesnvabr’s picture

Status: Needs review » Reviewed & tested by the community

I test this patch.It looks fine.

  • xjm committed 43f4378 on 8.2.x
    Issue #2048887 by pguillard, yoroy, Anul, rpayanm, meeli, ifrik, Bojhan...
xjm’s picture

Status: Reviewed & tested by the community » Fixed

This looks great now. Committed 43f4378 and pushed to 8.2.x. Thanks!

  • xjm committed 43f4378 on 8.3.x
    Issue #2048887 by pguillard, yoroy, Anul, rpayanm, meeli, ifrik, Bojhan...

  • xjm committed 43f4378 on 8.3.x
    Issue #2048887 by pguillard, yoroy, Anul, rpayanm, meeli, ifrik, Bojhan...

Status: Fixed » Closed (fixed)

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