Page Builder Solutions

	A	B	C	D	E	F	G	H
1	Solution	Status	Installs	Link	Contributors	Pros	Con	BoF discussion feedback

2	Site Studio	Active Development	n/a	https://www.drupal.org/project/acquia_cms_site_studio	Acquia	* Easy to use compared to other Drupal based tools * Low-code UI to manage components and layouts * Ability to configure styling for components and layout components out of the box * Integrates well with moderation, preview and scheduling	* Proprietary * Can be tedious to set up all of the components * Limited support for nested elements * Issues with translations * Not compatible with decoupled	Only 1 person had a bit of experience using it. Vendor lock-in. Can't remove it from site.
3	Layout Builder Core	Active Development	>52k		Acquia, Community	* In Drupal core * Data storage itself scales well * Integrates well with existing Drupal concepts such as structured data and blocks * Large ecosystem of contributed modules	* Confusing UX leaving more technical people responsible to build pages * Editing content happens on multiple pages * Scalability issues (Block derivatives) * Lack of translations support * Cannot reuse content * Limited support for nested elements * Limited support for decoupled * Multiple storage locations add complexity to upgrade paths / migrations	Works very well with existing Drupal core modules, structure, etc. Very extensible; loads of contrib modules already. Difficult to understand how it stores the config / content (as a developer). Always an issue that there are too many blocks to start with.
4	Layout Builder Misc Contrib	Active Development	n/a		Community		* High number of contributed modules required * Still hard to achieve good UX	Content editors like it a lot; it's easy for them to understand, use when it's set up well. Difficult to migrate to (espec. when the source site has a variety of columns)
5	Layout Builder UX	Abandoned	57	https://www.drupal.org/project/lb_ux	Acquia
6	LB Plus	Active Development	0	https://www.drupal.org/project/lb_plus	Tag1	* Implements solutions to many of the commonly occurring UX challenges * Drag and drop block placement * Block icons * Concept of promoted blocks * Sortable sections * Change a sections layout * A cleaner UI that looks more like the published content while editing	* Not widely adopted yet
7	Paragraphs	Active Development	187,552	https://www.drupal.org/project/usage/paragraphs
8	Layout Paragraphs	Active Development	~7500	https://www.drupal.org/project/layout_paragraphs	Aten Design Group	* Good UX out-of-the-box, well understood by editors * Translations support * Nested components supported out of the box * Works well with decoupled * Single edit page	* Lack of default layouts * Cannot combine structured data with unstructured data (Look: Block Field) * Scalability issues on large sites * Can be tedious to set up all of the components * Single point of failure - maintaned by a single company * Some accessibility issues with the UI	Allows good separation of meta (hidden) type fields and content fields (that get displayed). When outputting via API, very hard to tell which "image" (for example) is from which field. Still has the same issues that paragraphs typically have.
9	Gutenberg	Active Development	3700	https://www.drupal.org/project/gutenberg	Frontkom Wordpress	* Modern, seamless UX * Truly feels like a text editor (copy&paste, undo&redo) * Easy to set up – comes with many pre-defined components * Single edit page * Converting blocks between block types	* Not highly structured data, just blob of HTML * Creating custom components requires duplicate effort * Combining structured data with unstructured data is still limited * Single point of failure - maintaned by a single company * Limited control - we don't own the roadmap * Building custom blocks is tedious and requires expertise in React * Some accessibility issues with the UI	Messy; couldn't save content... Experience for clients is unbeatable. Con: Data storage (field mappings) isn't simple and clear. Pro: Thousands of hours of UX (WordPress). Things like translations are good. Difficult to extend the interface (because part of it is React) for Drupal devs. it's possible to map fields to the "layout blocks", but this requires a lot of work...
10	Page Manager
11	Panelizer	Abandoned
12
13	Layout build				6
14	Layout paragraphs				4.5
15	Gutenberg				2
16	Custom templating				2
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100