Skip to content

Document client-side evaluation of MDX expressions #7334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ethanpalm merged 3 commits into from
Sep 11, 2026
Merged

Document client-side evaluation of MDX expressions #7334

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
72fc45e
docs: note that MDX expression values are evaluated client-side and a…
mintlify[bot] Sep 10, 2026
98b6352
docs: tighten wording of the client-side evaluation note
ethanpalm Sep 11, 2026
8e55d00
Apply suggestion from @ethanpalm
ethanpalm Sep 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions create/reusable-snippets.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,6 +140,10 @@ Reference variables from a snippet in a page.
</Step>
</Steps>

<Note>
The browser evaluates MDX expressions, such as imported variables like `{myName}` and inline expressions like `{1 + 1}`. Their values do not appear in a page's initial HTML or in [offline exports](/deploy/export), so crawlers, LLMs, and other tools that do not run JavaScript see the surrounding text without them. Write the value as plain text if it must be visible to those readers.
Comment thread
ethanpalm marked this conversation as resolved.
Outdated
</Note>

### Import snippets with variables

Use variables to pass data to a snippet when you import it.
Expand Down