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
Sidebar reorganisation proposal #6845
Comments
Just adding my approval here! I love this idea because it always bothered me that some links were not available in certain viewport sizes. Now that we have https://community.astro.build and hope to use it for more, docs doesn't have to be the place that links to absolutely everything! If we link to just the community site, then people can get what they want in the right spot! |
Still happy with this proposal! |
I would love to collaborate on this and come up with an better solution to the current implementation. |
Are we still liking this @delucis ? Is this something that we're happy to have community members attempt? |
Definitely! Happy to provide any guidance if anyone would like to attempt all or some of this. |
Now that I've some more time, would love to take this on @delucis! |
Bring it, @SatanshuMishra ! 😄 |
Quick Clarification @delucis. For the footer below the pagination, should a new component be created? Or do you think adding it to the pagination component is sufficient? Depending on what we want to add to this, a new component may be the way to go. However, if we want to keep it to simple links, may be too much abstraction for a simple problem. |
Either is probably fine to start with — we can always move things around. Personally, I'd probably make a dedicated component for the links and then add it to footer. Thanks @SatanshuMishra! |
Prompted by #6791, I wanted to share a plan for the page sidebar to address a few longstanding issues.
Current sidebar
Overall aims
Proposal
Overall the result would look something like this:
The text was updated successfully, but these errors were encountered: