Dynamic Zone in Components | Content Editing XP

390

Dynamic Zone in Components

Alexandre Retourne

It could be great to add context or let the users create their contents with little constraints. For example, a grid could have differents components inside like download cards or profile cards. Making a grid component for each variation is not optimal so it would make the UI clearer with fewer components. Lastly, the front-end developer could develop a component manager from front-end and it would manage all content to build the website like legos. The developer would maintain the content builder from strapi POV and the users can immediately use the news components or make change on already launched content.

March 16, 2022

Aurélien Georget

Pinned

Hey everyone 👋
It's Aurélien from Strapi, we added this to our roadmap for next year. Right now, it's scheduled that we will work on it in Q2 (April - June). We know how important this feature is for you. Please continue to post your use cases; the more you share, the better it is for us to understand what you are trying to achieve.
✌️

Brianfbento

Aurélien Georget Just noticed your comment has this as scheduled but the status of this item hasn't been changed. Is this still planned?

Aurélien Georget

Brianfbento: Yes, we are researching how to do it smoothly. We could work on it this quarter according to the complexity of implementing it without dropping the performance.

Tony Gayter

Ive been developing for 15 years in CMS with almost every one out there, and this is my first foray into headless. This is literally the first thing I tried to do and it fell flat on its face. Terrible start, and unbelievable that its not been implemented yet. This lack of feature (shouldn't really be a 'feature' it is just core functionality). This whole data and attributes mess in the api and the lack of any extensibility (like having a 'master' collection type layout) is just pushing everyone away from this.

da_kicks_87

The main use case would be for creating and managing landing / marketing pages.
I would like to use nested Dynamic Zone to give clients a simple “Page Builder” experience. Key word is simple.  I don’t want it to overload users with too many options. The end result should not look like Photoshop or WP Page Builders plugins (Elementor, Oxygen etc..)
Landing / marketing pages are commonly divided into bold sections with a heading. The different sections of the page could have different background colors.  
In Strapi I would want something like this:
A “Section” component. With “Heading”, and “Background Color”  attributes.
In this “Section” component is where the nested Dynamic Zone would be. Here is where we can add row components to the section. Example a “Text and Media” component. Next row would be “3 column Icons and Text” component.
With having a nested Dynamic zone user can add as many or as littles rows to a page section.
Currently with Strapi attempting this structure without nested Dynamic Zone is tedious and is likely to be messy if not cautious. It involves re-creating new Section components based on previous components but with the additional static rows. Every  new component involves a new DB query and additional output code. It takes too long. Components made should be more reusable.
I hope this was clear. I am looking forward to hearing the progress on this. 
The new start of development seems far away...
Thanks.

Yup

We would like to have composition components. For example we have button component, link component and box component - box component could embed button and link. Button and links are standalone components.

Box

Border option
Placeholder

-- Button Component

-- Link component.

Other use-case is grid. We have a button and link - and we would like to have them inside 6x6 grid. We could make component 6x6 which will have 2 placeholders which can contain other components like button/link.

6x6 Component

Left Placeholder | Right Placeholder

Button component | - Link component

Aurélien Georget

Hey everyone 👋
It's Aurélien from Strapi, we added this to our roadmap for next year. Right now, it's scheduled that we will work on it in Q2 (April - June). We know how important this feature is for you. Please continue to post your use cases; the more you share, the better it is for us to understand what you are trying to achieve.
✌️

Johnny Prescott

Aurélien Georget: this is so great and will open so many possibilities. I think this is one of the worst flaws with strapi that makes us create less than ideal and hardcoded components to work around this.

Thanks. Will wait for this impatiently.

Laurens Kling

Aurélien Georget: this absolutely makes my day <3

Kristi Jorgji

Is there any update here ? I still can't use this. If this feature is released is fantastic and Strapi can finally act as a website builder as well like Frontastic etc.
You can have Section
 containing a config in json for layout column width etc, and blocks which is a dynamic zone of many possible components like text, image etc
Then finally someone can make a plugin for the ui to allow create page layout with drag and drop and make Strapi the nr 1 open source website-builder not just CMS

Kevin Vugts

I think this perhabs is the biggest next feature which can make the difference for Strapi to be the ruler of them all. 
As this discussion below is getting bigger and bigger I think the Strapi Team should really take a beer and sit down with everyone to consider building this feature in early V5. 
Meanwhile, patiently waiting...

Daniel Camargo

Any update on this? :(

Given Loyiso

Years later and this is still not available WOW, they should be ashamed. https://github.com/strapi/strapi/issues/5798

Serhii Tihovskii

I must express my profound disappointment regarding the absence of a fundamental feature on this platform. It is disheartening to find that such an essential aspect is not available. I had high hopes for this service, but this omission has left me greatly disillusioned.

→