Docs(blog): back link above post title#1
Open
Chesars wants to merge 1 commit into
Open
Conversation
The "← Blog" link was wrapped around `BlogPostPage`, which sits outside Docusaurus's `Layout`, so on mobile it rendered visually above the navbar. Its desktop styling also used `position: fixed`, so the link floated over the post body whenever the viewport was narrower than the empty margin beside the 820px content column. Swizzle `@theme/BlogPostItem/Header` and render a small `<BackLink />` inside the `<header>`, just before the title. Same left edge as the H1, scrolls with the content, no overlap. Guard with `useBlogPost().isBlogPostPage` so the link only shows on individual posts, not on the blog index. Drop the now-unused BackLink component and styles from `src/theme/BlogPostPage/`.
Chesars
changed the title
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
1 participant
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.
Was rendered outside the post container — on mobile it overlapped the content, on desktop it floated in the margin. Now it sits inline above the H1, mobile-first.