redesign: rebuild landing page in a sharp, Vercel-style UI - #8
Merged
Merged
Conversation
Full rebuild of the marketing landing page and a couple of related auth fixes found along the way. Landing page (components/landing/*, app/page.tsx): - Complete visual rebuild: sharp rectangular frames throughout, no border-radius anywhere, single blue accent on a near-black base, Geist Sans/Mono (matches the rest of the app's tokens). - New sections built from the real product: hero with the live Overview dashboard screenshot, an SDK/framework logo marquee, a two-column install snippet (JS/Python tabs, working copy button, line numbers), a feature bento grid (traces/endpoints/alerts, real screenshots), an AI anomaly-detection panel, a status-page showcase, an honest stats row, and two CTA tiles. - Floating sharp navbar; shared blue hover-fill treatment on every button-shaped CTA. - Footer wordmark: giant faded "LIVEBOARD" with the actual logo mark swapped in for the "O". - Copy was fact-checked against the codebase, not assumed: dropped an unverified "MIT licensed" claim (no LICENSE file exists), dropped "hosted platform" framing (production deploy step is unchecked in the project's own checklist), and traced the self-hosting/RLS claim through docker-compose.yml, auth.ts, core/config.py, and the RLS migration before keeping it. - Removed every old landing component in favor of freshly written ones (no reuse of the prior rounded/glow-heavy design). Auth (auth.ts, app/auth/signin/page.tsx): - Fixed a real data-loss bug: authorize() was defaulting a blank display name to the email prefix before it ever reached the backend, which defeated the backend's COALESCE-based name preservation on repeat sign-ins — every sign-in silently overwrote the user's display name. Blank now passes through as null. - Added DISABLE_DEV_LOGIN as a second, explicit kill-switch for the dev-login credentials bypass, independent of NODE_ENV. - Restyled the sign-in page to match the new theme; fixed "Welcome back" copy that presumed an existing account (there is no separate sign-up step — first sign-in provisions the account).
…d .env.example
- infra/docker-compose.yml: the frontend service never received
API_SECRET_KEY or INTERNAL_SERVICE_TOKEN, but auth.ts's
provisionUser() needs one of them to call the backend's
/v1/internal/provision on sign-in. As configured, self-hosting via
docker compose up would let sign-in "succeed" while silently never
creating the user's org/project/API key. Also wires through
DISABLE_DEV_LOGIN.
- .env.example: didn't actually exist despite docker-compose.yml's
own usage comment telling you to copy it. Added, covering every var
referenced across auth.ts, core/config.py, and docker-compose.yml,
with notes on what's required vs optional and why.
- .gitignore: removed a stray `.env.example` entry that contradicted
the file's own comment two lines above it ("intentionally NOT
listed here") and would have silently excluded the file just added.
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.
What
Full rebuild of the marketing landing page from scratch, plus two auth fixes found along the way while making the sign-in page presentable before deploy.
Landing page
Auth fixes
Verification