Repository navigation
Update from support feedback: clarify custom components are client-rendered - #7672
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…onents Default-imported MDX snippets render on the server, and not every built-in component does (Mermaid is client-only). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
ethanpalm
approved these changes
Oct 8, 2026
This branch was successfully deployed
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.
The React components page now says plainly that Mintlify leaves custom components (inline exports and
/snippets/imports) out of the server-rendered HTML. They render in the browser after the page loads. The page also recommends built-in components for content that must be in the initial HTML or must not flash. A new help center article, named for the symptom, covers the pop-in and missing-from-source behavior and links back to the canonical page. I checked the server-side no-JS compile (remarkMdxRemoveJs) in the code. The.md/llms.txt output is built from the MDX source, so this behavior doesn't affect it.Support context
Note
Low Risk
Documentation and help-center navigation only; no product or rendering code changes.
Overview
Clarifies that custom React components (inline
exportin MDX and named imports from/snippets/*.jsx) are client-rendered only and are omitted from server HTML, while MDX snippet imports still render on the server.The React components guide’s Considerations section is expanded with this distinction, tighter SEO/flash guidance, and a recommendation to use built-in components when content must appear in the initial HTML without layout shift.
A new help center article targets the symptom (“flash” or missing content in view source), explains the behavior, suggests built-in replacements, and is added to the help center nav in
docs.json.Reviewed by Cursor Bugbot for commit e7900ff. Bugbot is set up for automated code reviews on this repo. Configure here.