fix: add "Go Back" and "Up Next" navigation buttons for Specification… #1708
+17,290
−4,597
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
… 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.
ScreenRecording.mp4