Repository navigation
feat(frontend): calmer, consistent UI across every screen - #16
Merged
Merged
Conversation
…arity, refreshed landing shots
…ierarchy, settings rows, file viewer actions
…reate button, settings nav, dashboard layout
…dback, site index, settings hierarchy
…n top bar, cross-site search, settings nav grouping
…consistent scope wording
…ariants, quieter inputs, graph/tag pages, landing framing
…ghts, consistent empty states, legal/auth layout, UK copy
…e and password toggle
…iling sections, readable search meta
…er details, quieter tables, settings rows, legal and auth polish
… wording in file manager
…eference, invite gating and copy fixes
…uted placeholders, house-style commas
…rite on dashboard, top-anchored auth column, readable placeholders
Reworked the dashboard site card against a stress set (all features, long names and descriptions, slug names, long org names, bare private sites) until two design reviews both scored it 9/10: - Title is a link stretched over the card instead of role="button" wrapping buttons; only the org, feature, pin and menu controls sit above it, so the pill and padding click through. - Identity row shows the site's square logo (letter fallback) beside a 40px title slot, so descriptions align across a row. Multi-column titles clamp to two lines with a full-name tooltip on hover or focus (Escape dismisses); single-column titles wrap in full. - Org on its own line (links to the org for members, reveals the full name otherwise) above the counts; counts hold their line while loading. - AI / real-time glyphs are one button with an "Enabled on this site" popover, so their meaning is reachable on touch. - Published/Private is plain status; View public site lives in the menu. - Compact controls with 40-44px touch areas on phones; tooltips wait 400ms on the site grids; no equal-height rows, and the 2-column switch is a container query. - "Realtime" spelled "real-time" in user-facing copy.
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.
The app worked, but it wasn't easy on the eyes: inconsistent spacing and widths between pages, loud colours, cramped or oversized controls, and page actions scattered in different places. This pass reworks every screen – dashboard, file manager, doc reading and editing, file viewers, settings, profile, the published site, marketing/auth pages and mobile – into one calm, consistent system.
It was driven by screenshot review rounds (64 captures per round) until two independent design reviewers both scored every set of screens at least 9/10.
What changes for users
Behaviour changes worth knowing
GET /files?projectId=added.Testing
pnpm --filter frontend test: 917 passing;tsc --noEmitclean.