nebari-dev / nebari-dev/nebari-docs
[BUG] - Inconsistent 'Getting Started' hyperlink behavior
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Describe the bug
On the welcome page of the Nebari documentation, the Getting Started hyperlink under the Just Curious tab exhibits inconsistent behavior depending on the current URL.
Currently, the behavior of the 'Getting Started' hyperlink depends on the presence or absence of a trailing slash ("/") in the current URL:
-
When the current URL is https://www.nebari.dev/docs/welcome (no trailing slash), clicking on the 'Getting Started' hyperlink correctly navigates to https://www.nebari.dev/docs/category/get-started.
-
However, when the current URL is https://www.nebari.dev/docs/welcome/ (with a trailing slash), clicking on the 'Getting Started' hyperlink navigates to an incorrect URL (https://www.nebari.dev/docs/welcome/category/get-started) which leads to a 'Page Not Found' error.
Expected behavior
Regardless of whether the current URL ends with a slash ("/") or not, clicking on the Getting Started hyperlink should navigate to the Getting Started section of the documentation at this URL: https://www.nebari.dev/docs/category/get-started.
How to Reproduce the problem?
- Visit the welcome page of the Nebari documentation (both with and without a trailing slash).
- Click on the 'Getting Started' hyperlink under the 'Just Curious' tab.
Command output
No response
Versions and dependencies used.
No response
Anything else?
Contributor guide
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.
Research direction
Start from the linked documentation welcome page and locate the Getting Started hyperlink under the Just Curious tab. Reproduce the link from /docs/welcome and /docs/welcome/, then update the link so both URLs reach /docs/category/get-started and verify that neither produces a Page Not Found error.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100