-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
🎨 Improve navbar blur styles #2751
Comments
Very good point. I do have some thoughts on global header on doc layout. I'm thinking maybe we should draw a gutter line... 🤔 Especially on Tablet view size when we have "On this page" outline button. I wanted make that one better but couldn't come up with good idea, but if we have clear divider at header, it's much easier. I'll try to create mockup and gather some ideas. |
Hey @kiaking Thanks for the positive response. As we have not released the v1 yet I would like to suggest some change to the layout if you agree. It will be more natual, better & cleaner if we make the navbar full width like mintlify: Benefits:
I also did the same on my docs site if you want to check in VitePress: Anu Docs (I just hasn't enabled the blur yet) What's your thoughts on this? |
It's pretty easy to customize (here is a sample: #2442 (comment)), but would nice to have something like that out of the box. Blur filter for this kind of stuff getting more popular lately. |
🤦🏻♂️ This GH bots |
Is your feature request related to a problem? Please describe.
Hi 👋🏻
We are now moving towards v1 and with the merge of #2727 I would like to purpose another change which makes VitePress more elegant.
ATM, navbar blur on scroll doesn't blend into the content purticularly when it's dark content like code block
If you notices there's thick line clearly separating the navbar and the content.
Describe the solution you'd like
Making it more smoother. I don't have words for this but I guess you know how it should look.
Describe alternatives you've considered
None
Additional context
none
Validations
The text was updated successfully, but these errors were encountered: