-
Notifications
You must be signed in to change notification settings - Fork 1.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
Componentize the docs theme #332
Comments
We would also be super interested in this @withfig - is there any way we can help? |
I’ve been thinking about this feature recently, and will start working on it! Componentize the theme will also give us the ability to hide specific part (like the sidebar) for specific pages. |
Awesome - that’s so great to hear! Thank you so much and as I said, please let us know if we can help! |
I would also love this! Our use case: We have highly custom documentation code with much more But by renaming pages from |
A feature like a custom navbar component using next.js conversion would be really great. |
Currently the themes are essentially all or nothing for a given page, which makes it harder to adopt Nextra in more advanced projects.
For our use case, we love the sidebar of the docs theme but we want to use a different navbar.
It would be wonderful if the theme followed the Next.js convention of using a file in
components/layout.js
, and we could do something like:This would really make Nextra a killer app for us, as we would get all of the complexity of auto-generating the sidebar from the file tree, while retaining the ability to customize parts of the page directly instead of through configuration.
Also for context, our first attempt was looking at the docs theme in the
core
branch here. We quickly realized it would be brittle to start tweaking things and would also make it harder for us to contribute to Nextra once we had "ejected".Nextra feels like a really powerful project, so thank you for building it!
The text was updated successfully, but these errors were encountered: