feature: plan a student-support chatbot integration

Ouverte
  • Quelque chose ne va pas ?
#103 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
csharp, nextjs, typescript
Domaine
ai, backend, frontend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:ai area:backend area:frontend enhancement

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).

Langage dominant
TypeScript
Étoiles
1
Forks
1
Merge moyen
8 h 58 min
PR mergées (30 j)
37

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de procoderji-com/procoderji

Toutes les issues de procoderji-com/procoderji

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.