Repository navigation
Add day-100 comparison to the official landing page - #1550
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.
Add a day-100 comparison before “Keep your database. Add the app.” on the official homepage. SQLPage stays alongside five illustrative alternatives, using the existing typography, icons, database sculpture, and wave transitions.
All six cards use one Handlebars partial, and repeated illustration rows share a CSS primitive. Native horizontal scrolling, keyboard navigation, reduced motion, and the stacked phone layout are preserved. Browse controls remain stable during section animations, and arrow keys stay at the first and last cards.
Validation: scoped Biome checks,
npm test,npm run build, and all 36 landing-page Playwright cases using the prebuilt SQLPage binary. Before/after renders of all six panels at 1440, 768, 390, and 320 pixels are pixel-identical; the section's computed styles also match. Existing regression scenarios and assertions remain covered.