[Docs Bug 🐞 report]: Correct the links of navigation buttons in Docs

[akshatnema]

Describe the bug you found in AsyncAPI Docs.

Recently, I noticed that there are certain pages in the documentation which are connected wrongly with the adjacent/next pages in the UpNext and Previous buttons.

For ex: https://www.asyncapi.com/docs/tutorials/streetlights-interactive links the pages in a very different order as per the recent change and alignment of pages in docs. I would suggest refactoring the links inside each page related to these buttons in a correct manner so that we have a good synchronization with the pages inside the documentation. Overview pages of each section in Docs should also have these buttons, to connect the sequence of Docs.

Also, kindly change the route of UpNext button in https://www.asyncapi.com/docs/tutorials/getting-started page to /docs/tutorials/getting-started/event-driven-architecture

Attach any resources that can help us understand the issue.

This doesn't need any resources or tutorials as such. Just we have to change the links of each button on the respective doc pages

Code of Conduct

• I agree to follow this project's Code of Conduct

[manavdesai27]

Could I work on this issue, I had already started working on issue #1000 . Work has already been done, it just needs approval, as I had already discussed it there, and started working accordingly. @akshatnema @derberg

[derberg]

@manavdesai27 definitely makes sense you continue with this one too as it is #1000 related.
I recommend you first start by researching what docs pages are missing Next/Prev buttons, and where they should point to when you add them. Show it here in a comment in a table, so we can easily verify and then you can open a PR.

Makes sense?

[manavdesai27]

@manavdesai27 definitely makes sense you continue with this one too as it is #1000 related. I recommend you first start by researching what docs pages are missing Next/Prev buttons, and where they should point to when you add them. Show it here in a comment in a table, so we can easily verify and then you can open a PR.

Yeah sure, I will make a table and get it approved, and then will create a PR. @derberg

[manavdesai27]

I have currently created the buttons and linked them in this manner, I wasn't sure where to link the Reference Overview page and thus have linked it to Specification v2.5.0. The current commits are according to the table, and once you approve it, I would create a PR. @derberg @akshatnema

Go Back	Current Page	Up Next
N/A	Welcome	Concepts-Overview
Welcome	Concepts-Overview	Server
Overview	Server	Producer
Server	Producer	Tutorials-Overview
Concepts-Producer	Tutorials-Overview	Getting Started-Introduction
Tutorials-Overview	Introduction	Event Driven Architectures
Getting Started-Introduction	Event Driven Architectures	Coming From OpenAPI
Event Driven Architectures	Coming From OpenAPI	Hello World
Coming From OpenAPI	Hello World	AsyncAPI Documents
Hello World	AsyncAPI Documents	Servers
AsyncAPI Documents	Servers	Adding Security
Servers	Adding Security	Streetlights - Interactive (Alpha)
Getting Started - Adding Security	Streetlights - Interactive (Alpha)	Streetlights
Streetlights - Interactive (Alpha)	Streetlights	Tools - Overview
Tutorials - Streetlights	Tools - Overview	Guides - Overview
Tools - Overview	Guides - Overview	Reference - Overview
Guides - Overview	Reference - Overview	Specification - v2.5.0

[derberg]

I think it looks good, @alequetzalli can you confirm please?

[manavdesai27]

I see that /docs/reference/specification/latest redirects to the latest specification version page, and thus I think Reference-Overview's Up Next button should point to it. @derberg

[akshatnema]

@manavdesai27 I checked the table on which you listed the sequence and it looks good to me. But yess, it now depends on @alequetzalli as well 😅. Regarding the Specification v2.5.0 page, it's better to link it via /docs/reference/specification/latest so as to get the latest specification on next page.