# Content Modelling Multiple Blocks

**URL:** <https://community.prismic.io/t/content-modelling-multiple-blocks/14876>\
**Category:** Developing with Prismic\
**Tags:** product-feature-idea, content-modelling\
**Created:** [January 2, 2024, 1:39pm UTC](https://community.prismic.io/t/content-modelling-multiple-blocks/14876 "2024-01-02T13:39:44Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![come.sabran](https://avatars.discourse-cdn.com/v4/letter/c/b2d939/32.png) [@come.sabran](https://community.prismic.io/u/come.sabran)\
**Post date:** [August 9, 2024, 12:25pm UTC](https://community.prismic.io/t/content-modelling-multiple-blocks/14876/15 "2024-08-09T12:25:24Z")

</div>

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 for example.

We want to start (and we are starting now) with the 80% first, offering a nice way to do simple lists, for the most common use cases. And these of course will be able to be put in a group.

I hope this helps understand our vision. But I repeat, we do want to let you model these use cases.

Best,

Côme

---

_[View the full topic](https://community.prismic.io/t/content-modelling-multiple-blocks/14876)._
