🐛 Navigation links in the API page are broken
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- html, jekyll
- Domain
- documentation
Research direction
Open the parse-server API page and inspect the source that generates its navigation links and section headings. Compare each link hash, such as #using-environment-variables, with the corresponding heading and ensure the generated page scrolls to every linked section. Verify the result by clicking the navigation links on the API page.
Written by the indexing model from the issue text.
Description
Describe the bug
The links in the parse-server API page are broken. Clicking on them changes the page hash but doesn't scroll to the associated section.
To Reproduce
Steps to reproduce the behavior:
- Go to the webpage
- Scroll down to the nav links below the sponsors
- Click on any of the links, none work.
Expected behavior
Clicking on the link should scroll to the associated section.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: Ubuntu
- Browser: Brave
- Version: Version 1.28.106 Chromium: 92.0.4515.159 (Official Build) (64-bit)
Smartphone (please complete the following information):
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]
Additional context
One solution is to simply add the id attribute to all the headings so that the browser handles the scrolling without any additional config. For example for the "Using Environment Variables" link, the hash changes to #using-environment-variables, so the associated <h2> in the page should have id="using-environment-variables". This should be done for all the nav links.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 506
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from parse-community/docs
-
📙 Opendocs:cloud-code type:docs
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
parse-community/docs#936 ·
-
docs:sdk-js
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
parse-community/docs#961 ·
-
type:bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
parse-community/docs#950 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
parse-community/docs#947 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
parse-community/docs#929 ·
All issues in parse-community/docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100