> 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 会设置一个基础站点结构，其中包含适用于已登录和未登录参与者的不同布局和页面。还会为那些希望为其站点添加更多内容的人提供额外的布局和页面模板。

请参阅 [微型站点编辑器说明](/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.