-
Notifications
You must be signed in to change notification settings - Fork 127
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
@juanfra @beafialho This is ready for review. There is more than one way to do this. In this PR; I have kept all the current slugs. Another way would be to introduce generic slugs, like |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for working on this, Carolina. I left some comments of things I found.
There are some comments that are related to sizing. If the intention was to work on the sizing later on, please disregard them.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Thank you for your work on this and apologies for the delay in reviewing. Each style variation has particularities which are set up globally with the intent to make each variation unique. It goes a little further than just changing the font. I tested them and have a few comments: Preset 1
Preset 2
Preset 3
Preset 4
Preset 5
Preset 6
Preset 7
|
@beafialho Setting the shape is not possible in a typography preset, it must only change the typography, anything else needs to be separated. |
I wasn't aware. I thought of them as style variations. If it's not possible then, ignore that feedback in this context. cc: @richtabor |
What about the navigation block styles that @juanfra mentioned in the comments? |
Please refer to the comments I made regarding each preset in this comment:
|
Site title: Changed font family and text transform. Post title: Changed font size to 58px.
}, | ||
"core/post-title": { | ||
"typography": { | ||
"fontSize": "var:preset|font-size|xx-large", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Figma, the post title on the single post is set to 58px.
However, in the archive template markup, the post title is set to large, 32px. In the single post template markup, the post title is set to x-large, 48px.
Meaning that setting the size to 58px here won't have any affect on these two titles.
- Set the site title to the large font size - Set the font family, size, weight, and letters pacing on elements > button.
- Set site title to use the ysabeau-office font family, font size small, uppercase, and letter spacing 1.44px - Set elements > button to use the ysabeau-office font family, font size small, font weight 500, letter spacing 1.44px, and uppercase.
Site title: Remove the font family, to fallback on manrope, and apply uppercase. Post title: Change font weight to 300, light. Post terms: Apply uppercase. Navigation: Apply uppercase. Query title: Change font weight to 300, light. Elements > heading: Change font weight to 300, light.
Set elements > button font weight to 500, letter spacing to -0.36px, and apply uppercase.
- Site title: Remove font family. Set letter spacing to 1.6px, apply uppercase. - Elements > Heading: Set font weight to black, 900. - Query title: Set font weight to black, 900. - Elements > Button: set font family to literata, set font weight to 900.
- Query title: Apply font weight 800, extra bold. - Elements > heading: apply font weight 800, extra bold. - Elements > button: apply font wright 800, extra bold, set font family to platypi.
- Site title: Change font size to large. Apply uppercase. - Post title: Change font weight from 250 to 200. - Post terms: Apply uppercase. - Elements > Heading: Set font weight to 200 - Elements > Button: Add literata font family, font size medium, font weight 600, letter spacing -0.96px, and make it uppercase.
I feel like we're rushing implementing this work which has many small details to consider and the discussion is becoming a rabbit hole. I find it hard to review thoroughly in sectioned comments, so I suggest we merge this as is and test again later. |
The changes that were requested are implemented except for |
Description
This PR adds the typography presets.
Partial for #22
Screenshots
Testing Instructions
Apply the PR.
Go to Appearance > Editor > Styles
Test every typography preset in the editor, save, and view the preset on the front.
Confirm if the typography matches the design.
typography-preset-1
Beiruti & Literata Figmatypography-preset-2
Volkorn & Fira Code Figmatypography-preset-3
Platypi & Ysabeau Office Figmatypography-preset-4
Roboto Slab & Manrope Figmatypography-preset-5
Literata & Ysabeau Office Figmatypography-preset-6
Platypi & Literata Figmatypography-preset-7
Literata & Fira Sans Figmatypo-presets.mp4