-
Notifications
You must be signed in to change notification settings - Fork 687
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add typography section to styleguide #2013
Conversation
|
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.
So in general this looks great -- are you going to eventually add examples to the left/right as done on the spectrum typography page? Is this a follow-up ticket or should we hold up this PR on that?
</Columns> | ||
<Columns reverse={true}> | ||
<Emphasis /> | ||
</Columns> |
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.
<Section title="Formatting"> | ||
<Formatting /> | ||
</Section> | ||
<Section title="Usage guidelines" /> |
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.
This is empty. Drop some lorem text placeholder?
*** | ||
|
||
<Columns> | ||
<FontSize /> |
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.
Maybe it's the columns component but it looks like it makes two columns differing by background.
@@ -0,0 +1,4 @@ | |||
.title { | |||
font-size: var(--venia-global-text-fontSize-1100); |
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.
This feels like it should use a typography token for heading but I didn't find one that used 1100
.
export const H3 = props => <Heading {...props} level={3} />; | ||
export const H4 = props => <Heading {...props} level={4} />; | ||
export const H5 = props => <Heading {...props} level={5} />; | ||
export const H6 = props => <Heading {...props} level={6} />; |
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.
These don't seem to be used anywhere. Are these supposed to be components for the styleguide UI or for use in PWA Studio (why not both?)
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.
Oh nvm I see the MDXAdapter
:)
Verification steps looks good. Need @jcalcaben @soumya-ashok approval to merge this one. |
Description
Add a typography section to the styleguide. The prose content may be lorem ipsum, but the values should reflect the the official Venia styles.
Related Issue
PWA-153
Acceptance
Verification Stakeholders
@jcalcaben @soumya-ashok
Specification
Verification Steps
yarn workspace @magento/venia-styleguide run start
/page/typography
Screenshots / Screen Captures (if appropriate)
Checklist