> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/layout-manager/purpose-and-use.md).

# 目的和用途

### 布局管理器是确保文档类型配置正确、能够准确捕获和整理数据的重要工具。使用布局管理器有以下几个原因：

#### 结构化呈现：

* 布局管理器可帮助有序、结构化地呈现信息。
* 为不同的数据元素设置放置规则，可确保信息呈现一致、清晰。

#### 高效捕获数据：

* 使用布局管理器可帮助用户更高效地捕获信息。
* 设计良好的布局能让用户直观地知道应在哪里输入特定数据，从而加快数据捕获并降低出错风险。

#### 一致性：

* 一致的布局可确保文档格式保持统一。
* 不同文档使用相同的布局管理器时，可确保信息在这些文档中的呈现方式一致。
* 对于许多不同用户访问或协作处理文档的环境，这一点尤为重要。

#### 适应性：

* 布局管理器可根据需求自定义文档的外观。
* 根据文档类型或具体需求，可以自定义布局，以便更好地呈现不同类型的数据或信息。

#### 可扩展性：

* 配置良好的布局管理器可让文档更容易扩展。
* 添加新数据或需求发生变化时，可以自定义布局以轻松适应这些变化，而无需进行大规模重新设计。

总体而言，使用布局管理器对于确保准确捕获和整理数据至关重要。设计良好的布局能够改善用户体验、提高数据录入效率，并有助于保持文档的一致性和适应性。


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/layout-manager/purpose-and-use.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.