feat: redesign landing page hero, add performance proof, and refresh …#298
Open
Ibrahim2595 wants to merge 1 commit into
Open
feat: redesign landing page hero, add performance proof, and refresh …#298Ibrahim2595 wants to merge 1 commit into
Ibrahim2595 wants to merge 1 commit into
Conversation
…inference guides
- Hero: new headline/subhead copy, outlined "View the architecture" secondary
CTA, CNCF Sandbox project link, and a "Founded by" strip with founder
logos (Red Hat, Google Cloud, IBM, CoreWeave, NVIDIA) rendered as
monochrome marks on the dark hero. CNCF logo kept in brand color.
- New "Validated in production" section with five stat cards (3x, 70%,
40%, 13.9x, 50k) and an "Explore performance analysis" CTA linking to
prism.llm-d.ai.
- Inference guides section: renamed heading to "Start with the pattern
that matches your bottleneck." with subhead; cards refreshed (titles,
taglines, body, CTAs) and links switched to absolute llm-d.ai URLs.
- Section-end CTAs ("Explore performance analysis", "See all guides")
promoted from text links to outlined ghost buttons that share the
hero secondary button's box shape.
- Navbar logo switched to theme-aware SVG variants (light/dark).
- Removed the legacy inline "How llm-d works" YouTube embed from
src/pages/index.js (the dedicated /videos page still uses VideoEmbed).
Signed-off-by: IBRAHIM IBRAHIM <66755652+Ibrahim2595@users.noreply.github.com>
✅ Deploy Preview for elaborate-kangaroo-25e1ee ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ahg-g
reviewed
May 21, 2026
| description: | ||
| "llm-d's endpoint picker scores each replica in real time across four signals: prefix cache locality, KV-cache utilization, queue depth, and predicted latency. Each request is dispatched to the replica with the lowest expected tail latency — delivering order-of-magnitude p99 improvements over round-robin routing, with no additional hardware.", | ||
| linkLabel: 'Explore LLM-aware routing', | ||
| to: 'https://llm-d.ai/docs/guides/optimized-baseline', |
Collaborator
There was a problem hiding this comment.
@chcost we either make https://llm-d.ai/docs always point to the latest released branch, or for every link on the landing page we do https://llm-d.ai/{latest}/docs and we define a latest=0.7.0 var; I prefer the former
Contributor
There was a problem hiding this comment.
@ahg-g agree. Let's make the default the latest release branch. With the option "dev" in the toggle menu, that allows users to see documentation from main. Make sense?
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.
What does this PR do?
Refreshes the landing page end-to-end.
Why is this change needed?
The previous landing page led with a single distributed-LLM-inference claim and a row of three CTAs. Visitors didn't have a fast way to (a) see proof that llm-d works in production, (b) understand who's behind the project, or (c) move efficiently from "interested" to "which guide should I follow." This redesign adds those three signals in the hero/upper-fold and gives the inference guides a clearer entry point.
The CNCF Sandbox acceptance and the production benchmark numbers were the two strongest credibility moments missing from the previous design — both are now surfaced above the fold.
How was this tested?
npm test)npm run build)npm start)Checklist
git commit -s) per DCOnpm test)npm run build)Related Issues