-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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(www) Table of contents for API reference pages #21808
Comments
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Thanks again for being part of the Gatsby community! 💪💜 |
Hi! I'd like to contribute taking this one 😄can I ? |
Just opened a PR @wardpeet Let me know if I should change something please 🙏 is my first one! |
Summary
API reference pages, such as node-apis do not use our standard table of contents, instead using an inline component:
This is suboptimal, since it's stuck on the page content and we don't get the nice table of contents sidebar like we do in normal docs.
Implementation
We'd need to change the table of contents component to take in a generic list of items rather than a
page
objects. Once this is done, it should be fairly straightforward to add it to the api template.Related Issues
We may want to wait until #21762 to go in, since that also changes the table of contents component a fair bit.
The text was updated successfully, but these errors were encountered: