feature: plan a student-support chatbot integration
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
调研方向
This is a roadmap issue, so start with the discussion and the agreed scope rather than code. Read ADR 0001 for the frontend/backend boundary, and check #22 and #24 for related student-product context. Done means the supported question set, example answers, provider and data-handling decisions are recorded in this issue before any implementation PR is opened.
由索引模型根据 Issue 内容生成。
描述
Student problem
Students should be able to ask for help with placement-practice topics, understand an explanation, and find relevant ProCoderJii learning resources without leaving the site.
Proposal
Plan and integrate a student-support chatbot. Start with a small, clearly defined scope: placement-topic guidance, explanations, and navigation to reviewed learning resources.
Use the existing Next.js frontend and ASP.NET Core backend boundary. Model-provider credentials and provider calls belong on the server. Select the provider, model, access policy and operating budget during design; this issue does not commit to a vendor or paid service.
Acceptance criteria
- Agree the initial supported student questions and example answers before implementation.
- Provide an accessible chat interface that works on mobile and desktop within the existing yellow brand design.
- Ground answers in reviewed project content where available, link the relevant sources, and clearly acknowledge unsupported questions or uncertain answers.
- Route model requests through the backend with bounded input/output sizes, rate limits and a defined cost ceiling.
- Keep credentials, private account data and portfolio drafts out of model context; document what chat data reaches the provider.
- Decide whether chat history is needed. Do not persist conversations by default without an agreed retention/deletion policy.
- Handle loading, failed requests and unavailable providers clearly while keeping the existing learning flows usable.
- Validate representative learning questions, source references, error handling and access boundaries before launch.
Planning and coordination
Roadmap proposal; design and implementation will be scheduled later. Keep discussion and agreed scope in this issue, then link implementation PRs to it. Follow ADR 0001 for frontend/backend boundaries and record any new product or data decisions before implementation.
Related: #22 (student-product roadmap), #24 (placement-practice games).
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 1
- 平均合并
- 8 小时 58 分钟
- 30 天内合并 PR
- 37
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
难度 2/5 1-3 小时 新手友好度 62/100
procoderji-com/procoderji#104 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
procoderji-com/procoderji#36 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 85/100
procoderji-com/procoderji#35 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 79/100
procoderji-com/procoderji#34 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 90/100
procoderji-com/procoderji#33 ·
维护者通常 1 天内回复
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug platform-android
难度 2/5 1-3 小时 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 条评论 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复