If Strapi engineers had designed a train with cabinets for long distance travelling, it would definitely have no seats as third level components. Because they know better than people that if you sit while travelling in nested cabinets in wagons, you may not be able to get off the train safely in an emergency.

Thanks God Almighty that Strapi engineers are just developing CMSs.

Any update on this?

This feature is not complete, it is still causing issues for our team on a regular basis and it is the main reason we will not be using Strapi on any new projects moving forward. What will it take for the developer team to take this seriously?

Building modern dynamic components requires reusability and nesting, 2 levels is simply not enough.

Any update on this?

Colleagues, I don’t really understand the reason why the developers of strapi for almost 3 years cannot hear a completely logical request. Why can't I create more complex content structures out of the box? This also makes sense. I don't want to use a headless CMS, digging into data schemas manually. I want to have a configuration where I can decide for myself what nesting depth to use. What's the difficulty?

Since the functionality of this feature exists “not in the UI,” there are no internal problems or restrictions for its use. This means that the only limitation is in the developers’ policy. I got the impression that the only reason why they don’t want to implement this feature is the justification like “Well, this will just complicate our UI.” Seriously?

This topic has been pushed by Strapi users since 2021, and from the very beginning the developers have been citing the fact that the implementation of this feature is simply not in the plans yet.

Okay, is there an alternative UI for Strapi without this stupid limitation?

This is super frustrating and puts me off wanting to use Strapi.

This limitation forces me to reinvent the wheel instead of normal data structures.

For example, I can't create a "Page" type with a "Sections" dynamic zone, where each section will be an abstract component that contains a visibility toggle and content as a concrete component.

In turn, this component can also have its own connections with entities or other components.

Instead I'll have to create each section as a separate data structure and its complexity will be limited by the "UI", so I'll just have to give up the toggle visibility functionality :)

This is the most frustrating thing I came across with the Strapi. Beware that, If you take the path of adding the nested components manually as described below, you'll get an error when you want to customize the component via UI.

I truly miss the times of kings and queens, where the king would have you all executed if you don't implement it within 3 days and 3 moons. But unfortunately, we live in different times, so, we will have to live with the crup made by coconut brains.

How does it set to "completed" when the feture is still missing?! Honestly, I can't even imagine what the hype is about with so many basic features missing. Tried Strapi for several years in several projects and even now I feel really disappointed that I can't even create a basic multi-level navigation with components. Like starting from scratch again and again.. looking for solutions and always rethinking if I want to use Strapi. Really disappointed.