# Any update on nested repeatable groups? **URL:** \ **Category:** Developing with Prismic\ **Tags:** product-feature-idea, slice-machine\ **Created:** [December 18, 2024, 7:08am UTC](https://community.prismic.io/t/any-update-on-nested-repeatable-groups/18150 "2024-12-18T07:08:52Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jankohlbach](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/jankohlbach/32/8998_2.png) [@jankohlbach](https://community.prismic.io/u/jankohlbach)\ **Post date:** [December 18, 2024, 9:38am UTC](https://community.prismic.io/t/any-update-on-nested-repeatable-groups/18150/2 "2024-12-18T09:38:15Z")
100% with you on this last time I checked with them and wanted to know how to best model such slices following was the response: > [@What would be the best way to model such (twice nested) slice?](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/7): > > 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 slight_smile … think nested groups sadly are not coming which is a big bummer think they rather will implement more like the repeatable links field, maybe a gallery for example probably will solve some issues and more complex cases, but still not the same --- _[View the full topic](https://community.prismic.io/t/any-update-on-nested-repeatable-groups/18150)._