# Nested Reference Publishing

### About this export

| Field | Value |
| --- | --- |
| **content_type** | lesson |
| **platform** | contentstack-academy |
| **source_url** | https://www.contentstack.com/academy/courses/publishing-content/nested-reference-publishing |
| **course_slug** | publishing-content |
| **lesson_slug** | nested-reference-publishing |
| **markdown_file_url** | /academy/md/courses/publishing-content/nested-reference-publishing.md |
| **generated_at** | 2026-04-28T06:55:48.631Z |

> Part of **[Publishing Content](https://www.contentstack.com/academy/courses/publishing-content)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys.

<!-- ai_metadata: {"lesson_id":"03","type":"video","duration_seconds":160,"video_url":"https://cdn.jwplayer.com/previews/CbfudGAL","thumbnail_url":"https://cdn.jwplayer.com/v2/media/CbfudGAL/poster.jpg?width=720","topics":["Nested","Reference","Publishing"]} -->

#### Video details

#### At a glance

- **Title:** Nested Reference Publishing
- **Duration:** 2m 40s
- **Media link:** https://cdn.jwplayer.com/previews/CbfudGAL
- **Publish date (unix):** 1756311270

#### Streaming renditions

- application/vnd.apple.mpegurl
- audio/mp4 · AAC Audio · 113986 kbps
- video/mp4 · 180p · 180p · 234378 kbps
- video/mp4 · 270p · 270p · 347950 kbps
- video/mp4 · 360p · 360p · 426263 kbps
- video/mp4 · 406p · 406p · 498099 kbps
- video/mp4 · 540p · 540p · 721349 kbps
- video/mp4 · 720p · 720p · 1059640 kbps
- video/mp4 · 1080p · 1080p · 2175135 kbps

#### Timed text tracks (delivery)

- **thumbnails:** `https://cdn.jwplayer.com/strips/CbfudGAL-120.vtt`

#### Transcript

If your content has lots of connected pieces, like an article that pulls in related images or product pages that reference other entries, publishing can get tricky. You don't want to push the main entry live and forget about something it depends on. That's where Nested Reference Publishing comes in. It lets you publish an entry or a group of entries and all the entries and assets they reference up to 5 levels deep in one go. So nothing gets left behind. You'll see Nested Reference Publishing in action whenever you click Publish on an entry that has references. After you pick your environments and languages, a second modal called Publish References appears. This is a tree view showing your parent entry at the top with all of its nested references underneath. You can expand each level to see what's included. If you're happy, click Send with References and everything gets published together. This works for single entries or bulk publishing multiple parent entries at once. Why is this helpful? Well, without this feature, you'd have to track down and publish each referenced entry or asset manually, and it's easy to miss something. Nested Reference Publishing ensures you're sending the latest version of everything in that structure across all the environments and languages you select. If something can't be published, maybe it's missing required fields or stuck in an earlier workflow stage or needs approval, you'll see a warning icon in the tree. However, hover over it to learn why. You can even jump directly to that entry, fix the issue, and return to Publish again. One important detail. If a child entry fails validation, its own nested references won't be published either. Once you send it, your job appears in the Publish queue as a bulk action. There's a new summary column showing how many items published successfully and how many are still in progress, and if any failed or were skipped or need approval, you can click into the job to see the full breakdown of each item. Nested Reference Publishing takes the guesswork out of publishing complex content. One action and everything connected goes live, saving you time, reducing mistakes, and making sure your audience sees the complete picture the moment you hit Publish.

#### Subtitles (WebVTT)

```webvtt
WEBVTT

1
00:00:00.000 --> 00:00:06.260
If your content has lots of connected pieces, like an article that pulls in related images

2
00:00:06.260 --> 00:00:11.900
or product pages that reference other entries, publishing can get tricky.

3
00:00:11.900 --> 00:00:17.100
You don't want to push the main entry live and forget about something it depends on.

4
00:00:17.100 --> 00:00:21.380
That's where Nested Reference Publishing comes in.

5
00:00:21.380 --> 00:00:27.080
It lets you publish an entry or a group of entries and all the entries and assets they

6
00:00:27.080 --> 00:00:31.520
reference up to 5 levels deep in one go.

7
00:00:31.520 --> 00:00:33.760
So nothing gets left behind.

8
00:00:33.760 --> 00:00:39.680
You'll see Nested Reference Publishing in action whenever you click Publish on an entry

9
00:00:39.680 --> 00:00:41.680
that has references.

10
00:00:41.680 --> 00:00:48.960
After you pick your environments and languages, a second modal called Publish References appears.

11
00:00:48.960 --> 00:00:54.360
This is a tree view showing your parent entry at the top with all of its nested references

12
00:00:54.360 --> 00:00:55.760
underneath.

13
00:00:55.760 --> 00:00:59.280
You can expand each level to see what's included.

14
00:00:59.280 --> 00:01:04.880
If you're happy, click Send with References and everything gets published together.

15
00:01:04.880 --> 00:01:10.420
This works for single entries or bulk publishing multiple parent entries at once.

16
00:01:10.420 --> 00:01:11.760
Why is this helpful?

17
00:01:11.760 --> 00:01:17.440
Well, without this feature, you'd have to track down and publish each referenced entry

18
00:01:17.440 --> 00:01:22.080
or asset manually, and it's easy to miss something.

19
00:01:22.080 --> 00:01:26.900
Nested Reference Publishing ensures you're sending the latest version of everything in

20
00:01:26.900 --> 00:01:33.360
that structure across all the environments and languages you select.

21
00:01:33.360 --> 00:01:38.640
If something can't be published, maybe it's missing required fields or stuck in an earlier

22
00:01:38.640 --> 00:01:44.080
workflow stage or needs approval, you'll see a warning icon in the tree.

23
00:01:44.080 --> 00:01:47.400
However, hover over it to learn why.

24
00:01:47.400 --> 00:01:54.520
You can even jump directly to that entry, fix the issue, and return to Publish again.

25
00:01:54.520 --> 00:01:56.240
One important detail.

26
00:01:56.240 --> 00:02:03.040
If a child entry fails validation, its own nested references won't be published either.

27
00:02:03.040 --> 00:02:07.640
Once you send it, your job appears in the Publish queue as a bulk action.

28
00:02:07.640 --> 00:02:12.480
There's a new summary column showing how many items published successfully and how

29
00:02:12.480 --> 00:02:18.160
many are still in progress, and if any failed or were skipped or need approval, you can

30
00:02:18.160 --> 00:02:22.800
click into the job to see the full breakdown of each item.

31
00:02:22.800 --> 00:02:28.040
Nested Reference Publishing takes the guesswork out of publishing complex content.

32
00:02:28.040 --> 00:02:34.400
One action and everything connected goes live, saving you time, reducing mistakes, and making

33
00:02:34.400 --> 00:02:40.160
sure your audience sees the complete picture the moment you hit Publish.

```

```transcript
<!-- PLACEHOLDER: replace with real transcript before publish if cues were auto-derived from WebVTT -->
[00:00] If your content has lots of connected pieces, like an article that pulls in related images
[00:06] or product pages that reference other entries, publishing can get tricky.
[00:11] You don't want to push the main entry live and forget about something it depends on.
[00:17] That's where Nested Reference Publishing comes in.
[00:21] It lets you publish an entry or a group of entries and all the entries and assets they
[00:27] reference up to 5 levels deep in one go.
[00:31] So nothing gets left behind.
[00:33] You'll see Nested Reference Publishing in action whenever you click Publish on an entry
[00:39] that has references.
[00:41] After you pick your environments and languages, a second modal called Publish References appears.
[00:48] This is a tree view showing your parent entry at the top with all of its nested references
[00:54] underneath.
[00:55] You can expand each level to see what's included.
[00:59] If you're happy, click Send with References and everything gets published together.
[01:04] This works for single entries or bulk publishing multiple parent entries at once.
[01:10] Why is this helpful?
[01:11] Well, without this feature, you'd have to track down and publish each referenced entry
[01:17] or asset manually, and it's easy to miss something.
[01:22] Nested Reference Publishing ensures you're sending the latest version of everything in
[01:26] that structure across all the environments and languages you select.
[01:33] If something can't be published, maybe it's missing required fields or stuck in an earlier
[01:38] workflow stage or needs approval, you'll see a warning icon in the tree.
[01:44] However, hover over it to learn why.
[01:47] You can even jump directly to that entry, fix the issue, and return to Publish again.
[01:54] One important detail.
[01:56] If a child entry fails validation, its own nested references won't be published either.
[02:03] Once you send it, your job appears in the Publish queue as a bulk action.
[02:07] There's a new summary column showing how many items published successfully and how
[02:12] many are still in progress, and if any failed or were skipped or need approval, you can
[02:18] click into the job to see the full breakdown of each item.
[02:22] Nested Reference Publishing takes the guesswork out of publishing complex content.
[02:28] One action and everything connected goes live, saving you time, reducing mistakes, and making
[02:34] sure your audience sees the complete picture the moment you hit Publish.
```

#### Key takeaways

- Connect **Nested Reference Publishing** back to your stack configuration before moving to the next module.
- Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment.
- Re-read the delivery versus management boundary for anything you changed in the entry model.

## Supplement for indexing

### Content summary

Nested Reference Publishing. Nested Reference Publishing in Publishing Content (publishing-content).

### Retrieval tags

- Nested
- Reference
- Publishing
- publishing-content
- lesson 03
- Nested Reference Publishing
- publishing-content lesson

### Indexing notes

Index this lesson as a primary chunk tagged with lesson_id "03" and topics: [Nested, Reference, Publishing].
Parent course slug: publishing-content. Use asset_references URLs as thumbnail hints in search results when present.
Never surface LMS quiz content or assessment answers from this file.

### Asset references

| Label | URL |
| --- | --- |
| Video thumbnail: Nested Reference Publishing | `https://cdn.jwplayer.com/v2/media/CbfudGAL/poster.jpg?width=720` |

### External links

| Label | URL |
| --- | --- |
| Contentstack Academy home | `https://www.contentstack.com/academy/` |
| Training instance setup | `https://www.contentstack.com/academy/training-instance` |
| Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` |
| Contentstack documentation | `https://www.contentstack.com/docs/` |
