> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/shade-academy/shade-academy-zh/su-cai/asset-card-display.md).

# 素材卡片显示

资产卡片是你查看资产时所处的容器。Shade 目前支持网格列表、平铺或列视图。

{% embed url="<https://youtu.be/Hi2ElJcR3t0?si=881DevhZGuQGYY7L>" %}

<figure><img src="https://3843445310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FvyCUnSsubaYCE1Usd1SS%2FAsset%20Card%20Display.gif?alt=media&amp;token=92c45573-f494-4f9a-b512-ff5744cbc694" alt=""><figcaption></figcaption></figure>

### 视图选项

#### 网格

一种带平铺效果的网格视图，也可以包含资产元数据。请选择：

* 要显示的所需元数据属性
* 缩略图是适应还是填充
* 卡片大小

#### 列表

一种类似电子表格的文件和文件夹视图，包含列和行。请选择：

* 要显示的所需元数据属性
* 缩略图是适应还是填充
* 缩略图大小

#### 平铺

一种不显示元数据的视图，类似网格视图，资产缩略图与其对应的宽高比一致。请选择：

* 缩略图大小
* 缩略图的圆角或直角

#### 列

一种从左到右按文件夹层级展开的流式视图。请选择：

* 缩略图是适应还是填充
* 缩略图大小

### 自定义元数据显示

你可以向资产卡片添加自定义元数据字段，以显示更多信息：

* 创建自定义元数据属性（标签、文本、数字、复选框等）
* 选择在视图中可见的元数据字段
* 在网格和列表视图中查看元数据
* 在与客户共享集合时控制元数据可见性

### 扁平化目录视图

Shade 支持将目录扁平化，以电子表格样式显示跨文件夹的所有资产：

1. 在 Drive 中选择“显示”
2. 切换“扁平化目录”开关

这对于审阅跨多个文件夹的大量资产，或需要按元数据字段排序和筛选时尤其有用。

{% embed url="<https://youtu.be/J0gLCpTtdwQ?si=Fu5VCi3blirzaK6p>" %}


---

# 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://academy.shade.inc/shade-academy/shade-academy-zh/su-cai/asset-card-display.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.