> For the complete documentation index, see [llms.txt](https://sygnal.gitbook.io/sygnal-webflow-components/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sygnal.gitbook.io/sygnal-webflow-components/cc/experimental/merged-collection-list.md).

# Merged Collection List ⏸️

{% hint style="danger" %}
**R\&D RESULTS** \
Due to the nature of slots in Webflow's code components implementation, it's not possible to merge the collection lists server-side. 
{% endhint %}

## Goals

* Take several slotted collection lists 
* Merge all items into the first list structure in the slot

## Technical Notes

* All slotted items must be components, this includes collection lists 
* Ensure that you create these Components with the collection list itself as the root element 
* Merge is [client-side only](/sygnal-webflow-components/technical-notes/code-components/technical-notes/working-with-slotted-content.md) 

## R\&D 

* Determine at what point CSR completes 


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sygnal.gitbook.io/sygnal-webflow-components/cc/experimental/merged-collection-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.