> For the complete documentation index, see [llms.txt](https://doc.qrspace.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.qrspace.dev/zhi-shi-zheng-li-yu-zi-liao-shou-ji/universal-collections.md).

# 萬能集合容器

{% hint style="info" %}
**目前實際狀況**：集合可以放**文字和圖片**：打字、貼上、從網頁拖進來、拍目前的畫面、從摘錄和剪貼挑、網頁右鍵「加入集合」。可以建很多個集合、自己取名、拖曳或 Alt+↑↓ 排順序；放進來的都是複製一份。

* **本機檔案（PDF、DOCX、ZIP…）還不能放**。
* 網址目前是記成文字或圖片的來源，不是單獨的網址卡片。
  {% endhint %}

「集合」（Universal Collections）是口袋瀏覽器的全能資料儲存槽，支援拖入與存放各種類型的資訊素材。

***

## 為什麼需要萬能集合容器

在日常作業中，一個專案往往包含多種型態的碎片資料：

* 幾段參考文字
* 數張設計截圖
* 幾份本機 PDF 或試算表檔案
* 數條關鍵網頁連結

若將文字存便簽、圖片丟桌面、檔案放下載區、連結塞書籤，資訊便會完全割裂。「集合」提供一個無格式限制的通用收納箱：所有東西都可以放進來。

***

## 支援的資料型態

| 資料型態     | 收納方式                          | 面板呈現與互動                  |
| -------- | ----------------------------- | ------------------------ |
| **網址連結** | 拖曳網址列或網頁超連結至集合                | 呈現為含有網站圖示、標題與網域的互動卡片     |
| **文字片段** | 選取網頁文字後直接拖入                   | 呈現為純文字卡片，附帶來源標註與字數統計     |
| **圖片**   | 拖曳網頁圖片或本機圖片檔至集合               | 呈現為視覺預覽縮圖，點擊可放大檢視        |
| **本機檔案** | 自檔案總管直接拖入各類文件（PDF、DOCX、ZIP 等） | 呈現為檔案卡片，可直接在瀏覽器預覽或呼叫系統開啟 |

***

## 整理與使用方式

### 1. 拖曳即收納

集合面板支援全域拖放。無論是從網頁內部、桌面或是其他軟體，只要將目標拖曳至集合面板中釋放，系統即刻完成收納。

### 2. 標籤與分組

在集合中可建立專案標籤（例如「專案 A 調研」、「稅務憑據」、「設計參考」），將不同型態的物件歸入同一個邏輯群組。

### 3. 一鍵呼叫與調用

當需要在其他網頁表單或郵件中引用這些資料時，可直接自集合面板中將文字或檔案拖曳送出。


---

# 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://doc.qrspace.dev/zhi-shi-zheng-li-yu-zi-liao-shou-ji/universal-collections.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.
