Remove the previous/next article component - #3356
Merged
Merged
Conversation
The article journey nav sat at the foot of every page, pushing readers along the flattened menu order. That order is an artefact of how the nav tree happens to sort, so the "next article" was often unrelated to what the reader was doing. The sidebar and Related section already cover moving between pages. Removing it takes journeyOrder() with it, since nothing else flattened the tree, and the speculation rules that prerendered the two neighbour pages. The position:fixed Chromium sticky workaround lived in the same component but is unrelated to it - both nav columns are position:sticky - so it moves to the layout. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Pull request environment is available at https://stoctodocspr3356.z22.web.core.windows.net. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
The linked bug is specific to position: sticky with bottom: 0, where the element lands a toolbar's height above the viewport floor once the mobile browser chrome hides. Nothing here is bottom-anchored: .site-nav and .side-nav both stick to a top offset. Both also drop to position: static under 1130px, so at the widths where the bug appears the page has no sticky element at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
borland
reviewed
Aug 13, 2026
borland
left a comment
borland
left a comment
Contributor
There was a problem hiding this comment.
Code LGTM and I'm happy to remove it, but if you haven't already, check with Ellen on the design before we merge this
Contributor
Author
|
@borland Thanks, she has approved: 
|
borland
approved these changes
Aug 13, 2026
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
3 participants
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.
Removes the article journey nav (the "Previous article" / "Next article" buttons at the foot of every page).
Preview
A page that used to carry the buttons: Create a release
What it did
It flattened the nav tree to its leaves in menu order and linked the reader to the entries either side of the current page. That order is an artefact of how the nav tree sorts, so the "next article" was frequently unrelated to what the reader was doing. The sidebar nav and the Related section already cover moving between pages.
What goes with it
src/components/ArticleJourney.astrosrc/layouts/Default.astrojourneyOrder()insrc/lib/navigationTree.ts.article-journey*insrc/styles/main.css<script type="speculationrules"><div style="position: fixed;">position: sticky; bottom: 0, which this site has none ofOn that last one:
.site-navand.side-navare the only sticky elements here, both anchor to a top offset, and both switch toposition: staticunder 1130px.Verification
Local
pnpm build— 2674 pages, exit 0. The preview page above returns 200, with noarticle-journey,speculationrules, orposition: fixedin the served HTML.🤖 Generated with Claude Code