# 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:** 3\ **Page:** 1
**Author:** ![fbwio](https://avatars.discourse-cdn.com/v4/letter/f/51bf81/32.png) [@fbwio](https://community.prismic.io/u/fbwio)\ **Post date:** [December 18, 2024, 7:08am UTC](https://community.prismic.io/t/any-update-on-nested-repeatable-groups/18150/1 "2024-12-18T07:08:52Z")
I love prismic and I would like to use it more, but this limitation of not being able to create nested repeatable groups is **really making it impossible for me** to implement more sophisticated designs or recommend it for bigger clients with more flexible needs. Just one nested layer would be enough as a start! It has been a requested feature for _more than 4 years now_ and I don't understand why this takes so long. Please can you add this feature to your roadmap or give another update on when this will be available. Competitors and even good ol' ACF support nested repeated fields. **I don't want to keep using Headless WP in 2025. Please save me.** **PLEASE** give a proper update on this important feature, thanks. ---
**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 ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [December 18, 2024, 10:24am UTC](https://community.prismic.io/t/any-update-on-nested-repeatable-groups/18150/3 "2024-12-18T10:24:35Z")
Hi team, The thread @jankohlbach linked (thank you!) is indeed our latest update on the matter. You can also check out this thread about it: > [@Content Modelling Multiple Blocks](https://community.prismic.io/t/content-modelling-multiple-blocks/14876/17): > > hey! Indeed, we know that today's solution is not ideal. For your exact case, here is how I would see the things. A "Card" group with 3 Variants (NEW) : Simple With images With Tags Each of the 3 variants will have its fields, say for example the "Card" - "With images": Color field KeyText List of images (NEW) Then editors will be able to: Add a "Card" Choose which variant they need Edit the content I hope this helps. of course this requires work from our team and we know we are not t… We know this is a big need for users, and we're working on our implementation of it. Currently it's hard to give an exact timeline, but this is something we'll be very excited to announce and follow up on whenever we have news or more precise information. Thank you all for your patience with this! 🙂