> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/microsite-templates-explained.md).

# 微站模板说明

微型网站是专门构建的小型网站，仅向参与者提供计划信息。它们使用可视化编辑器构建。每个微型网站都支持多个页面。使用 *自动设置* 创建微型网站时，impact.com 会为已登录和未登录的参与者设置基本的网站结构，其中包含不同的布局和页面。我们还提供额外的布局和页面模板，供希望扩充网站内容的用户使用。

请参阅 [微型网站编辑器详解](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/microsites-overview.md) ，了解更多关于 *布局* 和 *页面* 的介绍，以及如何为它们打造品牌风格。

#### 布局模板

*布局* 是微型网站页面的容器。您可以添加希望在该布局中的所有页面上一致显示的组件，例如页眉和横幅。 *自动设置* 微型网站自带预制布局，您也可以添加更多布局。三种模板选项如下：

* **基本布局** - 用于整体内容。
* **已登录布局** - 用于已登录的参与者。
* **未登录布局** - 用于公开访问。

#### 页面模板

此外，还有各种页面模板可供选择。

{% tabs %}
{% tab title="仪表板页面" %}

* 计划说明部分
* 计划统计数据
* 推荐码和分享链接
* 分享按钮
  {% endtab %}

{% tab title="活动页面" %}
活动页面汇总了客户倡导者在您的微型网站中的计划活动。该页面包含计划统计数据和推荐记录表。
{% endtab %}

{% tab title="账户管理页面" %}
我们提供页面模板，供客户倡导者在使用网站的不同功能时访问。这些模板默认包含在 *自动设置* 微型网站中，但可以进行调整。账户管理模板包括：

* 编辑个人资料页面
* 404 页面
* 电子邮件验证页面
* 忘记密码页面
* 登录页面
* 注销页面
* 注册页面
* 重置密码页面
* 验证电子邮件页面
  {% endtab %}
  {% endtabs %}


---

# 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://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/microsite-templates-explained.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.
