# How to use a slice in repeatable zone?

**URL:** <https://community.prismic.io/t/how-to-use-a-slice-in-repeatable-zone/13905>\
**Category:** Developing with Prismic\
**Created:** [August 20, 2023, 9:11am UTC](https://community.prismic.io/t/how-to-use-a-slice-in-repeatable-zone/13905 "2023-08-20T09:11:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![james-dd-36](https://avatars.discourse-cdn.com/v4/letter/j/bc8723/32.png) [@james-dd-36](https://community.prismic.io/u/james-dd-36)\
**Post date:** [August 20, 2023, 9:11am UTC](https://community.prismic.io/t/how-to-use-a-slice-in-repeatable-zone/13905/1 "2023-08-20T09:11:18Z")

</div>

So far my experience developing a client's website with Prismic has mostly been pain-free, but I've found one area which appears to be lacking documentation, and confusing because there was previously a different way of doing this (using 'group' fields). I would really appreciate clarity on this as there is no clear answer.

I created a Carousel component which has an image and a subtitle field both in the repeatable zone, so I could add as many images / subtitles as I wanted.

Now I want to create a more complex component that has 3 tabs and depending on the tab which is selected it will load a different carousel containing different images / subtitles.

It appears the old way to do this was to add a group field (which contains image / subtitle fields in itself), but since then Prismic has changed their API and it's unclear how to achieve this.

Please enlighten me. Thanks.

---

<div class="post-metadata">

**Author:** ![Pau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.prismic.io/pau/32/5422_2.png) [@Pau](https://community.prismic.io/u/Pau)\
**Post date:** [August 21, 2023, 8:55am UTC](https://community.prismic.io/t/how-to-use-a-slice-in-repeatable-zone/13905/3 "2023-08-21T08:55:42Z")

</div>

The repeatable zone inside a slice works similarly to a group field. The primary distinction is that you can incorporate a group field at the top level of your documents. These are two distinct content modeling concepts. However, it's essential to understand that you cannot nest slices within a group field.

To establish connections between content documents, you can use content relationship fields. This allows you to associate specific pieces of content with each other.