| Project: | Drupal core |
| Version: | 8.x-dev |
| Component: | user interface text |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Issue Summary
So I've been contributing some small copyediting improvements to the ui text elsewhere, to help Drupal's usability, and want to suggest changes in build/themes.
build/themes currently reads:
Select which themes are available to your users and specify the default theme. To configure site-wide display settings, click the "configure" task above. Alternatively, to override these settings in a specific theme, click the "configure" link for that theme. Note that different themes may have different regions available for displaying content; for consistency in presentation, you may wish to enable only one theme.
To change the appearance of your site, a number of contributed themes are available.
See the available updates page for information on installed modules and themes with new versions released.
I'd like to propose a change to:
Set the default theme, and enable alternative themes to make them available to users. Click the 'configure' tab to change global settings for all themes and to override these settings for specific themes.
Available regions and displayed blocks may differ between themes; for consistent presentation you may wish to enable only one theme.
To change the appearance of your site, a number of contributed themes are available.
For information on installed modules and new theme versions, see the available updates page.
If you look closely at build/themes, I think my revision reads more clearly in usage and grammar, and reflects more accurately the purpose and use of the page.
I changed the phrase 'different regions available for displaying content' and referred specifically to blocks; but someone should confirm that I'm not leaving out some other theme-determined content display. Also I've made reference to the Configure tab more accurate.
If I can get a more experienced person to support these changes, I will add the style code, roll this into a patch, and upload it.
-- willhall
Comments
#1
I think this is a good change. My only comment is that it relies on someone to know the difference between the "configure" tab (global settings) and the "configure" link on individual themes. Or actually, now that I re-read it, I'm not sure the new version really addresses the "configure" link on individual themes. Of course, even if they click the "configure" tab, they'll get an option to select individual themes (as tabs) on the displayed page.
#2
You're right. I was struggling with how the two pages are themselves confusing, as you have a Configure tab and a configure link, and the link takes you to pages in the tab.
Below 'operations,' the 'configure' link should probably be 'settings.' This would make it consistent with the Configure tab page, where you have 'global settings,' then each theme's name.
The help text therefore raises the question of improving the overall interface, to avoid compounding the problem.
Technically here is what is going on:
With this version, the confusion of 'configure tab' and 'configure link' becomes more glaring, but it might be easier to understand than, as you note, failing to mention the 'configure' link.
And what about eliminating unnecessary words in the last two sentences?
Also, "wish" keeps jumping out at me. Change to "want," so it reads:
#3
I'm still new to rolling patches, have been trying things out with Textmate, but don't have much confidence. The patch revisions I submitted on other threads had failures; I think it might have been a file name convention error, so I re-submitted them. If someone can help out that would be great.
- Will
#4
I've only glanced at them, but they both seemed fine. I'll look at them closer the first chance I get.
#5
This is still a valid issue, even though the original text on the themes (appearance) UI has changed. See attached screenshot for how it is in 7.0.