feat(docs): redesign home page as an animated dark landing page#9
Merged
Conversation
Replace the plain docs home with a Linear/Vercel-style dark landing page: animated grid + glow background, aurora gradient headline, code card with a rotating border beam, framework marquee, scroll-reveal feature grid, an "observability without the tradeoff" section, roadmap, and a final CTA. - Animations via motion (framer-motion); CSS keyframes in global.css with a prefers-reduced-motion guard - Class merging via cnfast (fast clsx + tailwind-merge drop-in) - Messaging aligned with the README: drop-in for Express/Fastify/Hono/Elysia, two-line setup, OTLP export, REST-today roadmap
Five frameworks don't need a scrolling marquee — the looping duplicates read as filler. Show Express/Fastify/Hono/Elysia/Next.js once, centered. Drops the now-unused marquee keyframes/utility.
The roadmap already lives in the README and docs; on the landing it read as "what's missing" and undercut the pitch. Removes the section and its now-unused imports/data.
…only - Recolor the landing from violet to an emerald/teal/mint palette - Add an animated WebGL Beams hero background (React Bits / three.js), lazy- loaded client-side and disabled under prefers-reduced-motion - Add a "Two lines in. Full visibility out." showcase: the 2-line setup next to a dashboard preview (trace waterfall + logs) so the landing shows what you get - Force dark theme site-wide and hide the theme toggle (no light mode/fallbacks)
Replace the Express snippet with the flagship @getvision/server (Elysia) API: the handler adds a span, wide-event context and a log, and the dashboard mock maps 1:1 — root request span plus the db.select / enrich.profiles spans, with the log carrying the user.plan context. Makes clear that detail comes from instrumenting, not magic.
The fumadocs 16 default MDX components no longer structurally match mdx/types' MDXComponents, which broke `next build` type-checking. Cast the merged map back to MDXComponents.
…ames - Hero and a new lead feature card now headline the auto-generated dashboard (route/service discovery, zero config) — the core feature - Remove Encore.ts by name from the landing (comparison link and card reworded generically); the docs still carry the full comparison - Crossfade the WebGL beams in over the static background so the hero no longer visibly pops from fallback to animation
The transparent-canvas + grid combination muddied the beams; revert to the opaque beams look and remove the now-unused grid layer and its CSS.
three r183 deprecated THREE.Clock, which @react-three/fiber 9 still uses internally, logging a console warning. Pin three to 0.182 (last pre-deprecation release; satisfies r3f/drei peer ranges) until r3f migrates to THREE.Timer.
Add an SVG mark — two mint beams forming a "V", echoing the hero background — and wire it into the docs nav and as the favicon. Replace the "🔮" in the README title with the centered logo.
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
2 participants
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.
Replace the plain docs home with a Linear/Vercel-style dark landing page:
animated grid + glow background, aurora gradient headline, code card with a
rotating border beam, framework marquee, scroll-reveal feature grid, an
"observability without the tradeoff" section, roadmap, and a final CTA.
prefers-reduced-motion guard
two-line setup, OTLP export, REST-today roadmap