Material-ui: Process for developing new components?

[ryanpcmcquen]

Sorry if this has been asked already, I searched around but could not find anything that applied. Is there a documented process for creating _new_ components for Material UI? I looked here and do not see anything that applies:
https://github.com/mui-org/material-ui/blob/master/CONTRIBUTING.md

• [x] This is a v1.x issue (v0.x is no longer maintained).
• [x] I have searched the issues of this repository and believe that this is not a duplicate.

Context

My company is using Material UI as our baseline component repo, and we are developing components on top of Material UI (https://github.com/SurLaTable/slt-ui). We are trying to streamline the process of adding new components. I was wondering what process the Material UI team uses for adding new components, and getting instant or quick feedback on component level changes.

[oliviertassinari]

@ryanpcmcquen I'm happy to hear you are using Material-UI as a baseline for your project.

Is there a documented process for creating new components for Material UI?

I'm not sure to understand your concern. We are focusing on supporting a limited set of components, only providing the most requested components by our users. We rarely add new components. When we do, the process is to go through the lab.
For anything else, we encourage people to publish their components as third party projects we might promote in the documentation.
I hope this answer your question.

[ryanpcmcquen]

@oliviertassinari, ah, what is the process of _going through the lab_?

[oliviertassinari]

@ryanpcmcquen We already have a lot to do with the existing components. The process with the lab is to open an issue like you did here and to talk about the component you want to implement. What do you have in mind :)?

[ryanpcmcquen]

@oliviertassinari, I didn't have a particular component in mind, I am more interested in how you build it ... do you start with CodeSandbox to iterate on the component, or do you run some kind of local server, or something else?

[oliviertassinari]

@ryanpcmcquen We are using the documentation website.