Aurélien Georget: This is great to hear <3 The use case is pretty simple. Lets say you have a Background component. You have a select box for what kind of background it is, a primary color, etc, or a custom color. Now when the user select custom color you want to show an input to add that custom color string. Right now, that input will always be there, but it will never make sense to be there outside of the custom color context. This our UI is filled with edge-case inputs which make editing difficult and confusing.

Aurélien Georget: This is great to hear! I've been waiting for this functionality to be added for a while. My use case is to look at how ACF for WordPress uses Conditional Logic when building out field groups. It exactly what I would expect. One quick use case: I give choices to the content editor (Choice A, B,C), they choose, then the proper fields show up for them to add the content.

Aurélien Georget: Any chance we could include tabs as part of this? :D

Brianfbento: The chances are low, a tab system will be introduced for Draft & Published, we won't offer any extension possibilities for the first iteration, however, the component is here and it will create future opportunities :)

Lauge Milling: would love a solution as well.