Reduce prominence of theme name.

Example: Switch emphasis with parentheses so it says:
Current Theme (Bartik)

Switch tab labels on blocks page to match.

Comments

jefflinwood’s picture

jefflinwood commented

Is this in reference to the user being confused when adding a Block?

We had several observations about how this could be improved after watching the video of the user's session during the Usability talk at Drupal Camp Colorado 2011.

1) The "Add a block" form should default to just the end user site/theme. How many times is someone going to add a block to the admin theme themselves? That separation seemed to confuse the user

2) Region Settings is confusing. What's a region? Structure contains this text: "Configure what block content appears in your site's sidebars and other regions." which is nice, but on the Add a Block, you just get "Specify in which themes and regions this block is displayed." What if we put a reference to sidebars or footers in here?

3) On Blocks, there is a link to "Demonstrate Block Regions (Bartik)". Why isn't this on the "Add a Block" page? What if the demo that it brings up was in Region Settings on Add a Block, and clicking a block region would select it?

Bojhan’s picture

Bojhan commented

I am very intrigued by option 1), I have no idea how to do it - but it sounds like a good idea.

The other ideas sound like home in other issues, because they are not directly related to this labeling issue.

jefflinwood’s picture

jefflinwood commented

I realized later that there were several other issues that really cover my #2 and #3 better than this issue.

The easiest way to do #1 would simply be to hide the administration theme selection on that page - make "Add an admin block" a separate link on "Blocks"

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.

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

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.

marcusattxc’s picture

marcusattxc commented
Issue summary: View changes
Status: Active » Closed (outdated)

Theme names can be changed on your site if need be. Besides, these particular theme names are Drupal classics at this point.

marcusattxc’s picture

marcusattxc commented