What would be the best way to model such (twice nested) slice?

[Ezekiel (Ezekiel Ravidat)]

I see what you mean.

I think it's pros and cons, with the right nomenclature it might be easier to explain that the page has content "blocks" inside them and everything inside a category is its own block, which would avoid potentially page-breaking bugs if they don't have the same number/order of repeatable zones. But what you're saying makes sense, if your priority is the ease of having everything on one page so your client has a better experience that would be one way to do it

Nested groups or Slices have been a long-requested feature and we understand the need for it from you and other users' use cases. This is something that's being worked on and thought about. Our team is looking at ways to make this work in the best possible way:

Content Modelling Multiple Blocks

Hey there! Thanks for answering on this thread. Let me clarify here our recent statement of not doing groups in groups. In fact, we STILL want to implement a solution to let you accomplish all of these advanced use cases, but we don't think a generic solution allowing groups in groups is the first thing to do. We observed that in 80% of cases, the "nested" content is very similar (lists of images, lists of links, lists of tags etc..). The other 20% are more complex like list of cards in tabs…

Thank you for your feedback, and feel free to check out that thread, you may find some other ideas to make your project work in a more efficient way for everyone involved!