No bundle size changes

Generated by 🚫 dangerJS against 1418421

One question, docs/pages/playground.example.tsx will be deploy to production?

One question, docs/pages/playground.example.tsx will be deployed to production?

It does currently https://deploy-preview-29423--material-ui.netlify.app/playground.example. We can remove it from the export.

I have another way of adding the playground (without committing the file to docs).

We can try hygen. The flow is something like this:

• create a template in folder _templates/docs/playground
• npx hygen docs new playground
• open a prompt asking the playground name
• A playground file is created from the template under /playground

In the future, we can use this method to create other templates, not only about the docs playground.

@oliviertassinari Can I try this? I would like to use the playground when developing Joy also.

@siriwatknp I leave this question to @flaviendelangle, as he was iterating on the playground too. To be clear, the objective of the playground was to be one isolated blank page.

If the objective is to avoid page generation when we deploy, I think that I have a one-line fix. Personally, I think that we can have a cp instruction, it might be even simpler, I would wait for a stronger need to introduce a new tool (hygen).

I would like to use the playground when developing Joy also.

Speaking of which, I think that there is another issue, the _app.js injects the MUI branding by default, IMHO, it's shouldn't, it breaks the isolation property.

We could ignore /docs/pages/playgrounds to let people create several playground, than can be useful for major features where you want to compare several scenarios.

But for the global idea, I am in favor of keeping things simple. I'm not sure introducing a new tool is useful right now.

We could ignore /docs/pages/playgrounds to let people create several playground, than can be useful for major features where you want to compare several scenarios.

But for the global idea, I am in favor of keeping things simple. I'm not sure introducing a new tool is useful right now.

Fine for me. 👍

@siriwatknp I will follow up on this as I wasn't done. I still need to 1. Update the contribution guide 2. disable the static generation of the template page.

We could also add playground.js to gitignore, for even dirtier playgrounds without type checking.