Top navigation bar some hyperlinks are broken

[gbhat618]

Reproduction steps

In the https://docs.jenkins.io/ website, several hyperlinks in the top navigation bar seems broken, and go to 404.
Notably the in the Documentation dropdown the (Tutorials, Developer Guide, Contributors Guide) are broken.

Wrong hyperlinks

* Tutorials: https://docs.jenkins.io/doc/tutorials
* Developer Guide: https://docs.jenkins.io/doc/developer
* Contributor Guide: https://docs.jenkins.io/participate

They seems to navigate as per the sub paths in jenkins.io, however as they are routing in docs.jenkins.io those seem to be not found (in the above mentioned links replacing the docs.jenkins.io to jenkins.io would make the url work)

However there is a way to navigate via the botton tray

Top nav bar hyperlinks broken	Botton tray hyperlinks are workaround

Expected Results

The correct hyperlinks seem to be (as per jenkins.io), (notice these are versioned links so they should automatically bump to latest version)

Tutorials: https://docs.jenkins.io/tutorials/2.452.x/index.html
Developer Guide: https://docs.jenkins.io/dev-docs/index.html
Contributor Guide: https://docs.jenkins.io/community/index.html

Actual Results

The mentioned links navigating to 404

Anything else?

No response

[gbhat618]

I wasn't able to find where this top nav bar configuration is there in this GH repo. (for instance I tried search for Contributor Spotlight to easily also find the Documentation dropdown as it is in the same level; but couldn't find); so probably it is configured on the server ig 🤔 (?)

[krisstern]

Hi @gbhat618 this is a known issue and needs to be worked on during GSoC, so I have added the gsoc label to this. Thanks for creating the issue! However, I would like to ask you to please refrain working on this any further. We may disqualify anyone who attempts to start the project prematurely as if they have already been selected to contribute to the project.

[gbhat618]

Ok noted about it; sorry I wasn't aware.

Actually, just yesterday I discovered about the docs.jenkins.io and found it very helpful for reading the Developer Documentations. So thought to report issues as I noticed.

All best for the gsoc, makes sense 👍

[krisstern]

Thanks! You are welcome to create issues to report bugs though. Just wanted to be clear what we want to do for gsoc hence the clarification.

[beingPro007]

@krisstern Are there any prerequisites or steps we need to take to be eligible to request a pull request for issues labeled "GSoC" (Google Summer of Code), now that the 2025 GSoC dates are confirmed? Specifically, does this apply to this issue or others under the same label? If any guidelines or procedures need to be followed, please let us know.

[krisstern]

Hi @beingPro007 you will need to be selected to be the "official" contributor of this project in order to work on it. And for the steps to apply for GSoC, we have repeated these many times on the #jenkinsci/gsoc-sig channel, so you may want to follow up there instead.

[beingPro007]

Ok sorry for interrupting you, from next time, I will check before asking