Improve theme description and screenshot alt-text for usability

I know of only one blind site admin and, unfortunately, he does not use Drupal. Do we have someone to test this change?

We could find out what interests people by looking at searches on https://www.drupal.org/project/project_theme.
We then have to weed out the subjective things because everyone labels their themes as powerful, simple.

Responsive is the first thing I would add.

Does it require SASS or composer or anything external? That is something to avoid for many sites.

You can count the number of regions as an indicator of flexibility.

People seem to like grid systems then argue over the specific grid. 960 is probably the most useful option.

Wireframes?

What would be useful and could be checked objectively?

the alt text is probably the most important thing. Personally I want parity with modules, so we can group themes, set dependancies etc, such as require by, requires etc.

Classy has the following description:
description: 'A base theme with sensible default CSS classes added. Learn how to use Classy as a base theme in the Drupal 8 Theming Guide.'

I suggest we reuse the module config link idea for documentation. Make a documentation page a standard requirement for core themes and modules.

documentation:
    url: https://www.drupal.org/theme-guide/8
    title: Drupal 8 Theming Guide

For things like SASS:

uses:
    SASS

SASS could then be selectable in the list.

@perterx, yeah, that would totally awesome, it's horrible how we have to write stuff like this into the description.

IMHO this is the patch

Updated the issue summary to make it easier to follow.
Everything was outlined in detail in #922696: Follow-up: New methods, standards for describing core themes on themes admin page (was Theme screenshots do not have adequate alt text...).
This is just the specific follow up ticket for the work for Bartik.

Patch review of #7

- The screenshot text is correct.
- The new description text is taken from @yoroy's take on the new text which I approve of - see https://www.drupal.org/node/922696#comment-7963475.

My only query is where are the tags used? And what tags do we have to choose from?
I looked at Seven's tags and also asked @lewisnyman and we can't find where these tags are used. I can see the use of them for contrib but are they used/needed for default themes that are not listed on drupal.org in the same way?

About the tags, the patch uses: responsive, fixed width, 3 column, customizable color.

Seven has: multi-column, fluid, responsive, sans-serif, accessible

I can change the tags, what do you think?

Like emma I don't see the point of tags in core themes, they serve no purpose.

FWIW though Bartik is not a fixed width design in the classic sense of a fixed width design.

Other than that I never quite understood what "clean typography" is, I think a better description is that it's minimalist.

Is there actually an issue for using this alt text? If there is can someone please add it as the parent or related issue, otherwise I think we really need to be doing that first.

So I think for this issue we should focus on just the description and the alt text.

We have agreed above that tags might be pointless for core themes, we can spin this discussion off into a separate issue to discuss.

Issue for this #2471619: Remove tags from all core theme.info.yml files.

Alt text concerns

The issue summary stated that the alt text should be as follows ....

1. Every screen-shot has the alt text "Screen-shot for [theme-name] theme".

However in the Seven version of this issue #2193691: New methods, standards for describing Seven themes admin page which had the exact same guidelines, they decided and committed this much more descriptive text as follows...

+alt text: 'Default administration theme for Drupal 8 with simple blocks and clean lines.'

Work to be carried out for this issue:

1. Remove the tags from the patch.
2. Decide if we should change to a more descriptive alt text for Bartik or raise an issue for Seven to tone theirs down.
3. If we keep the current alt text please can we correct "screen-shot" to "screenshot".

I don't see what is the reason for more descriptive alt text. It seems to contain everything that is also in the description?

Work to be carried out for this issue:
1. Remove the tags from the patch.
2. Decide if we should change to a more descriptive alt text for Bartik or raise an issue for Seven to tone theirs down.
3. If we keep the current alt text please can we correct "screen-shot" to "screenshot".

I've removed the tags line and correct 'Screen-shot' to 'Screenshot'. I didn't change the alt text.

I don't see what is the reason for more descriptive alt text. It seems to contain everything that is also in the description?

I'm a little bit confused with this new alt property, +1 for lauriii's comment. Is sth. like "Screenshot for x theme" would be fine for all themes, wouldn't it?

Also that 'alt text' key is not used anywhere that I can see. Using that if present would have to be a separate issue if it's desired.

The alt text is currently auto-generated and is already "Screenshot for Bartik theme" - only difference is there is no period.

Ugh, this sounds horrible. I have no idea what half of this really means "clean typography" "mobile-first? - not true". etc.

Isn't the fact that this shows the flexibility of Drupal the reason, we want people to see this? Design wise there are good attributes, but I don't think typography plays such a central role.

I agree, what was I thinking! :-)

Is "Provides multiple regions for layout flexibility. The color scheme can be customized." better?

@Roy Going to art school, this should be our speciality. I do really like when it comes to the aesthetic talking about the intend.

"Default theme with multiple regions for content that provide layout flexibility. Using.... "

Anyone can pick this up, doesn't specifically needs ux review.

I'm in DrupalCon 2016 New Orleans, mentored sprints, going to review this.

I'm in DrupalCon 2016 New Orleans, mentored sprints, going to review this.

I took some text from #23 and added to the description. I also added that it is the default theme for Drupal 8. I did pair a programming with Unitoch and cdyksrtra.

I did pair a programming with Unitoch and jasonPivot at DrupalCon NOLA 2016.

+++ b/core/themes/bartik/bartik.info.yml
@@ -14,7 +14,7 @@
+description: 'A default theme included with every Drupal site. A responsive theme with multiple regions for content that provide layout flexibility.'

The second sentence reads a bit awkwardly to me. Another suggestion:

A responsive theme with multiple content regions for creating flexible layouts.

According to #35

+1 for RTBC

On applying the patch #38 with git apply gives error. On drupal 8.2.x-dev branch.

Updated patch.

This issue is already fixed.

@rajeshwari10 thanks for looking into this. This issue hasn't been fixed yet so I'm reopening it. To give a couple tips: If it were fixed it would be helpful for you to point to an issue where this has been fixed, and in that case this would be closed as a duplicate issue (ideally with a reference made via the related issues field to/from the duplicate issue). Also the status of Closed (fixed) shouldn't be set by a human, that is only to be used by the system for issues that are set to 'Fixed' and have no activity after 2 weeks.

Unable to apply patch. Tried patch reroll as well.

No reason why patch is failing. So uploading patch again.

Thanks everyone for contributing to this issue.

It has been quiet here for over 5 years and Olivero has been added and soon Claro. If the scope of this was changed to cover all themes then this can be fixed in one issue. And as a reviewer, it would a lot easier to review the changes to all the themes as once. This is similar to how the coding standard issues are done. With that in mind I have taken a bold step and updated the Issue Summary and Title.

Settings to NW for adding improvements to the text for all themes. Changing component to what I think is a better fit. Unassigning as well because it has been over 5 years.

Hope this helps get this moving again!