Repository navigation
Keep a contextual return link visible while reading detail pages - #48
Merged
Merged
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
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.
Readers previously had to scroll back to the beginning of coursework and long articles to find their parent page. All 27 detail pages now keep a small arrow and a specific “Back to …” link beneath the LO identity in the sticky left rail, replacing About / Experience on those pages. Each link returns to its original Education, research, or Experience entry anchor, including when the detail page is opened directly.
The same return link stays visible in the compact mobile header without opening a menu. Top-level pages retain the existing navigation, and redundant return links at the start of detail content are removed. The return control uses the shared 14px Inter interface style, a 44px touch target, and existing focus and accent treatment.
Validation: npm run check passed (103 tests), including every detail-page return destination and parent anchor. Browser checks covered deep scrolling, direct links, return clicks, mobile menu restoration, and 320 / 390 / 768 / 1440px layouts. Content and formula preservation checks passed.