Hey there, I’m struggling to get CMS nest to work after going through the documentation and implementing it on my site:
Any help would be appreciated:
here is a read-only link as well.
Hey there, I’m struggling to get CMS nest to work after going through the documentation and implementing it on my site:
Any help would be appreciated:
here is a read-only link as well.
Hey @caleb.raney,
We can see what’s happening with your CMS Nest setup. The issue has two parts, and the second one is the key piece that’s missing.
CMS Nest works by pulling data from a Collection List on a CMS Template page (like your Session template) and injecting it into nest-target divs on your static page (like your Agenda page). Both sides need to be configured for nesting to work — and right now, you’re missing the template page side entirely.
Fix the Attribute Syntax on Your Static Page
In your HTML, you currently have:
<div nest-target="speakers" fs-list-element="nest-target">
Change this to TWO separate attributes:
<div fs-list-element="nest-target" fs-list-nest="speakers">
The fs-list-nest=“speakers” needs to be its own attribute, not combined with nest-target=.
Set Up the Missing Template Page Source (This is Critical)
This is the main issue — you need to create the source Collection List on your Session Template page:
Without the template page setup, CMS Nest has nowhere to pull the speaker data from — the nest-target divs on your static page are just empty containers waiting for content that never arrives.
Once you’ve made these changes, the speakers should automatically nest into each session on your published Agenda page. Feel free to share your staging link or read-only link again after making these updates, and we’ll double-check everything is connected correctly ![]()
Thank you! I had mixed up two data attributes on the target element as you pointed out and that’s what was breaking it. Seems to be working now, really appreciate the help!