-
Notifications
You must be signed in to change notification settings - Fork 451
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
feat(structure): document panel UI updates #8622
base: next
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
No changes to documentation |
⚡️ Editor Performance ReportUpdated Tue, 18 Feb 2025 11:52:50 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
Component Testing Report Updated Feb 18, 2025 11:56 AM (UTC) ❌ Failed Tests (5) -- expand for details
|
6d03be5
to
a381f6e
Compare
{createLinkMetadata && | ||
isSanityCreateLinked(createLinkMetadata) && | ||
CreateLinkedBannerContent && ( | ||
<ShowWhenPaneOpen> | ||
<Banner | ||
tone="transparent" | ||
data-test-id="sanity-create-read-only-banner" | ||
content={<CreateLinkedBannerContent metadata={createLinkMetadata} />} | ||
/> | ||
</ShowWhenPaneOpen> | ||
)} |
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 was moved to the banners into the DocumentPanel* with the rest of banners
4c23995
to
f99df5a
Compare
dca0550
to
767739e
Compare
Ahh I see what you mean, I completely missed the call to actions act the bottom. This was something I brought up as well when the create banner was first implemented. Initially, they had the buttons at the bottom on the footer as well but Product asked they move it to the banner if I'm not mistaken because it was too intrusive for normal users. So yes, I'd definitely want to just have a double check from create before we go ahead with these changes 🙏 edit: also, I was unable to test this myself on the deployed version; but before: if a user started editing the document, the banner would disappear, making it that if the user didn't want to engage with create they would just keep going about their day. Would the document actions revert back to the normal actions if the editor starts making changes in a doc? @pedrobonamin @mariusGundersen |
It should definitely be flex end. I missed it, I looked to much into the mobile view. |
Yes, it will
Screen.Recording.2025-02-18.at.10.01.46.mov |
Thanks for the instructions this is very useful to know (remember?) (also sorry for digging into this, just want to make sure I fully understand it and it's clear, ultimately it's up to create if these changes are ok!) |
Yes, it will work in the same way as before. |
baf1854
to
74730a3
Compare
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.
Nice!
Description
This PR updates the document panel UI
TLDR;
The Create banners are also updated, this shows the new designs.
Mobile view

The mobile view was updated to include a dropdown instead of the tabs for the different views.
Also, the perspectives badges for the documents have a fade scroll view, they don't wrap anymore in the flex container
What to review
Testing
Notes for release