[website] X landing page update June/July 2026

[joserodolfofreitas]

Summary

Adds:

• X Scheduler
• X Chat
• AI Assistant on the Data Grid

Also trying to fix a problem with a section title

Preview

https://deploy-preview-48716--material-ui.netlify.app/x/

[code-infra-dashboard]

Deploy preview

https://deploy-preview-48716--material-ui.netlify.app/

Bundle size

Bundle	Parsed size	Gzip size
@mui/material	0B(0.00%)	0B(0.00%)
@mui/lab	0B(0.00%)	0B(0.00%)
@mui/private-theming	0B(0.00%)	0B(0.00%)
@mui/system	0B(0.00%)	0B(0.00%)
@mui/utils	0B(0.00%)	0B(0.00%)

Details of bundle changes

---

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

[joserodolfofreitas]

@Janpot, could you please help me untangle the deploy/pnpm docs:build failure on this PR?
The first error says Module not found: Can't resolve @mui/base, but the import trace points to packages/mui-lab/build/..., not to the new X Scheduler demo. Locally that looks like stale Lab build output: current packages/mui-lab no longer depends on @mui/base, but the ignored packages/mui-lab/build folder can contain old v6 output that does.

Edit 1: So the @mui/base error was stale local artifact noise. The real PR blocker is the new Scheduler import path in the landing page compiling @mui/x-scheduler@9.0.0-beta.2 against React 19
Webpack is rejecting one React private-internals fallback in the Scheduler dependency’s ESM build.

Edit 2:
The issue is in @mui/x-internals@9.6.0, pulled by @mui/x-scheduler@9.0.0-beta.2. It does:
React.__CLIENT_INTERNALS_DO_NOT_USE_OR_WARN_USERS_THEY_CANNOT_UPGRADE ?? React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED
React 19 has the first one, but webpack still statically validates the second property as a React ESM export and fails because React 19 does not export __SECRET_INTERNALS....