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
Unrelated Navigation in Community Guideline #4968
Comments
I would like to work on it |
I am already working on it |
Could you describe the issue in detail? @dhamkirti21 |
I have described the issue @Mohith234 please check it, again |
I have assigned it to you @dhamkirti21 |
any review @DarrenDsouza7273 or should i add something more to it |
@Mohith234, it would be ideal if the sidebar table of contents is dynamically populated and doesn't rely on hardcoding of the sections / headings. Can we get an issue opened describing this? // @SudhanAruna |
This issue has been open for some time with no recent activity, unassigning to open it up for new contributors to give it a go. |
Hey @saurabh100ni I would love to work on this issue :D, can you please assign me |
Current Behavior
<! -- A brief description of what the current circumstance is. -->
Currently In the handbook specifically on Community Guideline page, on the right side of page there is a page navigation for the sections dedicated to the specific page but in context of this page we have only community guideline navigation is only useful and working and others are not working and not related to this page.
Head over to the issue: https://layer5.io/community/handbook/community
Desired Situation
Unrelated Navigation should be removed or replaced to useful links.
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the
master
branch.📚 See contributing instructions.
🎨 Wireframes and designs for Layer5 site in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.
Join the Layer5 Community by submitting your community member form.
The text was updated successfully, but these errors were encountered: