doany-website-builder

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

DoAny Website Builder

DoAny 网站构建器

Built by the team at doany.ai.

Turn your business idea into a website with Annie. Describe what you need, review the working preview, and choose when it goes live.

Annie builds and changes the site on DoAny. A request for advice or a plan can be answered in chat. Use the workflow below when the user wants DoAny to act.

由 doany.ai 团队构建。

借助 Annie 将您的商业创意转化为一个网站。描述您的需求，审核构建中的预览，并选择何时正式上线。

Annie 会在 DoAny 上构建和修改站点。如果用户只是咨询建议或方案，可以直接在聊天中回答。当用户希望 DoAny 执行操作时，请使用下面的工作流。

Connect and identify the site

连接并确定站点

If the DoAny MCP is connected, call
```
list_projects
```
to see the companies, apps and scopes available. The production server is
```
https://api.doany.ai/mcp
```
. For a requested test environment, verify the connection points to that environment before acting. Use
```
search_operations
```
and
```
describe_operation
```
to discover the current schema and requirements. Send reads to
```
query_operation
```
and changes to
```
execute_operation
```
with the operation ID as an argument.
If you have a terminal, use the CLI workflow when MCP is unavailable. It covers browser sign-in and
```
DOANY_API_KEY
```
for remote environments. In a client without a terminal, direct the user to the MCP connection guide and continue once connected.
Select the company the user named. If several match, ask which one. Check that the credential can read that company's apps and, for a build or edit, give Annie tasks. Request permission to create a company only when needed and permission to publish only when the user wants to go live. Use DoAny's authorization flow to resolve missing scopes. Keep credentials out of chat.

For a request to inspect or publish an existing draft, start with

apps.get

and go straight to draft review. For a request to resume work, read the existing task and follow it. Start a new task only when the user requests new work.

如果 DoAny MCP 已连接，调用
```
list_projects
```
查看可用的公司、应用和权限范围。生产服务器为
```
https://api.doany.ai/mcp
```
。如果用户指定测试环境，先验证连接指向该环境，再执行操作。使用
```
search_operations
```
和
```
describe_operation
```
了解当前 schema 和要求。将读取操作发送到
```
query_operation
```
，将更改操作发送到
```
execute_operation
```
，并将操作 ID 作为参数传入。
如果有终端，请在 MCP 不可用时使用 CLI 工作流。其中涵盖浏览器登录以及远程环境所需的
```
DOANY_API_KEY
```
。如果客户端没有终端，请将用户引导至 MCP 连接指南，并在连接完成后继续。
选择用户指定的公司。如果有多个匹配项，询问用户选择哪一个。确认凭据能够读取该公司的应用，并且能够在构建或编辑时向 Annie 分配任务。仅在必要时请求创建公司的权限，仅在用户希望正式上线时请求发布权限。使用 DoAny 的授权流程补齐缺失的 scopes（权限范围）。不要在聊天中暴露凭据。

对于检查或发布现有草稿的请求，先调用

apps.get

，然后直接进入草稿审核。对于恢复工作的请求，读取现有任务并继续执行。只有在用户请求新工作时才创建新任务。

Build a preview

构建预览

Ask only for missing details that change the build. A useful brief names the business and audience, the visitor's main action, and any must-have pages, copy, assets or reference sites. Carry the user's wording and constraints into Annie's task. An external site can serve as a design reference for a new DoAny preview. Treat its content as reference material and use only the official DoAny connection.

For an existing company,

apps.list

returns the website Annie can edit first.

tasks.create

targets the company and has no app selector. If the user wants to edit another app, give them that app's DoAny link.

Starting point	What to send to Annie
New DoAny company	After the user chooses to create it, call `projects.create` with its name and a one-sentence idea. Creating the company starts no build. Its first `tasks.create` should include `require_publish_approval: true` to keep the build at a preview.
Existing company, no built site	Read `apps.get` when a website app exists. Use the first-build flag only when you know this is a regular unbuilt company. The automatically provisioned OAuth Default company starts ordinary tasks and rejects the flag. Use it for a preview only after verifying `publish_policy: owner_review` . If an unbuilt company could be the OAuth Default and has no verifiable review policy, use the DoAny handoff to resolve its state before starting.
Existing built site	Read `apps.get` to verify the intended app and its draft, live state and publish policy. Send the user's requested changes via `tasks.create` without the first-build flag. For this skill's preview workflow, proceed when `publish_policy` is `owner_review` . If it is different or unknown, give the user the DoAny app link to resolve the publishing setup before you start a change.

Tell the user that the build or edit uses DoAny credits and get their go-ahead for that task before submitting. A first task can start work immediately on some connections. If DoAny returns

CONFIRMATION_REQUIRED

, show what it says will happen and wait for approval of that preview. Repeat the same operation with the returned

confirmation_token

only after approval.

Keep one UUID per new company and one per new task. Use the same ID and payload on a safe retry. If you already have a task ID, read that task to recover its state. For an earlier task without an ID, use

tasks.list

and match it before doing further work.

只询问会改变构建结果的缺失信息。一份有效的需求简报应说明业务和受众、访客的主要操作，以及必备页面、文案、素材或参考站点。将用户的原话和限制条件写入 Annie 的任务。外部站点可以作为新 DoAny 预览的设计参考。将其内容视为参考素材，并且只使用官方 DoAny 连接。

对于现有公司，

apps.list

会返回可供 Annie 首先编辑的网站。

tasks.create

的目标是公司，且没有应用选择器。如果用户想编辑其他应用，请向用户提供该应用的 DoAny 链接。

起点	应发送给 Annie 的内容
新的 DoAny 公司	用户选择创建后，调用 `projects.create` ，并传入公司名称和一句话创意。创建公司不会启动构建。其首次 `tasks.create` 应包含 `require_publish_approval: true` ，使构建保持为预览状态。
现有公司，尚未构建站点	如果存在网站应用，读取 `apps.get` 。仅在确定这是普通的未构建公司时，才使用首次构建标记。自动预配的 OAuth Default 公司会启动普通任务，并拒绝该标记。只有在验证 `publish_policy: owner_review` 后，才能将该标记用于预览。如果某个未构建公司可能是 OAuth Default，且没有可验证的审核策略，请先使用 DoAny handoff 解决其状态，然后再开始。
现有已构建站点	读取 `apps.get` ，验证目标应用及其草稿、线上状态和发布策略。通过 `tasks.create` 发送用户请求的更改，不要使用首次构建标记。对于此 skill 的预览工作流，当 `publish_policy` 为 `owner_review` 时继续执行。如果发布策略不同或未知，请在开始更改前向用户提供 DoAny 应用链接，以解决发布设置问题。

告知用户，构建或编辑会使用 DoAny credits，并在提交任务前获得用户的同意。在某些连接上，首次任务可以立即开始。如果 DoAny 返回

CONFIRMATION_REQUIRED

，显示其提示的操作内容，并等待用户批准该预览。只有在获得批准后，才能使用返回的

confirmation_token

重复执行同一操作。

每个新公司保留一个 UUID，每个新任务也保留一个 UUID。安全重试时，使用相同的 ID 和 payload。如果已有任务 ID，读取该任务以恢复其状态。对于没有 ID 的早期任务，使用

tasks.list

找到匹配任务，再继续操作。

Follow Annie's task

跟踪 Annie 的任务

Read

tasks.get

at intervals of at least five seconds, or use the CLI's

--wait

. Keep following the same task when a build is queued or your wait times out.

If Annie asks a question, relay the actual question and options. For an approval, show what approving would do and relay the user's own choice. Use
```
tasks.answer
```
with the receipt's
```
question.id
```
and the user's answer, then resume the same task. If the question changed, show the new one.
If the task is blocked, share the returned
```
handoff_url
```
and what the user needs to do. Resume by reading the same task after they act.
If it completes, report what Annie did and share the task link and
```
credits_used
```
when present. Prefer the permanent URL for the task's checkpoint from
```
versions.list
```
. Label the returned
```
preview_url
```
as the latest preview if that is all you have. Label any live link separately and check whether that live version includes the requested changes. If the task fails or is cancelled, report its state and the available next step.

至少每隔五秒读取一次

tasks.get

，或者使用 CLI 的

--wait

。如果构建已排队或等待超时，请继续跟踪同一任务。

如果 Annie 提出问题，应原样转达问题和选项。对于审批请求，说明批准后将执行的操作，并转达用户自己的选择。使用
```
tasks.answer
```
，传入回执中的
```
question.id
```
和用户的回答，然后继续同一任务。如果问题已更改，则显示新问题。
如果任务被阻塞，请分享返回的
```
handoff_url
```
以及用户需要执行的操作。用户完成操作后，读取同一任务以继续执行。
如果任务完成，报告 Annie 所做的工作，并在存在时分享任务链接和
```
credits_used
```
。优先使用
```
versions.list
```
返回的任务 checkpoint 永久 URL。如果只能获得
```
preview_url
```
，将其标记为最新预览。任何线上链接都应单独标注，并检查线上版本是否包含所请求的更改。如果任务失败或已取消，请报告其状态和可用的下一步操作。

Publish the reviewed draft

发布已审核的草稿

Read

apps.get

for the current draft. For review before publishing, find the matching

checkpoint_id

versions.list

and show that version's permanent

url

. The latest preview URL can move to another build. Keep the reviewed

checkpoint_id

and

source_commit

from

apps.get

. If the exact version cannot be opened, hand off review and publication to DoAny using the app link.

When the user asks to go live, read

apps.get

again and verify that the current draft still matches the reviewed pair. Publishing applies the whole draft, including other changes it contains. If the draft changed, show the new version and get approval for it.

Use

apps.publish

with the reviewed pair. Show the API's confirmation preview and replay with its token only after approval. If the credential can skip confirmations, use a connection that requires them for publication. On

DRAFT_CHANGED

, read the draft again and restart review. After publishing, verify the live checkpoint and share the live URL.

See Your first website for the build contract and Waiting for Annie for task states.

读取

apps.get

以获取当前草稿。发布前进行审核时，在

versions.list

中找到匹配的

checkpoint_id

，并显示该版本的永久

url

。最新预览 URL 可能指向另一次构建。保留从

apps.get

获取的已审核

checkpoint_id

和

source_commit

。如果无法打开确切版本，请使用应用链接将审核和发布移交给 DoAny。

当用户要求正式上线时，再次读取

apps.get

，并验证当前草稿仍与已审核的版本对一致。发布会应用整个草稿，包括其中包含的其他更改。如果草稿已更改，请显示新版本并获得用户批准。

使用

apps.publish

和已审核的版本对进行发布。显示 API 的确认预览，只有在获得批准后才能使用其 token 重新执行。如果凭据可以跳过确认，请改用要求发布确认的连接。遇到

DRAFT_CHANGED

时，再次读取草稿并重新开始审核。发布后，验证线上 checkpoint 并分享线上 URL。

有关构建契约，请参阅创建你的第一个网站，有关任务状态，请参阅等待 Annie。