Repository navigation
feat: add startSide to ScrollTimeline - #9
Merged
Merged
Conversation
Cards alternate above and below the axis so each gets its own half of it, which is what lets them be tall relative to the viewport. That alternation is a layout device and means nothing by itself — but when the items carry an order a reader will project onto the vertical axis, it decides which of an adjacent pair sits on top, and a lower-ranked item landing above a higher-ranked one reads as a hierarchy that isn't there. startSide flips which side the run begins on. Defaults to 'above', so existing callers are unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Cards alternate above and below the axis so each gets its own half of it — that's what lets them be tall relative to the viewport. The alternation is purely
index % 2; it means nothing about the items.But when the items carry an order a reader will project onto the vertical axis — seniority, rank, size — the parity decides which of an adjacent pair sits on top, and a lower-ranked item landing above a higher-ranked one reads as a hierarchy that isn't there.
Came up on the portfolio's work timeline: a Senior role landed above the Staff role directly next to it, at the same company. Nothing was wrong with the layout, but it read wrong.
Defaults to
"above", so existing callers are unchanged. One test covering the flipped run, plus aStartBelowstory.Full suite: 181 passing across 25 files. Lint, typecheck, stylelint and build all clean.
🤖 Generated with Claude Code