> For the complete documentation index, see [llms.txt](https://docs.tenten.co/docs-webflow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tenten.co/docs-webflow/webflow-101/changelog/2023/yuan-jian-xian-zai-ke-yi-zai-ji-he-qing-dan-zhong-shi-yong.md).

# 元件現在可以在集合清單中使用

基於上個月[對組件的改進](https://webflow.com/feature/improvements-to-components)，今天我們進行了另一項強烈要求的更新：允許您將組件添加到集合列表，並將 CMS 數據連接到組件屬性。&#x20;

這可讓您重複使用已轉換為 CMS 內容元件的常見設計模式，同時將這些佈局與網站上元件的所有其他實例保持同步。

以下是新內容的簡要概述：

* **將組件新增至集合清單。**&#x73FE;在可以將元件拖曳到 CMS 集合清單以及 CMS 頁面**範本**
* **將集合清單中的元素轉換為元件。**&#x96C6;合清單項目中的元素現在可以轉換為元件，就像任何其他元素一樣

<figure><img src="https://cdn.prod.website-files.com/64f9399ca7d13575ff21a675/64f9399ca7d13575ff21d678_SYBG_CMSCollectionItemComponents_2400x1400%20(1).jpg" alt=""><figcaption><p>元件現在可以在集合清單中使用</p></figcaption></figure>

[在這篇 Webflow University 文章](https://university.webflow.com/lesson/components#how-to-use-components-in-collection-lists-and-collection-pages)中了解有關建立、管理和修改元件的更多資訊。&#x20;


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tenten.co/docs-webflow/webflow-101/changelog/2023/yuan-jian-xian-zai-ke-yi-zai-ji-he-qing-dan-zhong-shi-yong.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
