The color module preview image keeps being misinterpreted as a live preview of the user's actual site with their content, visual changes, logos, etc.
There is this existing issue, where many people have discussed it from a few years back up to right now... #1167366: Replace "Lorem Ipsum" Color preview HTML templates with example text in Twig templates .
And a new issue raised by someone this week... #2396983: Header Logo with Bartik won't change in settings preview.

People keep expecting this image of Bartik to show their actual site which it can't do and shouldn't try to do.

The real purpose of this image is to demo colours picked in the color scheme above it. It is indeed within the Color Scheme fieldset, but people don't seem to immediately understand this.

As an alternative solution to changing the content within the "preview" of Bartik, which is still under discussion here, I think a quicker win and a good start to this in the meantime would be to rename the title above the preview image.

This snapshot of Bartik is not a preview, the real site does not look like this, it's just an example of Bartik. As said in this issue here by John Albin.

I suggest changing the title to "Example" as suggested here or more specifically with no room for error "Example Color Scheme" to define what the image is actually portraying.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

SteffenR’s picture

Assigned: Unassigned » SteffenR
SteffenR’s picture

Assigned: SteffenR » Unassigned
Status: Active » Needs review
FileSize
483 bytes

Attached a patch fixing the wording. I choosed "Example Color Scheme" for clarification of content shown below the headline.

As i was thinking about the issue some time the wording "Example Color Scheme" seems to be a bit unspecific in this case - cause the content below shows the color scheme with the actual selected colors - from my understandings an example color scheme would be "Bartik in its default colors".

Maybe we should rename the section to Preview of color scheme - in this case it's clear to the user, that we don't show a preview of the page.
What do you think?

SteffenR

oadaeh’s picture

I think "Example" can be misconstrued in a similar way that "Preview" can be. To me, "Demonstration" would be a better choice, and probably better yet, something more like "Demonstration of chosen color scheme".

SteffenR’s picture

@oadaeh: good point - what do you think @emma.maria

sivaramakrishnan’s picture

Status: Needs review » Needs work

Need to desired on correct text for Preview to Demonstration or Example Color Scheme.

gbisht’s picture

Status: Needs work » Needs review
FileSize
483 bytes

I think "Preview Color Scheme" is better text here. Attached the patch as well.

SteffenR’s picture

Status: Needs review » Reviewed & tested by the community

Thanks gulab.bisht - i think we can set the patch / the issue tp RTBC..

emma.maria’s picture

Status: Reviewed & tested by the community » Needs review

I have some more thoughts on this before a committer takes a look at it.

Apologies for losing track of this issue in the pile and not giving feedback earlier.

meramo’s picture

The patch in #6 still applies against the latest HEAD

aburke626’s picture

The patch in https://www.drupal.org/node/2400277#comment-9526805 applies cleanly and the label text is changed as expected. I think that "Preview Color Scheme" is a straightforward explanation for what this functionality does.

emma.maria’s picture

Issue tags: -Novice
Bojhan’s picture

I am pretty sure we don't camel case like that.

SteffenR’s picture

I hope we can merge the patch into core now - changed the camel casing to "Preview color scheme" in the attached patch.

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.

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

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

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

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.

quietone’s picture

Project: Drupal core » Color backport
Version: 9.4.x-dev » 2.x-dev
Component: color.module » Code

Color has been removed from core, #3270899: Remove Color module from core.

gaurav-mathur’s picture

FileSize
36.75 KB

Patch #13 tested and applied successfully. Attaching screenshot for reference.