The Gutenberg project has been going great. Lots of activity, Slack fun meetings, GitHub issues are filled with discussion, you’ll love to read. Here’s the meeting summary for this week’s editor team meeting (agenda here) in #core-editor Slack channel.
There was a good deal of discussion around the states of a block in general. General consensus led to the following decisions/suggestions (Mockups should be further improved to include five states mentioned below):
- Selected block
- Selected content within the block
Empty State (optional for some, but important for extension flexibility)
Ticket for fail-states, like broken hyperlinks and images that didn’t upload, block-parse errors. Even warnings if you try to publish with placeholders.
Moreover, following discussion took place:
Text Selection: Selecting text, whether by mouse or via keyboard nav, should invoke controls.
Embeds: Include embed in tech requirements, as well as the neutral state.
Ticket: What happens to block controls when you page down a draft, when do they show up? On select, on arrow keys, on PgDn? We will discuss further in a ticket.
Testing: @karmatosed is offering to test things at upcoming WordCamps. Let her know your ideas in #core-editor.
Link Boundary Feature: Everyone loves the link boundary feature. Some accessibility issues that are solvable.
That’s about it, happy hacking!