Implement custom blocks for end users about blocks HOT 4 CLOSED

This sounds like it covers most of the bases. Here's a few thoughts:

// I don't think there's much value in using context here
<Blocks.Provider theme={theme} blockComponents={components}>
  <Blocks.Editor />
</Blocks.Provider>

// E.g. using props seems more standard/straight-forward
<Editor theme={theme} components={components} />

As for the schema and serialization, I think it could make sense to treat all blocks as the jsx type in the Slate schema, and use an addition data.type property or similar to add the root component name, which can be checked against the components provided to the Editor. If we're talking about using static properties to define the shape of the editing forms anyway, we'll need to check that in the runtime. We probably will still need someway to know whether a JSX block accepts children or not though... I think I have enough to put together a proof of concept of this if this doesn't make sense

from blocks.

Updated the proposed API to <Editor theme={theme} components={components} /> 👍

from blocks.

In order to make things simpler we're now opting (as of #17) to only use two custom block types: jsx and jsx-void which a block extends. The metadata needed for rendering and exposing the form can be added to the node's data field.

{
  type: 'jsx-void',
  data: {
    type: 'YouTube',
    props: {}
  }
}

from blocks.

Addressed by #17 and #19

from blocks.