Skip to content
This repository was archived by the owner on Mar 11, 2026. It is now read-only.

Commit 2cb6aad

Browse files
committed
docs: add DeerFlow docs design plan
1 parent 4a8697e commit 2cb6aad

File tree

2 files changed

+161
-0
lines changed

2 files changed

+161
-0
lines changed
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
# DeerFlow Agent Runner Docs Design
2+
3+
## Goal
4+
5+
Add DeerFlow Agent Runner documentation to AstrBot docs in the same style as the existing third-party Agent Runner pages, with both Chinese and English coverage.
6+
7+
## Scope
8+
9+
- Add dedicated DeerFlow setup pages in `zh` and `en`
10+
- Add DeerFlow to the Agent Runner sidebar groups
11+
- Update Agent Runner overview pages to surface the new entry
12+
- Update usage pages so the supported runner count and examples match current AstrBot behavior
13+
- Update high-level introduction pages that list third-party Agent Runners
14+
15+
## Source of Truth
16+
17+
The documentation should follow the current AstrBot implementation instead of guessing DeerFlow behavior. The relevant implementation lives in the main AstrBot repository:
18+
19+
- `astrbot/core/config/default.py`
20+
- `astrbot/core/agent/runners/deerflow/deerflow_agent_runner.py`
21+
- `dashboard/src/i18n/locales/zh-CN/features/config-metadata.json`
22+
- `dashboard/src/i18n/locales/en-US/features/config-metadata.json`
23+
24+
The documented DeerFlow-specific fields are:
25+
26+
- `deerflow_api_base`
27+
- `deerflow_api_key`
28+
- `deerflow_auth_header`
29+
- `deerflow_assistant_id`
30+
- `deerflow_model_name`
31+
- `deerflow_thinking_enabled`
32+
- `deerflow_plan_mode`
33+
- `deerflow_subagent_enabled`
34+
- `deerflow_max_concurrent_subagents`
35+
- `deerflow_recursion_limit`
36+
37+
## Content Strategy
38+
39+
Follow the structure already used by `Dify`, `Coze`, and `Alibaba Cloud Bailian Application`:
40+
41+
1. short introduction with supported version
42+
2. preparation section that points users to DeerFlow official deployment/config docs
43+
3. AstrBot-side configuration steps
44+
4. Agent Runner selection steps
45+
5. concise operational notes only when backed by code or official DeerFlow docs
46+
47+
The new pages should stay practical and avoid marketing language. They should not invent setup steps that are not validated by AstrBot or DeerFlow official docs.
48+
49+
## Navigation Changes
50+
51+
Update both locale sidebars under the Agent Runner section so DeerFlow appears beside the existing third-party runners.
52+
53+
## Related Copy Updates
54+
55+
Update summary pages that currently list only Dify, Coze, and Bailian so they also mention DeerFlow when describing supported third-party Agent Runners.
56+
57+
## Verification
58+
59+
Run `npm run docs:build` in the docs repository worktree after all edits.
Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
# DeerFlow Agent Runner Docs Implementation Plan
2+
3+
> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.
4+
5+
**Goal:** Add bilingual DeerFlow Agent Runner documentation and update related navigation and overview pages so DeerFlow is documented like the existing third-party runners.
6+
7+
**Architecture:** Create dedicated Markdown pages for DeerFlow in `zh` and `en`, then wire them into the VitePress sidebar and the Agent Runner overview/usage pages. Base every documented field and note on the current AstrBot DeerFlow integration so the docs match shipped behavior.
8+
9+
**Tech Stack:** VitePress, Markdown, `.vitepress/config.mjs`
10+
11+
---
12+
13+
### Task 1: Add planning artifacts
14+
15+
**Files:**
16+
- Create: `docs/plans/2026-03-08-deerflow-docs-design.md`
17+
- Create: `docs/plans/2026-03-08-deerflow-docs.md`
18+
19+
**Step 1: Write the validated design doc**
20+
21+
Describe the agreed documentation scope, source of truth, affected files, and verification approach.
22+
23+
**Step 2: Save the implementation plan**
24+
25+
Capture the file list, task order, and verification command for the DeerFlow docs work.
26+
27+
**Step 3: Commit the planning docs**
28+
29+
Run: `git add docs/plans/2026-03-08-deerflow-docs-design.md docs/plans/2026-03-08-deerflow-docs.md && git commit -m "docs: add DeerFlow docs design plan"`
30+
31+
Expected: a new commit containing only planning documents.
32+
33+
### Task 2: Add DeerFlow documentation pages
34+
35+
**Files:**
36+
- Create: `zh/providers/agent-runners/deerflow.md`
37+
- Create: `en/providers/agent-runners/deerflow.md`
38+
- Reference: `zh/providers/agent-runners/dify.md`
39+
- Reference: `en/providers/agent-runners/dify.md`
40+
- Reference: `astrbot/core/config/default.py` in the main AstrBot repo
41+
42+
**Step 1: Draft the Chinese page**
43+
44+
Document deployment prerequisites, AstrBot configuration fields, and runner selection steps using the same style as existing Chinese Agent Runner pages.
45+
46+
**Step 2: Draft the English page**
47+
48+
Mirror the same structure and verified fields in English.
49+
50+
**Step 3: Self-check content drift**
51+
52+
Verify the docs mention only real DeerFlow fields and supported defaults from the current AstrBot implementation.
53+
54+
### Task 3: Update navigation and related overview pages
55+
56+
**Files:**
57+
- Modify: `.vitepress/config.mjs`
58+
- Modify: `zh/providers/agent-runners.md`
59+
- Modify: `en/providers/agent-runners.md`
60+
- Modify: `zh/use/agent-runner.md`
61+
- Modify: `en/use/agent-runner.md`
62+
- Modify: `zh/what-is-astrbot.md`
63+
- Modify: `en/what-is-astrbot.md`
64+
65+
**Step 1: Add DeerFlow to both sidebars**
66+
67+
Insert DeerFlow under the `Agent 执行器` and `Agent Runners` sidebar groups.
68+
69+
**Step 2: Update quick links and overview text**
70+
71+
Add DeerFlow links to the overview pages and extend high-level descriptions to mention DeerFlow.
72+
73+
**Step 3: Fix supported runner counts**
74+
75+
Change the usage pages from four built-in runners to five, and add DeerFlow to the bullet lists and examples.
76+
77+
### Task 4: Verify and prepare PR
78+
79+
**Files:**
80+
- Verify: site-wide docs build output
81+
82+
**Step 1: Run the docs build**
83+
84+
Run: `npm run docs:build`
85+
86+
Expected: VitePress build completes successfully without new errors.
87+
88+
**Step 2: Review the diff**
89+
90+
Run: `git diff --stat && git diff`
91+
92+
Expected: only the intended DeerFlow docs, navigation, and related copy changes are present.
93+
94+
**Step 3: Commit the docs changes**
95+
96+
Run: `git add . && git commit -m "docs: add DeerFlow agent runner guide"`
97+
98+
Expected: a clean commit for the end-user documentation updates.
99+
100+
**Step 4: Open a pull request**
101+
102+
Push the branch and create a PR with a concise summary of the DeerFlow docs additions and navigation updates.

0 commit comments

Comments
 (0)