Discussion Needed for integrating GrapesJS with Wagtail-CMS

[hazho]

I want to contribute and make the Great GrapesJS available in the Great CMS of Django/Python world that called WagtailCMS, need some help from experienced contributors here, the following are features of wagtail that are related to GrapesJS:

1. Collections: wagtail cms has some sort of categorization or directories called collections, and those collections given certain permissions in the User group's security model, i.e. a group may have access to a certain collection and its subcollections, another group may have edit permissions over a certain collection and subcollections, ....etc.
   there is an Image chooser widget similar to the AssetsManager called ImageChooser (this can be set for the direct DB field and/or for the blocks of StreamFields that is JOSN serializable data type).
2. Media files are divided into two types: Documents and Images, Docs can be any type of documents that had been set in the Project configuration settings.
3. both Images and Docs have Tags and Collections, a user can filter the results of listing page to only show images/docs within a certain collection and/or tagged by a certain tag.
   the filtering done by a URL query param for tag (admin/images/?tag=<an_images_tag>) or for collection (?collection_id=) or for both (?collection_id=&tag=<an_images_tag>).
4. number of items in the assets listing page divided into a number of paginations weather dynamically set in the frontend or just as a static setting in the project configuration settings.

[hazho]

Questions:

is it better I create a branch for this?

what could be the best approach?
grapesJS editor to be as one of the streamFields' blocks
or
to be a separate actual DB field of the page

how to integrate assets while there are two separate apps dealing with assets in the WagtailCMS (Docs & Images) and respect their view restrictions?