-
Notifications
You must be signed in to change notification settings - Fork 337
Configurable footer components #42
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
Comments
Thanks for opening the issue, I will take the time to put together something. |
Is the current implementation corresponding to what you were expecting in 2019 or is there still things to change ? |
I think that the implementation of the footer still hasn't changed by too much...IMO there might still be some nice low-hanging fruit to improve there. (e.g., we could have a |
I think a big improvement that would be quite simple is to instead of having a If backward-compatibility is important, maybe a |
solved in #1184 ? |
Ah indeed I think so! closed by #1184 |
Context
Currently our footer is quite minimal, and auto-populated with some Sphinx flags to show things like the copyright etc.
However, many sites use the footer to provide contextual information for readers that scroll to the bottom, things like social media links, site navigation, etc.
Proposal
Our footer should be composable with components, similarly to how our header navbar works. We could re-use some components from the header (e.g.,
icon-links
) and potentially define a footer-specific component or two (e.g.,column links
that displayed vertically instead of horizontally).Design inspiration
edit: this was edited heavily by @choldgraf :-)
The text was updated successfully, but these errors were encountered: