Can a CMS collection contain collections as an item?
Robin not sure how you want to setup, I have been trying nesting and nest cross components, makes my head hurt
Aloha Steve,
I’m trying to see if it is possible to create a mechanism for reading a process manual using the CMS. I have the basic concept working just fine, but because there are sub-items in each of the steps of the process, it really needs the ability to have items in a collection that are collections themselves.
I don’t think it is possible, but I can’t be sure. Was hoping @ben could shed some light on the feasibility.
I think what you’re describing is a relationship between two Collections. For example, you’d have a list of Products, each Product would have one or more Variants, and you’d want to display that Product → Variant relationship. Is that correct?
At the moment, automatically loading or nesting child Collections like this isn’t supported.
@ben Yes, that is close to what I’m trying to attempt. Except in my case, there are a bunch of top-level topics that, in turn, have sub-items drilling down into more detail on a topic.
I didn’t think this was possible, which was why I was asking. It means I will have to expose all of the processes as a single list, instead of being able to nest some of them.
I think you might want to look at your approach slightly different.
One of the things I’ve been working on is using the CMS for different sections of a site. Each section has a different set of articles. Thus, each section has a different Collection, and I’ve created sub-folders in the CMS for each one. Thus on the page for Section 1 I create a Collection Component that points to one sub-folder, on the page for Section 2 I create a Collection Component that points to a different sub-folder, and so on.
I’m not sure why I’d want a list of lists, which is what embedding a collection within a collection would produce (if it could be done), as this starts to send users down a click tunnel and you’re also going to need a very visible breadcrumb component otherwise they’re likely to get lost. Users are, however, very familiar with menus with different levels, so I’d use that as the organizer.
Yes, I can see where the approach you have described would work.
But in my case I’m trying to document a process where I do not want the reader to have to go to different pages in order to read difference parts of the process. I would like it all present on a single page where they can easily read the various topics and sub-topics.
So the list if topics is more like a table of contents than anything else. I cna accomplish something similar with a flat list but it gets way to long requiring scrolling by the user. But it appears that might be the only option in the short term.