> 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/yin-ru-yong-wu-yi-dong-yuan-su-de-xin-jian-pan-kuai-jie-jian.md).

# 引入用於移動元素的新鍵盤快捷鍵

今天，我們引入了鍵盤快捷鍵，使用戶能夠更有效、更精確地在 Webflow 畫布上移動元素，從而減少對滑鼠和導航器的需求。

<figure><img src="https://cdn.prod.website-files.com/64f9399ca7d13575ff21a675/64f9399ca7d13575ff21d682_TN_Move%20after%20sibling%20element.webp" alt=""><figcaption><p>引入用於移動元素的新鍵盤快捷鍵</p></figcaption></figure>

‍

這些快捷鍵可讓您在畫布上移動元素：

* 將元素移到上一個元素之前：**\[**&#x6216;**Command** +**向下鍵**(Mac) 或**Control** +**向下鍵**(Windows)
* 將元素移到上一個元素之後：**]**&#x6216;**Command** +**向上鍵**(Mac) 或**Control** +**向上鍵**(Windows)
* 將元素移到目前父級中的同級元素之前：**Command** + **\[**&#x6216;**Command** + **Left** (Mac) 或**Control** + **Left** (Windows)
* 在目前父級中的同級元素之後移動元素：**Command** + **]**&#x6216;**Command** +**向右鍵**(Mac) 或**Control** +**向右鍵**(Windows)
* 將元素移到父元素之前：**Command** + **Shift** +**向上鍵**(Mac) 或**Control** + **Shift** +**向上鍵**(Windows)
* 將元素移到父元素之後：**Command** + **Shift** +**向下**(Mac) 或**Ctrl + Shift + 向下**(Windows)

‍

要了解有關這些新快捷命令如何運作的更多信息，請查看我們[關於 Webflow University 的文章](https://university.webflow.com/lesson/keyboard-shortcuts#move-element-shortcuts)。


---

# 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/yin-ru-yong-wu-yi-dong-yuan-su-de-xin-jian-pan-kuai-jie-jian.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.
