Problem/Motivation

Sometime in the Drupal 7 cycle, a decision was (apparently?) made that the word "Settings" was out, and "Configure" or "Configuration" was in.

https://www.drupal.org/node/604342#wording

However, we have a lot of pages in the Drupal 8 admin UI that are called "Settings" and/or that have "settings" in their URL.

What should we do about this? Should either:

a) Fix the UI text standards page so it reflects reality... if we do this, then maybe we should also go fix the pages labeled "configure" or "configuration" to say "settings" again? Probably they should all be consistent.

b) Fix the UI so it conforms to the standards -- rename the "settings" pages to be "configure" or "configuration.

Proposed resolution

1. Decide whether the standards or the UI is wrong.

2. Fix the one that is wrong.

Remaining tasks

Decide.
Fix.

User interface changes

A more consistent UI that conforms to our standards.

API changes

None.

Data model changes

None.

Comments

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented
Issue tags: +Needs usability review

This needs a decision from the Usability team.

Bojhan’s picture

Bojhan CreditAttribution: Bojhan as a volunteer commented

Hmm, we use Configuration on the top level and "settings" on the lower levels - I thought

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

Hm... The UI text standards clearly say not to use "Settings".

The current state is quite a mish-mash. For instance:

admin/structure/views/settings -- this is under Structure (it's about Views) but the page title and URL are "Settings" (it's the settings for the Views UI module really). Save button says "Save configuration".

appearance/settings/bartik - This is under Appearance (it's the settings for the Bartik theme). Page title here is "Bartik". Save button says "Save configuration".

And then if you go to admin/config (the Configuration menu page), you have things like:

"Account settings
Configure default behavior of users..."
==> admin/config/people/accounts
"Text formats and editors
Configure how user..."
==> admin/config/content/formats
"Search pages
Configure search pages and search indexing options"
==> admin/config/search/pages
"Logging and errors
Settings for logging..."
==> admin/config/development/logging
"Regional settings
Settings for the site's default time zone..."
==> admin/config/regional/settings
"Image styles
Configure styles that..."
==> admin/config/media/image-styles

So even within some of these items, there's a mix of "settings" and "configure" in the UI text, and some of the URLs have both configure and settings in them. But nearly all of those pages (plus many others), when you get to them, have a "Save configuration" button (unless they're "add a new one" types of pages).

Anyway, I don't see any guidance on the UI text page saying that "settings" is a good name to use or that it's settings lower-level (not sure even what that means).

Bojhan’s picture

Bojhan CreditAttribution: Bojhan as a volunteer commented

@jhodgdon What would be your suggestion? It's kind of difficult as "configuration" can be used nicely in parallel with "Configure" and "Save configuration" which is much more sensible than "Set". However as a title for tabs "Configuration" can be a bit lengthy.

FYI the reason I think this never really got streamlined is because it doesn't create any usability issues. From a standards POV although we want to standardise this.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
CreditAttribution: jhodgdon commented

I have no idea what to prefer. My concern is that we have a documented standard that isn't being followed at all. So we should either get rid of the standard or follow it.

Bojhan’s picture

Bojhan CreditAttribution: Bojhan as a volunteer commented

What about going with "Configure" and use the word "Settings" for the pages that are on the lower levels?

Bojhan’s picture

Bojhan CreditAttribution: Bojhan as a volunteer commented
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

yoroy CreditAttribution: yoroy commented
Issue tags: +ux-interfacetext
yoroy’s picture

yoroy CreditAttribution: yoroy commented
Version: 8.1.x-dev » 8.2.x-dev

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

AaronMcHale’s picture

AaronMcHale
Primary language English
Location Edinburgh, Scotland
CreditAttribution: AaronMcHale as a volunteer commented

The trend definitely seems to be more towards "Configuration"/"Configure" these days.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.