-
Notifications
You must be signed in to change notification settings - Fork 7
DSD-1843: Hero primary refactor #1765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@bigfishdesign13 updated to use the 12-col grid as in the POC. Let me know what you think and then I'll clean up the PR. |
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.
The grid looks good. It just needs some other small adjustments.
src/components/Hero/Hero.mdx
Outdated
<ComponentDocsHeader | ||
category="Basic Elements" | ||
componentName="Hero" | ||
summary="The `Hero` component is used to display a full width banner at the top of a page" |
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 can be simplified to A full-width banner at the top of a page
.
src/components/Hero/Hero.mdx
Outdated
| Component Version | DS Version | | ||
| ----------------- | ------------ | | ||
| Added | `0.2.0` | | ||
| Latest | `Prerelease` | | ||
|
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 can be removed because it is in the revamped page header.
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.
I think I saw it somewhere else as the updated v4 pattern so I moved it down here. I'll remove.
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.
Yes, I recall that. I think that was a mistake on my part. 😨
src/theme/components/hero.ts
Outdated
md: `". content content content content ."`, | ||
}, | ||
gridTemplateColumns: "repeat(12, 1fr)", | ||
gap: { base: "1.5rem", lg: "2rem" }, |
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.
You should be able to use the useResponsiveSpacing
hook.
src/theme/components/hero.ts
Outdated
}, | ||
content: { | ||
bg: "ui.black", | ||
color: getTextColor("body", "light", foregroundColor, isDarkText), | ||
gridArea: "content", | ||
gridColumn: { base: "1 / -1", md: "2 / 12", lg: "3 / 11" }, | ||
maxWidth: { md: "860px" }, |
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 can be removed. Yes, it allows the width of the content area to be greater than the 800px
max width recommendation, but that's ok.
src/theme/components/hero.ts
Outdated
p: "l", | ||
paddingInline: "1rem", |
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.
Why both of these? If they are both needed, you can use s
for paddingInline
.
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.
💯
Fixes JIRA ticket DSD-1843
This PR does the following:
Open Questions
How has this been tested?
Accessibility concerns or updates
Accessibility Checklist
aria-live
is used, a screenreader was used to verify the text is read.ref
s, focus management was reviewed.Open Questions
Checklist:
Front End Review: