-
Notifications
You must be signed in to change notification settings - Fork 5.2k
feat: ContentHero design update #16032
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
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -73,7 +73,7 @@ export const UpgradeLayout = ({ | |
const heroProps = { | ||
...frontmatter, | ||
breadcrumbs: { slug, startDepth: 1 }, | ||
heroImg: frontmatter.image, | ||
heroImg: { src: frontmatter.image, width: 5750, height: 4332 }, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm a bit unsure about this pattern and whether it's truly needed. For dynamic images, I assume we'll need to pass width and height for aspect ratio. If so, I'd define these in the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Not sure either I guess... it's not really meant to dictate the rendered size, more to tell the aspect ratio and prevent layout shift.. but if we're already confining the image to a fixed box size then likely doesn't matter? |
||
description: ( | ||
<> | ||
<div> | ||
|
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.
shouldn't we keep these dimensions to keep the same aspect ratio or a calculated width & height to avoid layout shifts?