Feature: Added "Back To Top Button" in Glossary Page #694
+2
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Akella Srinivas <alsrinivas.346@gmail.com>
Srinu346
force-pushed
the
fix/glossary_moveup_button
branch
from
50a1f5a to
05627b4
Compare
|
I have read the CLA Document and I hereby sign the CLA |
|
@Achanandhi-M please go through |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What has changed?
This PR adds a "scroll-to-top" button to the Glossary page.
Previously, the Glossary page lacked this navigation feature, which is already present on other long-form content pages. This created an inconsistent user experience, requiring users to scroll manually to the top of a potentially long page.
This change utilizes the existing BackToTop component to ensure functional and visual consistency with the rest of the documentation site, improving overall usability.
This PR Resolves #3086
Type of change
How Has This Been Tested?
Build Results
Screenshot
Checklist: