[docs] Style inline code parameters with background to distinguish from links

[CiscoFran10]

• I have followed (at least) the PR section of the contributing guide.

Summary

Inline terms like mergeProps were styled in blue without a background, so they looked like links. This change gives inline code that represents parameters a padded, colored background so it reads as code instead of a link, improving clarity and accessibility.

Changes

• Added --syntax-parameter-background and a rule for [data-inline][data-syntax='parameter'] so inline parameter code gets a background, border-radius, and padding.
• Inline code nodes that contain a parameter token are marked with data-syntax="parameter" so the new styles apply.

Closes: #4009

[pkg-pr-new]

• base-ui-tanstack-start

• vite-css-base-ui-example

  pnpm add https://pkg.pr.new/mui/base-ui/@base-ui/react@4043
  

  pnpm add https://pkg.pr.new/mui/base-ui/@base-ui/utils@4043
  

commit: c36484f

[mui-bot]

Bundle size report

Bundle	Parsed size	Gzip size
@base-ui/react	0B(0.00%)	0B(0.00%)

Details of bundle changes

---

Check out the code infra dashboard for more information about this PR.

[netlify]

✅ Deploy Preview for base-ui ready!

Name	Link
🔨 Latest commit	c36484f
🔍 Latest deploy log	https://app.netlify.com/projects/base-ui/deploys/698c1e5eaa4cf400085216bd
😎 Deploy Preview	https://deploy-preview-4043--base-ui.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR improves documentation readability by adding a background style to inline code parameters (like mergeProps), making them visually distinct from hyperlinks. The implementation adds a CSS variable --syntax-parameter-background and a styling rule that applies background color, border-radius, and padding to inline code elements marked with data-syntax="parameter". The rehype plugin was updated to detect inline code containing parameter tokens and mark them with the appropriate attribute.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are isolated to documentation styling with no impact on component logic. The implementation is clean, uses existing CSS variables, and follows established patterns in the codebase. The rehype plugin change is a simple, safe addition that marks elements for styling.
• No files require special attention

Important Files Changed

Filename	Overview
docs/src/syntax-highlighting/index.css	Added CSS variable and styling rule to give inline code parameters a background, distinguishing them from links
docs/src/syntax-highlighting/rehypeInlineCode.mjs	Added logic to detect and mark inline code containing parameter tokens with data-syntax="parameter" attribute

[Copilot]

Pull request overview

This PR improves Base UI docs readability/accessibility by visually distinguishing inline code (especially identifiers that were tokenized as “parameter”/variable tokens) from links, addressing confusion raised in #4009.

Changes:

• Tag inline <code data-inline> nodes with data-syntax="parameter" when the inline-highlighted tokens include --syntax-parameter.
• Add a new CSS custom property for the parameter background and apply background/padding/radius styling to [data-inline][data-syntax='parameter'].

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
docs/src/syntax-highlighting/rehypeInlineCode.mjs	Adds data-syntax="parameter" to inline code nodes when parameter-colored tokens are present.
docs/src/syntax-highlighting/index.css	Introduces --syntax-parameter-background and styles parameter inline code with a background + padding to avoid link-like appearance.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[colmtuite]

Hey @CiscoFran10, thanks for the help with this PR, but we're already working on a redesign + rebuild of the docs, which will include this improvement. So I'm gonna close this as we've got it covered, but thanks for the effort, I appreciate it.

[CiscoFran10]

@colmtuite No problem at all, looking forward to the new docs 😁 .

Just to confirm, will all the points mentioned in the early feedback issue #2766 be addressed as part of the rebuild, or are there still some areas where contributions would be helpful? I was planning to continue fixing some of the items I could, such as the theme toggle.

Also, I currently have these two open PRs that were mentioned in #2766:

• [docs] Add InstallationBlock with package manager tabs to quick start #4052
• [docs] Add GitHub demo source link to Demo component #4076

Should I expect those to be closed as well due to the redesign, or are they still relevant?