Jan Potoms

I think we should label in function of what we want to measure. We're currently labelling bugs and regressions. > some metrics could help us identify if we write enough...

> To provide clarity on what the issue/PR is about. Sometimes simply choosing between, a bug, a new feature, support: question, and docs, can require a very deep understanding of...

Ok, sounds good. So in terms of which labels have to be applied, how about - core - docs to define area of ownership (We can add more labels when...

This was just some pseudo-code to illustrate an idea, I didn't intend for this to be used as a starting point or anything.

It's currently possible (as a test I've set your license model to "perpetual" by default), but the UI currently doesn't update with it. The reason is that default values are...

> It behaves strangely. The reason it behaves like this is that default value is only used during the first render. When the default value is changed while the component...

> I can't bind the URL parameter to the "value": Are you looking for a way to two-way bind? as in, changes in the text editor should also be reflected...

> 5. Instance editor with left pane alternatively: * project hierarchy * explorer (They use this in vscode) * navigation pane * outliner (blender)

The Toolpad docs are very image heavy. This is a difference from the core docs. I see a few issues that could come up: 1. Linting: There's no automated build-time...

@oliviertassinari I'm moving the discussion to the docs infra notion space https://www.notion.so/mui-org/Images-solution-30e78dbf24744ed5b570027656139092