docs: casual UX PRD — pervasive inline explanations + help FAB - #9
Merged
Conversation
Sister doc to onboarding-prd.md (PR #7). Where onboarding-prd covers the registration FLOW (which steps run, in what order), this doc covers the configuration DENSITY (how much explanation accompanies every field, and which fields get hidden entirely for non-technical users). Key decisions: - New <FieldHint> component renders inline below labels for casual persona (always-visible 1-2 sentence plain-language hint) and as hover-popover for dev/team (low-density default for power users) - Casual mode hides advanced configuration entirely: currency toggle, custom topup amounts, redemption codes, /keys Advanced mode entry, /playground model parameters, /profile notification settings tab - New global <HelpFab> floating action button on all authenticated pages with workshop video URL / WeChat group / support email (admin-configurable, no hard-coded support contacts) - Workshop / video content stays operations-owned: product reads URLs from admin config, never tries to be the source of educational content. Placeholder when URLs unset. Implementation scope (PR #9): - <FieldHint> + <HideForCasual> + useIsCasual hook (~1 day) - <HelpFab> + admin config keys (~1 day) - Apply hints to /welcome wizard, /keys Simple cards, /onboarding tutorials, /wallet (~3 days) - ~5 days total, no platform/ops dependency Out of scope: - Workshop video production (ops) - WeChat group establishment + QR (ops) - Screenshot capture for tutorials (platform) - AI help bot (deferred to Phase 2) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
8 tasks
10 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
继 onboarding PRD (PR #7) 之后的姊妹 PRD：casual UX PRD。
两个 PRD 的分工：
Workshop / 视频 vs 产品的分工
DeepRouter 团队用 workshop / 视频引导用户怎么用 = 运营 & 内容团队职责。
产品层目标：让用户在没看视频、没问朋友、没加群的情况下，光看屏幕就能猜对每个配置。
两者互补：视频帮愿意学的用户；inline 解释帮没耐心的用户。
核心交付（PR #9 落地）
1. `` 标准组件
两种渲染模式：
2. Casual 模式下隐藏的高级字段
3. `` 全局求助浮窗
右下角浮窗，所有 _authenticated/* 页面都有：
Casual 用户首次访问带 NEW 红点。
4. 视频入口的 4 个植入点
所有视频 URL 从同一 admin 配置项读。
文案密度对照（示例）
Cherry Studio Base URL 配置
当前：
```
```
Casual 看到：
```
🌐 Base URL / API 地址：
https://deeprouter.ai/v1 [📋]
💡 粘到 Cherry Studio 的 "API 地址" 字段，
末尾不要加斜杠。
```
Dev 看到：
```
Base URL: https://deeprouter.ai/v1 [📋] ?
```
(hover ? 才看到说明)
工时
不依赖 platform / 运营准备：视频 URL / 微信群从 admin 配置读，没填就 fallback placeholder。
文件
仅新增一个文档：`docs/tasks/casual-ux-prd.md`（约 600 行）
关联
🤖 Generated with Claude Code