Create Admin Dashboard for Question Management

[MRIARC-08]

Admin backend endpoints are ready:

Backend Status: ✅ Complete

• Add question endpoint: POST /api/admin/add-question
• Seed NCERT endpoint: POST /api/admin/seed-ncert
• Role-based access ready

Frontend Work Required:

• Admin-only dashboard
• Question management interface
• Add/edit/delete questions
• Bulk NCERT seeding interface
• View user statistics
• Monitor platform health

Components to Create:

• src/components/AdminQuestionForm.tsx - Add/edit questions
• src/components/AdminQuestionList.tsx - List questions
• src/components/AdminSeedingPanel.tsx - Seeding controls
• Create src/app/admin/questions/page.tsx
• Update src/app/admin/page.tsx

Integration Points:

• POST /api/admin/add-question with question data
• POST /api/admin/seed-ncert with seeding config
• Handle admin-only access
• Show success/error messages

Expected Outcome: Complete admin interface for content management.

Related to backend: Admin Module

This is a GSSoC'26 contribution opportunity!

[Achiever199]

hi @MRIARC-08 , please assign this issue to me

[PranavAgarkar07]

Hey! I would like to work on the Admin Dashboard. My approach:

1. Create src/components/AdminQuestionForm.tsx — form for adding/editing questions with validation
2. Create src/components/AdminQuestionList.tsx — paginated table listing all questions with edit/delete actions
3. Create src/components/AdminSeedingPanel.tsx — UI for bulk NCERT seeding with progress feedback
4. Wire up to existing POST /api/admin/add-question and POST /api/admin/seed-ncert endpoints
5. Protect routes with admin-only role check middleware
6. Add success/error toast notifications

Can you assign this to me under GSSoC?

[pisum-sativum]

@MRIARC-08 Kindly assign me this issue

[Harryhist]

@MRIARC-08 Hi!
please assign me this issue

here is what I understood:
The backend is ready with POST /api/admin/add-question and
/api/admin/seed-ncert endpoints. We need to build a user-friendly
admin dashboard with three main components: a question form (add/edit),
a questions list, and a seeding panel.

My Proposed Approach:

1. Build AdminSeedingPanel first (most isolated,
   fewer dependencies). Gets a quick win and tests the endpoints early.

2. Create AdminQuestionForm with validation,
   handling both add and edit modes. Test against POST /api/admin/add-question.

3. Wire up AdminQuestionList, add error handling,
   success messages, and the role-based access layer.

4. Add loading states, pagination for large datasets,
   and update the main admin page.