Make WordPress Core

Opened 22 months ago

Closed 5 months ago

#57024 closed enhancement (wontfix)

Twenty Twenty-Three: Randomly apply a style variation on activation

Reported by: desrosj's profile desrosj Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.1
Component: Bundled Theme Keywords: 2nd-opinion dev-feedback
Focuses: Cc:

Description

In addition to the default base styling, Twenty Twenty-Three comes with 10 additional style variations.

When activating for the first time, an interesting way to showcase what the theme has to offer would be to randomly apply one of the 11 style variations.

Change History (6)

#1 @joyously
22 months ago

I don't think random is a good way to present a theme.
In a classic theme, there is starter content for fresh sites, but that is done through the Customizer, which block themes don't do.
The default style should be the one that users see when activating it, or there is a mental stress of wondering what they did wrong.

#2 @mikachan
22 months ago

The default style should be the one that users see when activating it, or there is a mental stress of wondering what they did wrong.

Yeah, I see where this could cause confusion for users.

Perhaps instead of applying a random variation on activation, we could introduce an opt-in for randomization. For example, a button on the Theme selection page, near the 'Activate' and 'Live Preview' buttons. Plus this could appear for all themes that have variations, not just Twenty Twenty-Three.

I'm not sure the above idea is ideal either, but I really like randomization as a fun way to show off variations.

#3 @karmatosed
5 months ago

@mikachan what are your feelings on this now that some time has passed?

#4 @karmatosed
5 months ago

  • Keywords dev-feedback added

#5 @mikachan
5 months ago

I think randomonising style variations is still a fun idea, but maybe we could pursue this as an experiment in Gutenberg or another plugin for now.

Happy for this ticket to be closed for now, and we can come back to it when we have more of an idea of what users would like to see.

#6 @karmatosed
5 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

Thanks @mikachan I am going to close this then and we can review at some point as an experiment.

Note: See TracTickets for help on using tickets.