# What would be the best way to model such (twice nested) slice? **URL:** \ **Category:** Developing with Prismic\ **Tags:** slice-machine\ **Created:** [October 29, 2024, 1:29pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899 "2024-10-29T13:29:51Z")\ **Posts on this page:** 14\ **Page:** 1
**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:** [October 29, 2024, 1:29pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/1 "2024-10-29T13:29:51Z")
## Describe your question/issue in detail I'm happily using prismic and the slice machine, I really love it, but from time to time I have a slice that I'm just not sure how to model, because it kind of needs some nested logic. I really appreciate you bringing in the repeatable groups feature to have multiple repeatable groups in a slice, that already solved quite some issues, but here's my remaining one: ![Screenshot 2024-10-29 at 14.29.06](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/a/a9d6eea2f85c060382f6833b2e56abe87d04cebb.png) ![Screenshot 2024-10-29 at 14.29.18](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/8/8f311032582d7e49ae35ea54f4365ad724f22f34.jpeg) ![Screenshot 2024-10-29 at 14.29.37](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/5/5282fba98bb8ec5ad120dda7fc0f1c658ec9b1ec.png) So what I have (in the design) is a list of let's call it categories, this is a repeatable group. Now I kind of want to have a title field in each group, but then I need another repeatable group inside the group to have a list of images. I can't find a way to do that currently. I understand that endless nested repeatable groups is probably not something good to do. But I'm not sure how to best model such a slice otherwise, to stay flexible and the client can later add or remove groups. ---
**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:** [October 29, 2024, 1:36pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/2 "2024-10-29T13:36:19Z")
I know that I could do two separate repeatable groups, but I think that's not intuitive for the client and also everyone would need to make sure that the separate groups items fit and are in code combined. What if there are 5 titles, but only 4 lists of images for example? I theoretically could create another slice just for one item that has a title and a list of images, but then I would need an option to make a slice selectable as field in a repeatable group in my main slice. ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [October 29, 2024, 3:15pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/5 "2024-10-29T15:15:16Z")
Hi @jankohlbach, Nested repeatable groups are indeed not currently doable in Prismic. But there may be other ways to achieve what you want! Just so we're on the same page, you'd want to be able to repeat `category`, and those categories would have one `title` and repeatable `image` fields? Like this: ```auto ├── Repeatable Zone └── Category ├── Title └── Repeatable zone ├── Image ├── Image ├── Image └── Category ├── Title └── Repeatable zone ├── Image ├── Image ├── Image ``` If so, an alternative for what you're trying to do could be to create a custom type for what you're displaying inside the category (with a title field and a repeatable group of images), then use a [Content Relationship](https://prismic.io/docs/content-relationship) field in the category. In order to access and display that content, you can then use [GraphQuery](https://prismic.io/docs/rest-api/query-the-api/graphquery)to retrieve the linked document data. Like this: ```auto ├── Repeatable Zone └── Category ├── Content Field Relationship ``` And the Custom Type: ```auto ├── Title └── Repeatable zone ├── Image ├── Image ├── Image ``` Does that make sense? 🙂 ---
**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:** [October 29, 2024, 3:27pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/6 "2024-10-29T15:27:26Z")
That makes sense yes, and it's the structure I need. However, managing content for inside a slice somewhere else (as content type, same hierarchy as a page) and named completely different (slice \<-\> content type) is not something I would give a client or editor, think that's just too confusing. Would I would love to have is referencing another slice instead of a content type, then I could do what you proposed, but stay inside slices (obviously there's currently no way in the admin dashboard to edit something like this). Maybe for the future an idea to create a space to add something like reusable blocks, that then could be referenced in slices (would love to see that). If there's no other way, that's a bit sad, because I think two nested hierarchies are happening in almost every project I have at least once. More than that is very unlikely I guess, but 2 levels would be nice to create something like this. I guess the best thing I could do currently is then something like: ```auto ├── Repeatable Zone └── Category ├── Title ├── Repeatable Zone └── Category Content ├── Image ``` and then match them in the code, hoping that the client manages to keep the same number and order of repeatable zones not would I would ideally choose to do, but then at least everything is inside the slice together ---
**Author:** ![Ezekiel](https://avatars.discourse-cdn.com/v4/letter/e/848f3c/32.png) [@Ezekiel](https://community.prismic.io/u/Ezekiel)\ **Post date:** [October 29, 2024, 4:11pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/7 "2024-10-29T16:11:36Z")
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](https://community.prismic.io/t/content-modelling-multiple-blocks/14876/15): > > 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! ---
**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:** [October 29, 2024, 4:40pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/8 "2024-10-29T16:40:04Z")
alright, thanks at least now I know that I haven't overseen an obvious solution to this 😅 ---
**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:** [October 29, 2024, 5:24pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/10 "2024-10-29T17:24:15Z")
just seeing [Advanced groups in slices](https://prismic.io/updates/advanced-groups-in-slices) this though from the roadmap > In the process of designing the solution while talking to developers like you who use Prismic, we realized that groups within groups are complex and do not align with our vision of creating the simplest page builder for marketing websites. and like others, I have to disagree, I don't know why groups within groups would be complex, like mentioned 2 levels of nesting are pretty much needed for almost every normal website and yes, you said you focus on the 80% of standard use cases, but then I just have to HOPE that my case is covered? how can I sell the client a cms when I don't know yet if it's capable of managing their content think that's not a good direction to go honestly, and if it's not possible doing groups within groups because of other reasons like it could indefinitely expand and cost more (money? bandwidth?) or is not manageable in the admin editor, then please be honest about that and say that you want to create "the simplest page builder for marketing websites" but that means not having to send editors to custom content types just for adding some content that should live inside a slice ON the page, please keep that in mind I love the product, and I love and appreciate the recent updates in the whole product, but I need to know that the cms is capable of managing all my use cases BEFORE the project starts, and not hoping that I somehow can model it via some hacks, that's just my honest feedback ---
**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:** [October 31, 2024, 3:04pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/11 "2024-10-31T15:04:16Z")
Hi @jankohlbach, I'm Côme, I'm product manager for the developer tools team at Prismic. I wanted to share some additional details here. We indeed want to make the easiest page builder for marketing websites. But that doesn't mean we want to ignore complex cases as the one you shared. Because we know they exist and come quite often. But we believe that very often these use cases can be solved in a more elegant way, providing a great editor experience, than by adding an "all in one" generic feature. Here your example is perfect. The items you want to repeat inside the categories are actually just images. Said differently you want to make lists of images into a list of categories. This use case of repeating images, whether it's in a group field or not, is super common and we believe we can adress it specifically. Not coming with a final solution here, just ideas, but what if you could simply do this? ```auto `` └── Category (Group field) ├── Title (Key Text field) ├── Image gallery (Image field - repeatable) ``` ---
**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:** [November 4, 2024, 9:19am UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/12 "2024-11-04T09:19:37Z")
yeah, if I can repeat the group, sure also for this exact use case (there are others), a gallery field would also work for now, I made it like this: ![Screenshot 2024-11-04 at 10.15.47](https://europe1.discourse-cdn.com/flex013/uploads/prismic/original/2X/5/5aac3ab8e9d2494751f5c206f09c060ddb0fef37.png) that's the most dynamic version I can create which is still ok'ish for the editor because it's all in one place, but do I like it? no 😅 there should be no need to add a row number and also the title and images should be together looking forward to what you come up with, pretty sure it will work somehow, the development of the last months made me very happy, and I hope this will somehow be added so I can be more confident to choose prismic for clients ---
**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:** [January 28, 2025, 10:15am UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/14 "2025-01-28T10:15:28Z")
hey @come.sabran I really appreciate your efforts in making this better e.g. the repeatable links is exactly going in this direction wanted to ask if there is any update, especially on a gallery field for example use case: currently have a project, where the client will upload a lot of images that are displayed as a masonry grid layout it'll probably become tedious for the client to search and select a single image in a group 50 times for that grid and would be so much easier if he could just select 50 images from the media gallery and then maybe sort it, but these are in one field and then just used in the frontend gallery bit afraid that the client is not happy at all to select all images in a new field every time ... ps. also applied for the partner program since I've done a few projects and hope to do more, but haven't heard back, is there a typical timeframe that's needed there? ---
**Author:** ![benjamin.martin](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/benjamin.martin/32/8187_2.png) [@benjamin.martin](https://community.prismic.io/u/benjamin.martin)\ **Post date:** [January 29, 2025, 3:57pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/15 "2025-01-29T15:57:46Z")
Thanks for your message. Regarding the **gallery field** , it’s something we’ve seen requested before, and we’re going to take a closer look at how we can prioritize it. We’ll be evaluating this need further and will keep you updated if we have any news on this front! As for your **Partner Program application** , I’ve asked the team for a follow-up, so you should hear back soon. That said, don’t hesitate to reach out again if you don’t get a response in a reasonable time! Thanks again for your input 🚀 ---
**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:** [January 20, 2026, 6:39pm UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/16 "2026-01-20T18:39:56Z")
quick update question, is the gallery field still something that is considered or worked on would love to see this a million times more than any bs AI feature that is pushed in I have some clients that are photographers or simply need to add a lot of images in image grids or galleries and I simply cannot tell them to click through every single one on its own they need the option to bulk upload and drag&drop to sort - as simple as that ---
**Author:** ![Levi](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/levi/32/24_2.png) [@Levi](https://community.prismic.io/u/Levi)\ **Post date:** [January 22, 2026, 9:19am UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/17 "2026-01-22T09:19:51Z")
@jankohlbach Thanks for your feedback. Bulk image upload + quick drag-and-drop ordering for galleries is a real workflow need, especially for photographers and anyone managing large sets of images. At the moment, a dedicated gallery field (with the kind of bulk upload and sorting UX you’re describing) isn’t a priority on our roadmap, and I don’t want to overpromise on timing. That said, your use case is valid, and this feedback is helpful for how we evaluate what to build next. ---
**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:** [January 22, 2026, 9:23am UTC](https://community.prismic.io/t/what-would-be-the-best-way-to-model-such-twice-nested-slice/17899/18 "2026-01-22T09:23:54Z")
thanks for the reply then it has to be another cms for now for most of my clients, sad to hear, still hope you’ll integrate this sometime soon