Saxon Fletcher

From a UX perspective there isn't much difference between those approaches as all the complexity should be hidden behind the scenes. It should just feel like you're adding to or...

> we could consider triggering the transformation into links when someone tries to edit the content of the page list, but we'd have to consider how that interaction would happen...

@mtias just to confirm I understand the above. We would like to add something like the below to theme.json spec: ``` "aspectRatio": [ { "width": 16, "height": 9, "name": "16/9"...

> he former seems more correct to me given many of these aspect ratios are just table stakes and generally relevant. @mtias Sounds good to me. Side note, it might...

@richtabor design wise it looks good to me with adjusted controls. I'm assuming we will want the dropdown used in image crop to use the same component. Unrelated to this...

Wondering if we could highlight properties in the toolbar that are connected much like we will do in inspector where we use an icon. In toolbar we could highlight with...

To give a more complete picture here is the direction of block connections across both templates and posts. **Template** You _can't_ modify attributes that are connected. We should show default...

A suggestion on how to possibly move this forward in an iterative manner. The idea behind the [States](https://github.com/WordPress/gutenberg/issues/57719) issue was to build a flexible approach to define the multitude of...

I would +1 @aaronrobertshaw comment. A summary of the timeline so far. We started with focusing on just colours via [colour sets/ways](https://github.com/WordPress/gutenberg/issues/48581) (basically what you've proposed here @richtabor ). We...

> Just to confirm, do you mean we should stick with the buttons for block style variations? No I meant stick with what you've built.