Related controls discussion: #16

Taking a few of the current mockups as a basis, I've identified some/all of the pieces a developer should expect to be able to implement:

Label
- To be shown in insertion dialog
Icon
Block controls
Inline controls (optional)
- In the case of the quote mockup, one should expect to be able to format text. Is this merely supporting nested plain text block?
- It's possible that some blocks may want to support only a subset of formatting options
Children
- Given sub-note of inline controls, perhaps blocks could allow nested block descendants
- Future support of a "Columns" block?
Custom editor-specific form
- In the case of the quote mockup, the quote and citation may be separate fields
Transform support
- Mockup
- e.g. change plain text to heading or quote
Advanced settings popover ("Inspector")
- Shown in early mockups for image settings, assumed to be the gear icon in the current image mockup

Below are a few of my early prototypes which include rough implementations of some or all of these requirements:

Given discussion at aduth/wp-block#1, I've also been wondering if we could optionally / alternatively support server-side block registration options, with the following goals in mind:

Sanitize block attribute values based on defined types
Scaffold UIs based on defined block attribute types
- These would admittedly not be as great a user experience, but seems to be an easy way for developers to make quick early iterations of a block, or for freelancers/agencies who can't necessarily justify creating extremely polished block UIs
Allow blocks to be exposed through REST API or elsewhere in PHP, as current proposals expect registration to occur within browser client

We could look to Shortcake and JS Widgets for inspiration on implementing / consolidating server-side registration if it's a path we want to pursue (cc @westonruter @mattheu @danielbachhuber )

Less obvious, but if we decide to add a new syntax for blocks, we'll also want to consider how to add backwards compatibility support for e.g. captioned images (currently shortcode) which should either be supported by or transparently upgraded to the new recommended block. This might need to be a separate issue.

Create an API for defining blocks in the editor. #104

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions