Gutenburg – blocks as “separately authorable objects”

feature Suggest for allowing
blocks as “separately authorable objects”

During website creation, a team may be working in their various fields of specialization or task designation.

Content creators in various media are working concurrently with the website appearance and navigation designers, along with technical performance tuners.

It would be handy to be able to separately edit a block, without needing to assign it any location at the time that it is created.

Blocks can then be stored in a repository for inclusion at any place at any time, repeatedly.

Additionally the layout designer can design locations for blocks, that have no content. But when the content creators have made content, then that content is automatically sent to the locations on all pages that it is required at (which could also be to entirely different websites).

This could work like RSS from author to presentation location(s) on the site(s).

It would also be very easy (once having made this functionality), to then generate a list of all locations where a block is presented, and to manage the handling (in bulk) of any block.

This may not need a re-write of the present Gutenburg UI, but it may benefit from additional modes to the use of the UI.

For users that are restricted to authoring certain blocks or block types, the UI could be simpler and optimized for that “mode of use” (task and work flow).

This might include a method for them to “manage their blocks”, that could be similar (in code) to the system presently used for managing pages (list, bulk actions).

I hope some of this inspires some thoughts.