Skip to content

feat(discussion): add cohort-scoped peer discussion forum - #1165

Open
Umesh-369 wants to merge 1 commit into
vicharanashala:mainfrom
Umesh-369:discussion-forum
Open

Umesh-369 wants to merge 1 commit into
vicharanashala:mainfrom
Umesh-369:discussion-forum

Conversation

@Umesh-369

Copy link
Copy Markdown

What

Adds a Discussion Forum section to the course sidebar, letting students
in the same course + cohort ask and answer each other's questions.
Instructors/admins can view and moderate (pin/delete).

Why

Students currently have no in-app way to get peer help on doubts tied
to their specific cohort. This adds a lightweight, scoped Q&A space
without touching proctoring, quizzes, or grading.

Scope

  • New backend module: thread + reply CRUD, cohort-membership enforced
    server-side on every read and write.
  • New frontend section: sidebar entry, thread list, thread detail,
    new-thread composer — rendered in the existing course main panel,
    same color palette/components as the rest of the course UI.

Explicitly out of scope (v1)

Upvotes, nested replies, attachments, notifications, forum search,
accepted-answer marking — noted as follow-ups.

How to test

  1. vibe start frontend backend
  2. Log in as a student enrolled in [course]/[cohort A]; open the course,
    click Discussion Forum, create a thread, reply from a second account
    in the same cohort.
  3. Log in as a student in [cohort B] of the same course; confirm you do
    NOT see cohort A's threads.
  4. Log in as the course instructor; confirm threads from both cohorts
    are visible and you can delete a thread.
Screenshot 2026-07-18 231224 Screenshot 2026-07-18 231314 Screenshot 2026-07-18 232955

@github-actions github-actions Bot added frontend Changes to the frontend of the project backend labels Jul 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backend frontend Changes to the frontend of the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant