> 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/5-yuan-su-de-ceng-ji.md).

# 5 元素的層級

點選左側menu來欄位或是按下快速鍵 Z 可以打開元素層級。&#x20;

![](https://i.imgur.com/jLXkdpV.png)

你可以切到 CSS 樣式面板或 HTML 屬性的版面，對元素進行進一步設計調整，也可以針對層級去做拖拉。&#x20;

![](https://i.imgur.com/9ThbhlQ.png)

另外要注意的是，由於元素模型本身的限制，入當前的元素沒辦法放入目標位置，這時候頁面上就會出現提示變紅，也就是無法移動。（如下圖）

![](https://i.imgur.com/5NIsdFB.png)


---

# 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/5-yuan-su-de-ceng-ji.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.
