Hey @torceee here’s how I can envision this working. Create three CMS collections.
- Event Calendar collection
- Presentations collection
- Presenters collection
The Event Calendar would have a multi-reference field connected to the Presentations. This will bring in all the presentations for that event and display them on the Event template page using a collection list.
The Presentations would have a multi-reference field connected to the Presenters. This way each presentation can be assigned multiple presenters. They would appear on the Presentation template page. If you want the names of the presenters on the Event template page, you will need to use multiple single-reference fields. In the future when we get nested dynamic lists this will be possible through a multi-ref field too.
So the flow of info/pages goes from big picture to small picture as they drill down Events→Presentations→Presenters
You could also have a Locations collection that is referenced by the Events collection. Also a Rooms collection could be referenced by the Presentations. A profession collection could be referenced by the Presenters and so on and so on. There really is a lot of depth and dynamics that you could build here depending on the data you have to work with.
I see from your share link that you have a lot of collections already. It’s really about looking at the relationships between the data and giving it a hierarchy or flow that is intuitive to the visitor.
Here’s a great read from the blog about this topic. Hope this helps.