feat: Updated add "Go Back" and "Up Next" buttons for specification navig…

[vtushar06]

… versions (#1618)

What kind of change does this PR introduce?
Bugfix — improves UI/UX through enhanced navigation between Specification version pages.

Issue Number:
• Closes #1618

Screenshots/videos:
https://github.com/user-attachments/assets/7815d73e-23ed-4cb0-9b75-693a8bb183b1

If relevant, did you update the documentation?
Not applicable — changes are limited to component-level enhancements.

Summary
This pull request addresses the missing "Go Back" and "Up Next" navigation buttons across the Specification version pages, as discussed in issue #1618.
As part of this contribution:
• I implemented a reusable navigation component for consistency.
• Integrated the component into five Specification version pages to ensure seamless traversal across document versions.
• Validated the functionality across all affected routes for correct previous/next link logic.
• Ensured the code adheres to existing linting and styling standards.

These enhancements improve overall documentation navigation flow and accessibility for users referring to different spec versions.

Does this PR introduce a breaking change?
No — the implementation is fully backward compatible and isolated to specific pages.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

ScreenRecording.mp4

[github-actions]

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name	Status	Preview	Last Commit
website	✅ Ready (View Log)	Visit Preview	b5f2849

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@7e78fe8). Learn more about missing BASE report.
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main     #1743   +/-   ##
========================================
  Coverage        ?   100.00%           
========================================
  Files           ?        29           
  Lines           ?       548           
  Branches        ?       158           
========================================
  Hits            ?       548           
  Misses          ?         0           
  Partials        ?         0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Utkarsh-123github]

Great job ! @vtushar06 .
Just some small extra changes are to be reverted in the formatting part which I have suggested in the attached video, fixing those changes will make this PR ready to be merged.
Please refer to it.
Thank you !

2025-06-28.20-46-38.mp4

[vtushar06]

hey @Utkarsh-123github sir, I reverted changes which you pointed out, Thanks for detail guidance
will love to work with you in future and JSON org team.
Thank you so much.
@vtushar06

[Utkarsh-123github]

Good work @vtushar06 !
LGTM 🚀

[vtushar06]

Thanks a lot @Utkarsh-123github, Please can you suggest me others challenging issues where i can spend good amount of time in solving that.

[Utkarsh-123github]

You're most welcome! @vtushar06

I'd suggest exploring the open issues in the repo , there are quite a few that might match your interest and skills. If you find any that you feel are challenging and you'd enjoy working on, feel free to drop a comment on the issue or let me know directly. If it's unassigned and fits well, we can definitely get it assigned to you! 🚀

[vtushar06]

Thank you so much @Utkarsh-123github for this humble response,
I will go through old issue and let you know which i finds more challenging one .
@vtushar06

[vtushar06]

Hi @Utkarsh-123github, just checking in to see if there are any updates or further inputs needed from my side for this PR. Thanks!

[Utkarsh-123github]

Hey @vtushar06 , the PR doesn't needs any further changes based upon my review.

I have added this PR to second review, and after that it'll get merged.
Thank you for your contribution 🚀

[vtushar06]

Thank you so much @Utkarsh-123github, I appreciate your guidance and review throughout the process. Looking forward to the merge 🚀. Happy to contribute!

[vtushar06]

Hi @Utkarsh-123github,
Just checking in regarding issues #1474 and #1192—I’m planning to work on them. Please let me know if there are any specific considerations before I proceed.

Thanks,
@vtushar06

[Utkarsh-123github]

Hi @vtushar06 ,

Thank you so much for your enthusiasm and willingness to contribute—it’s always wonderful to see new contributors getting involved! 🙌

Just a gentle reminder: please try to avoid tagging unnecessarily or repeatedly , as it can clutter the discussion and make it harder to manage notifications. It is considered a bad practice/ approach. For instance, in this case, the issues you mentioned don’t seem directly related to the PR, which can create a bit of confusion.

Rest assured, we do receive notifications and I’m actively monitoring the repository—so no worries on that front. I truly appreciate your patience as we go through the process.

It’s completely okay—these things happen, especially when you’re just getting started. Just be sure to carefully review the issue context before commenting so we can keep conversations as clear and focused as possible.
Looking forward to seeing your contributions take shape!

Thank you!

[vtushar06]

Thank you for the kind reminder and guidance! I’ll make sure to be more mindful going forward.