Usability looks not easy

Thank you so much for the feedback!

Yes, current editing UX is not that handy and obvious. The UX is a next big step.

> Create body leads to a frozen modal frame
What does you mean by "frozen"?

> Create Columns leads to a frozen modal frame with only Save button
Yes, it is by design. It's not obvious, but you should place a components under the "Columns" (using drag & drop like then managing taxonomy terms), not inside.

> Create Grid leads to a frozen modal frame with only Save button
The same as above.

> Create Section leads to a frozen modal frame = I can add a section
The same way as above you can put any content under Section.

> When I edit an existing node, I don't know what are my content items (see screenshots) so usability looks difficult. I have to click on Search to see my items (Edit_Page_Test_de_bricks_Drupal_standard_-_2015-11-06_11.15.33.png)
No, that's not true. Search button is for re-using of Bricks from other pages. You should see. Probably it's a bug. Could you please describe your steps?

> When I ask for preview or in View mode, it is almost empty instead of displaying 8 entities (Test_de_bricks_Drupal_standard_-_2015-11-06_11.15.54.png).
Not exactly. Those 8 entities exist but not attached to the page! Use a combination of Search button and Add another item to add all of them. Don't forget about drag & drop them in a tree structure!

Anyway I need to work on documentation first and then on UX for sure.

I'm currently heavily exploring this avenue in site building. I haven't had a chance to build a site with "Bricks" yet but it's great project name. At least as good as Blocks and certainly better then Paragraphs or the ridiculous Beans. I guess what I'm getting at is good branding will definitely help UX and adoption.

When building entities (grids/sections/etc) all would benefit from a custom form validation that adds in a human readable title, instead of the entity id.

Either that, or hiding the autocomplete form element (and search button) altogether, and making it a hidden field.

Also there is no way to remove an element once you've added it.

This module would really benefit from the use of inline entity form (https://www.drupal.org/project/inline_entity_form) instead of the confusing popup.

FYI.. this patch to the references dialog module #2154513-9: Improve the UX by grouping multiple links in a dropdown would help cleanup those "+ Create" links into a drop down select.

At least as good as Blocks and certainly better then Paragraphs or the ridiculous Beans. I guess what I'm getting at is good branding will definitely help UX and adoption.

@travisc, thank you for the kind words. It was long story of choosing a proper name and concept, and now I hope we are on the right way.

When building entities (grids/sections/etc) all would benefit from a custom form validation that adds in a human readable title, instead of the entity id.

@jwilson3, not sure. My vision is to manipulate with entity previews. For example, when you adding an image you want to see the IMAGE, not a title. Also: as I see you didn't get the key thing: try to reorder bricks like on my screenshot below (three bricks are children of parent Columns brick).

Either that, or hiding the autocomplete form element (and search button) altogether, and making it a hidden field.

Search button allows you to navigate through existing bricks and this is one the most handy features. Autocomplete form element — yes, it is mostly for internal use.

Also there is no way to remove an element once you've added it.

Now there is! And even to restore it back! (see screenshots below)

This module would really benefit from the use of inline entity form (https://www.drupal.org/project/inline_entity_form) instead of the confusing popup.

My first implementation was build on top of it. But practically it's not that convenient — just imaging how it will look like in case of 100 bricks on one page.

FYI.. this patch to the references dialog module #2154513-9: Improve the UX by grouping multiple links in a dropdown would help cleanup those "+ Create" links into a drop down select.

@gmclelland, thank you SO MUCH for pointing! It is exactly what I was looking for. I will also try to force this patch in References Dialog.

Thank you all, finally I did a solid update to UI:

Which is rendered to:

Also: as I see you didn't get the key thing: try to reorder bricks like on my screenshot below (three bricks are children of parent Columns brick).

Right, I didn't get this because the system did not prevent one thing from being added before the other existed. Maybe there is a way to guide the user through that process? In the end i think you're going to need to create a custom widget instead of piggybacking on the existing multi-occurrence form field UI, so that each item can be encapsulated inside another, and you can prevent adding things where they wont render correctly or dont belong and so you can essentially guide users through building while they learn, and prevent them from shooting themselves in the foot.

Focusing on 8.x version which is stable now!