feat: add persistent course bookmarks and student wishlist

[Jidnyasa-P]

Description

Students can browse and search courses, but they currently have no way to save interesting courses for later without enrolling.

Add a persistent wishlist that allows authenticated students to bookmark courses and manage them from a dedicated dashboard section.

Proposed Features

• Add a bookmark button to:

  • Course cards
  • Course detail pages

• Add a dedicated Saved Courses page.

• Store bookmarks per authenticated user.

• Prevent duplicate bookmarks.

• Allow bookmarks to be removed.

• Show whether a course is already saved.

• Add filters by:

  • Category
  • Free or paid
  • Course availability

• Add sorting by:

  • Recently saved
  • Course title
  • Price

• Display a saved-course count in navigation.

• Remove or clearly mark deleted courses.

• Add optimistic UI updates with rollback on failure.

• Include loading, empty, and error states.

Backend Requirements

Create bookmark endpoints to:

• Save a course
• Remove a saved course
• Retrieve the current user’s saved courses
• Check whether one or more courses are saved

Store bookmarks using either:

• A dedicated bookmark model, or
• A user wishlist field containing course references

Enforce uniqueness using user ID and course ID.

Frontend Requirements

Create reusable components or hooks such as:

• BookmarkButton
• SavedCourses
• useBookmarks

The bookmark state should stay consistent across catalog cards, course details, and the saved-courses page.

Acceptance Criteria

• Authenticated students can bookmark courses.
• Duplicate bookmarks are prevented.
• Students see only their own saved courses.
• Bookmark state remains correct after page refresh.
• Bookmark state stays synchronized across pages.
• Students can remove saved courses.
• Saved courses can be filtered and sorted.
• Deleted courses are handled safely.
• Loading, empty, and error states are implemented.
• The interface is keyboard accessible.
• Existing enrollment functionality is unaffected.

Kindly assign this issue to me under ECSOC26

[Jidnyasa-P]

/assign

[github-actions]

@Jidnyasa-P, you are already assigned to 2 open issues. Please complete those before taking on new ones (limit is 2).

[udaycodespace]

@Jidnyasa-P Assigned this issue to you all the best!

Before starting, please note the review requirements for this issue.

When you open the PR, please include actual testing evidence, not just screenshots or code snippets.

Required:

• Terminal output showing backend validation (e.g. npm test, node --check, or other relevant commands)
• Terminal output showing a successful frontend production build (npm run build)
• Terminal output for any lint/test commands you ran
• Actual UI screenshots/GIFs demonstrating the implemented feature (not just code)
• API testing evidence (Postman/cURL/Thunder Client) showing expected request/response and authorization where applicable
• Brief explanation of what you tested and the expected vs. actual behavior

PRs without sufficient testing evidence may be requested for additional changes before review.

[udaycodespace]

Hi @Jidnyasa-P, just checking in on this issue. Are you still working on it?

If so, could you please share a quick progress update and let me know when you expect to open the PR? Thanks!

[Jidnyasa-P]

I will submit the PR by tomorrow

[udaycodespace]

I will submit the PR by tomorrow

No issue, take your time. Thanks for the update!

[github-actions]

@Jidnyasa-P this issue has been unassigned automatically after 3 days of inactivity with no linked PR. It is now open for other contributors.

If you still want to work on it, comment again with /assign and share your approach.

[Jidnyasa-P]

/claim