-
Notifications
You must be signed in to change notification settings - Fork 49
Group 4: Banner and Image audit on the website #2907
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
In this audit I fixed the following component pages: - Button - Code-editor - Flyout - Form / File-input - Form / Masked-input - Modal - Page-header - Flex - Grid --- All other pages (x) total are okay with no changes needed
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Left some feedback.
I noticed some banners not being directly under the heading but from a content perspective it made sense to me.
website/docs/components/code-editor/partials/guidelines/guidelines.md
Outdated
Show resolved
Hide resolved
website/docs/components/code-editor/partials/guidelines/guidelines.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Majed <[email protected]>
@andgen404 Should I be checking banner placement on the "Code" tab as well as the "Guidelines" tab? For example, this one from the MaskedInput Code tab: |
Yes, both tabs. If a banner placement feels out of place, please note it. Thank you! |
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 looks good to me now 👍
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.
Looks good
Group 3: @majedelass and @KristinLBradley
What:
You’ll review and approve PRs that update banner and image placement across our documentation pages. Each PR will follow these standards:
Each PR will include context and a summary of changes.
You’ll review alongside a design partner, ensuring both design and engineering teams are involved in each update.
📌 Summary
If merged, this PR will complete updates for the following component pages as part of the audit:
All other pages (7) total are okay with no changes needed.
🔗 External links
Jira ticket: HDS-4425
Google Sheet file: Here
👀 Component checklist
💬 Please consider using conventional comments when reviewing this PR.