Docs landing & product-page rework#748
Merged
Merged
Conversation
…le showcase, and migrate sections
…/integrations/demos/console to product pages
…add lang icons; restore Concepts; tune landing grid columns
…brand lang icons; concept icons
…via width:0 instead of display:none)
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
CahidArda
changed the title
… Redis demos; fix MCP link to /agent-resources/mcp
…ccurate SDK/demo descriptions
…r and Database Migrator to Search integrations
…rgets (redirect stubs don't redirect on direct nav)
CahidArda
changed the title
…low Agents SDK; drop hero buttons; re-add console tabs (placeholders)
…ter vertical fade)
…ks follow the card link
…e-width fix via data-current-path instead of :has()
- Move /redis/integrations/mcp to /redis/sdks/mcp (nav, catalog, redirect, inline links updated) - Product landing pages now show only the SDKs catalog section; drop demos/integrations/guides sections - Landing: link the pricing page in the Products section sub, tighten copy, and fix .u-sub styles (Mintlify renders the sub as <span>, so p.u-sub selectors never matched)
- REST API page: add frontmatter description, replace the plain create-a-database sentence with a Tip linking to getstarted and connect-client, drop the redundant intro line - Credential Protection: describe where to find Reset Credentials
alitariksahin
approved these changes
Jul 13, 2026
CahidArda
added a commit
that referenced
this pull request
Jul 24, 2026
… race) (#764) The custom docs landing (mode: frame, introduced in e7e3bec / #748) renders its body client-side, so on a hard load the page is short and the footer sits inside the viewport. Mintlify's footer-avoidance scroll handler then pins the fixed sidebar above the viewport (negative inline top) and only recomputes on a scroll event - once the body hydrates and the footer moves away, nothing re-runs it and the sidebar stays stuck showing the tail of the nav. Replaces the scroll-nudge auto-repair (ba7a78b / #757), which repaired after the wrong paint (visible snap) and silently failed exactly when the bug is born: the pre-hydration page can be too short to scroll, so its 1px scroll fired no scroll event (and the resize event it also dispatched does not trigger Mintlify's handler at all). - style.css: reserve min-height:100vh on #content for /introduction from the first paint, so the footer can never be in view while the body is empty and the bad measurement becomes impossible. Keyed on data-page-href, which is SSR'd with the real path (data-current-path SSRs as "/" and is stamped only after hydration - too late). Second selector covers local mint dev, which stamps the attribute as /src/_props/introduction. - script.js: replace the nudge machinery with a small backstop that, if a stuck state ever appears (negative top with the footer far from view), re-runs Mintlify's own listener via a synthetic window scroll event - nothing visibly moves, and it works on an unscrollable page.
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.
https://linear.app/upstash/issue/DX-2806/docs-landing-page-improvements
Summary
Reworks the Get Started landing page and every product landing page into richer
hubs. Adds a shared catalog of SDKs, integrations, and demos so each product page
surfaces the right resources, and gives the landing a custom layout that keeps the
docs sidebar.
Shared building blocks
snippets/catalog.jsx: one source of truth for SDKs, integrations, demos, andguides. Filter by product and type; cards show a language icon where relevant.
snippets/landing.jsx: custom landing components (hero, product grid, agentresources, concepts, community).
style.css: custom card and section styles for light and dark.img/icons/*.svg), language icons (TypeScript and Pythonfrom Tabler, Ruby logo), the Context7 mark, and Tabler icons for the
agent-resource and concept cards.
Per-page changes
introduction.mdx): custom landing (mode: frame, keeps thesidebar). Hero, Products grid, Agent Resources (MCP Server, Skills, CLI,
Context7), Concepts, and Community.
redis/overall/getstarted): SDKs, Integrations, and Featured Demos(Hacker News Trends, Eve).
redis/search/introduction): a Demos section showing thesearch-related demos.
qstash/overall/getstarted): SDKs and Integrations.workflow/getstarted): SDKs and Demos.search/overall/getstarted): SDKs and Integrations (includingDocumentation Crawler and Database Migrator).
box/overall/quickstart): SDKs (TypeScript, Python, CLI) and Guides(OpenClaw, Hermes, Crabbox, Playwright).
vector/overall/getstarted): SDKs and Integrations.Future work
(
snippets/migrate.jsx) but hidden. It will list source platforms (Redis Cloud,ElastiCache, DynamoDB, and others) once the guides exist.
product page once the screenshots are ready.
Note on
style.cssCustom CSS is officially supported by Mintlify
(they auto-load a root
style.cssand recommend CSS files over inline styles), sothe amount here is fine. Most of it is our own
.u-*classes.Page-specific overrides are scoped with Mintlify's documented
data-current-pathselector (e.g. the
mode: framefull-width fix only applies to/introduction).The one caveat: a couple of rules still target Mintlify's internal elements
(
#content-area/#content-side-layout, plus a prose<img>margin reset).Mintlify warns that "styling of common elements is subject to change," so these
could break on a future Mintlify upgrade. They're isolated and commented in
style.css.