Not saying it is the best, but I would use Nested Content.
"text-left image-right" / "text-right image-left" would probably be the same type for but with a switch for the editors to decide left/right positioning.
Very nice package. In this way you can insure your users only use doctypes in the grid that are preconfigured. Without using the macros. Less error margin for the users is far better UX.
I have read some things about grid V2 that is suppose to have about the same functionalities. But not much dev is done there.
I don't think Nested Contents UI can handle the complexity of a page builder, with a lot of different component types, and give an easy overview of what is on the page.
Stacked Content was nice, but it lacked the sectioning feature that grid has, where you can have a different sections with their own settings, containing multiple components.
But don't use Grid as it is OOTB, to me grid is only a viable option when you go 100% DTGE editors, and use a custom rendering view suited for your site.
Best approche to content page "builder"
Hi, using umbraco 8, what is the best approche to create a content page "builder"?
Scenario: We would like the client to build his page for instance. If we break down the parts in this example:
component: text-left image-right
component: full-width image
component: text-right image-left
component: full-width text
component: image gallery
....
The client should be able to compose a page with these parts. Ofcourse it's up to the client in what order or how many blocks he uses.
What is the best approche? Grid, nested content, other...?
Thanks!
Not saying it is the best, but I would use Nested Content.
"text-left image-right" / "text-right image-left" would probably be the same type for but with a switch for the editors to decide left/right positioning.
Regards, Magnus
Hi. I also suggest Stacked content. He is good for doing page builder. I made a change to the source code where the visual appears in the backoffice
We ended up using doctype grid editor: https://our.umbraco.com/packages/backoffice-extensions/doc-type-grid-editor/
Very nice package. In this way you can insure your users only use doctypes in the grid that are preconfigured. Without using the macros. Less error margin for the users is far better UX.
I have read some things about grid V2 that is suppose to have about the same functionalities. But not much dev is done there.
Thanks!
I would say grid (I'm obviously biased though :))
I don't think Nested Contents UI can handle the complexity of a page builder, with a lot of different component types, and give an easy overview of what is on the page.
Stacked Content was nice, but it lacked the sectioning feature that grid has, where you can have a different sections with their own settings, containing multiple components.
But don't use Grid as it is OOTB, to me grid is only a viable option when you go 100% DTGE editors, and use a custom rendering view suited for your site.
is working on a reply...