[docs] Improve migration guides to link raw markdown format for AI

[cherniavskii]

As an experiment, I added raw .md migration guide files that are easier to consume by AI tools like Copilot or Cursor

[mui-bot]

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

Updated pages:

• docs/data/migration/migration-charts-v7/migration-charts-v7.md
• docs/data/migration/migration-data-grid-v7/migration-data-grid-v7.md
• docs/data/migration/migration-pickers-v7/migration-pickers-v7.md
• docs/data/migration/migration-tree-view-v7/migration-tree-view-v7.md
• docs/data/migration/usage-with-material-ui-v5-v6/usage-with-material-ui-v5-v6.md

Generated by 🚫 dangerJS against 121d79b

[bernardobelchior]

As an experiment, I added raw .md migration guide files that are easier to consume by AI tools like Copilot of Cursor

There's also this llms.txt proposal. Could we use that with Cursor and, as a side-effect, expose it for other LLMs?

Just wondering 🤔

[cherniavskii]

@bernardobelchior Yes, I'm aware of that. However, it will be a larger effort to adopt it for the MUI docs as a whole.
This PR is a low-hanging fruit. These .md files are much more friendly to AI code tools.

[alexfauquette]

@cherniavskii Do you know if the markdown file needs to be hosted on the same domain name?

If not, we already have something nearly ready for all pages: the "Edit this page" button that links to the GitHub edit page. We could have a similar one leading to the GitHub raw page

[cherniavskii]

Do you know if the markdown file needs to be hosted on the same domain name?

No, it doesn't.

we already have something nearly ready for all pages: the "Edit this page" button that links to the GitHub edit page.

Oh, I didn't think of it! Do you think we should prefer linking to GitHub instead?

[alexfauquette]

Do you think we should prefer linking to GitHub instead?

I'm not familiar with those files for LLM. So I don't know what we should do. But I can see some points:

1. The main advantage of github link is the implementation. Just modifying the footer component adds the link to all markdown pages (including the core and toolpad docs). Instead of adding pages, you modify the page layout
2. The SEO: for Google, I don't know what is the impact of internal page with similar content. Coudl it be interpreted as duplicate? We should be careful to don't get those MD files indexed by Google search engine. At least with external links it's not an issue
3. We would be blocked on further improvement. If at some point you want to replace the {{"demo": .... }} bloks by their code in the MD files, this would not be feasible with the GitHub links

[oliviertassinari]

Related to mui/base-ui#1738.

[cherniavskii]

@alexfauquette I updated the PR to link to the raw .md files on GitHub instead. Thanks for the idea!