Andrea Fercia

I'd like to propose to add https://github.com/WordPress/gutenberg/pull/65524 to the list.

Generally, visible labels are always better especially with complex forms with several input fields. In this case, the form is very simple and there's no ambiguity as the context is...

> I lean towards avoiding duplication too. But I am also slightly bothered by the inconsistency here: Eheh yes that's a good case. I'd love to see some established guidelines...

I'd totally support a drastic simplification of the (too long) help text for the settings. As mentioned in https://github.com/WordPress/gutenberg/pull/58207 the help text could be way shorter. More detailed descriptions and...

There's now a smaller PR https://github.com/WordPress/gutenberg/pull/69334 for the InputControl. My fault, I missed this PR and the associated issue https://github.com/WordPress/gutenberg/issues/64666. I'd suggest to merge https://github.com/WordPress/gutenberg/pull/69334 first, if no objections. The...

> It does look better than trunk: Yes it deoes look better but i'm not sure it fully solves the issue. Ideally, the focus style should be the same blue...

It is worth reminding that the whole mechanism of the WP logo / site icon is being discussed in https://github.com/WordPress/gutenberg/issues/57813. To me, the current implementation especially in the Site Editor...

Added the Accessibility label as typography is an essential part of readability and accessibility.

@jameskoster regarding the indentation of the help text, I just noticed that when the help text is long and is multiline, only fhe first line is indented. Is this the...

I have a question. I see Text alignment block support is mentioned in [the WordPress 6.6 Field guide](https://make.wordpress.org/core/2024/06/25/wordpress-6-6-field-guide/) as one of the new features that land in the release and...