Server-side rendering for custom components (run custom component code on your servers)

[Haroenv]

Problem

Custom components (.jsx and .mdx snippets with props/logic) render client-side only. Your own docs acknowledge the consequences: "Visitors may see a flash before components render" and "Search engines may not fully index client-rendered dynamic content." Built-in components (<Note>, <Card>, <Tabs>…) and raw HTML server-render fine — but anything we author as a component does not.

Why it's limiting

This rules out any custom UI that needs to be present on first paint, avoid layout shift, or be indexable. Concrete example: we built a framework/flavor switcher (JS/React/Vue/iOS/Android/Flutter) that belongs at the top of each page. As a component it flashes in and shifts the content below it. Our only no-flash option was to generate raw inline HTML into ~400 pages via a codegen script — which works, but can't be encapsulated as a reusable component, exactly because components can't SSR. The same limitation hits custom navbar/toolbar controls (e.g. an "Ask AI" button) that snap in after load.

Request

A way to run custom component code on Mintlify's servers, e.g.:

• an SSR opt-in for /snippets components (render on the server, hydrate after), or
• a way to register server-rendered custom components into the MDX pipeline like the built-ins, or
• at minimum, a build-time prerender of custom components so their initial HTML ships with the page.

Any of these would eliminate the flash + layout shift and make custom UI indexable — a big unlock for what we can build on the platform.