feat(demo): redesign — show the grid first, and give the site a mark - #8
Merged
Merged
Conversation
The demo's job is to show a layout, and it was showing an essay. On the dashboard route the first tile started 440px down the page, behind two paragraphs of prose and a wall of controls. It now starts at about 185px. Every panel is closed by default. The example keeps a heading and a one-line summary; the long explanation moved into a Notes panel beside Config and Code, so it is one click away rather than in the way. Design work beyond that: - Spacing, radius and colour are scales now rather than per-component guesses, which is what stops a page this dense looking accidental. - A compact sticky header, so the nav survives scrolling a long grid. It unpins below 680px, where half a phone screen of chrome costs more than it gives. - The three panel buttons became one segmented control: one object with three states rather than three competing buttons. - Cards lost their coloured top stripe and widgets their left border. The hue is sample data, not meaning, and a stripe reads as a status indicator for a status that does not exist. Widgets keep the colour as a small dot. - Dark mode rebalanced, focus-visible rings, and reduced-motion honoured. - Mobile: the nav scrolls horizontally, the segmented control goes full width. Adds a logo mark — three equal-width columns, blocks of unequal height, no gaps left behind. Six shapes, because it has to survive 16px in a tab. The page had been asking for favicon.ico, which was not in public/ at all, so every visit took a 404. Verified in Chromium at 1280 and 390, light and dark: all five routes, all three panels, copy against real clipboard contents, item counts unchanged after toggling, zero failed requests and no console errors. 185 library tests still pass.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
The demo's job is to show a layout, and it was showing an essay. On the dashboard route the first tile started 440px down the page, behind two paragraphs of prose and a wall of controls. It now starts at about 185px.
Every panel is closed by default. The example keeps a heading and a one-line summary; the long explanation moved into a Notes panel beside Config and Code, so it is one click away rather than in the way.
Design work beyond that:
Adds a logo mark — three equal-width columns, blocks of unequal height, no gaps left behind. Six shapes, because it has to survive 16px in a tab. The page had been asking for favicon.ico, which was not in public/ at all, so every visit took a 404.
Verified in Chromium at 1280 and 390, light and dark: all five routes, all three panels, copy against real clipboard contents, item counts unchanged after toggling, zero failed requests and no console errors. 185 library tests still pass.
What does this change?
How to see it
Checks
npm testpassesnpm run formatrun on the files I touchednpm run verify:compat, if I changed anything public (builds a real app on Angular 17–22)