Skip to content
This repository has been archived by the owner on Oct 28, 2022. It is now read-only.

Variation "Sherbet" #104

Closed
bgardner opened this issue Aug 23, 2022 · 4 comments
Closed

Variation "Sherbet" #104

bgardner opened this issue Aug 23, 2022 · 4 comments

Comments

@bgardner
Copy link

bgardner commented Aug 23, 2022

Screenshot:

Sherbet

Figma:
https://www.figma.com/file/p4qBWBvxIEvT0bAHdCwf23/TT3-Variation-%22Sherbet%22?node-id=2%3A9

Theme.json:
variation-sherbet.json

@beafialho
Copy link
Collaborator

This style variation has been selected to be bundled with the Twenty Twenty-Three default theme! @critterverse and I have made some tweaks to the submission as a part of the curation process to ensure that all the selected variations work together nicely as a collection. Here are the requested changes:

Sherbet

  • Incorporate wide content width (and possibly larger type sizes on the post titles within the query)
  • We loved the all caps typography in the header area and thought this could this be carried throughout the post titles, buttons, etc
  • We’d love to use Inter for this variation, which is currently only being used on “Pitch”
  • Incorporate a very opinionated duotone effect like the Retroactive variation by @scruffian

No explicit next steps are needed — feel free to update theme.json files where relevant or they will be updated in development. Thanks for the contribution!

@scruffian
Copy link
Collaborator

Could we also add the button and separator styles from Retroactive?

@beafialho
Copy link
Collaborator

Could we also add the button and separator styles from Retroactive?

I think the buttons can work! I like the separator styles too but I don't think they'll fit with the bold type in this variation. There's quite a lot going on already and I'm afraid it'll be confusing especially in templates such as "Blog (Alternative)".

@mikachan
Copy link
Member

Closed with #174.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants