[UX]: Missing regenerate/back-to-input flow after quiz generation

[AdityaP700]

Feature and its Use Cases

After quiz generation completes, users can edit individual questions or export (Google Form / PDF).

However, there is no clear way to:

• Regenerate the full quiz with same parameters
• Go back to the input screen while preserving content
• Adjust difficulty and regenerate
• Retry generation without refreshing the page

Given that generation may take several minutes and question quality may vary, users may need an iteration loop.

Current Behavior

• Input → Generate → Review → Export
• If unsatisfied, refresh page and re-enter everything

Expected Behavior

Proposed UI (Mockup)

After Quiz Generation:

┌─────────────────────────────────────────────────┐
│ ← Back to Input 🔄 Regenerate Quiz Export │
│ │
│ Difficulty: [Easy] [Medium ✓] [Hard] │
│ Questions: [5] [10 ✓] [15] [20] │
│ │
│ Question 1: What is... │
│ [Edit] [Delete] [Regenerate This One] │
│ ... │
└─────────────────────────────────────────────────┘
Consider adding:

• "Regenerate Quiz" action
• "Back to Input" navigation with preserved state
• Optional: difficulty adjustment post-generation

This would improve usability and align with modern AI-assisted workflows.

Additional Context

Related Work

• PR Allowing generated Q&A to be edited and shuffled #383 allows editing/shuffling individual questions
• Issue [BUG][Web] Navigation Redirects to Landing Page After Question Generation #384 fixed redirect behavior after generation
• Issue Adaptive and Explainable Quiz Generation #392 explores adaptive difficulty

However, none address full quiz regeneration or preserving input state for iteration.

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates

[AdityaP700]

Hi maintainers/contributors, I would like to know your insights about this issue and would like to know about any other edge cases , Thanks in anticipation!

[anurag-sinha04]

I would like to work on this enhancement

[Jaypal-Singh]

i would like to solve this problem , i have proper approch to solve it,

- State Persistence (Input Layer): : Modify Text_Input.jsx to utilize localStorage for saving all form states
Logic: On component mount, checking for and restoring these values. This ensures that when a user clicks "Back" from the Output page, their previous work is preserved.

Output Page Enhancements (UI/UX): :
Control Bar: Introduce a new control section in Output.jsx (sticky at the top or within the header) containing:
"Back to Input": A navigation button that returns to the input screen (now with preserved state).
"Regenerate Quiz": A button to re-trigger the generation process using the current (or updated) parameters.
"Difficulty Selector": A dropdown to adjust the difficulty level directly from the results page.

Regeneration Logic: Implement a handleRegenerate function in
Output.jsx
.
This function will retrieve the persisted parameters from localStorage, construct the API payload, and call the existing backend endpoints (/get_mcq, /get_shortq, etc.).
Upon success, it will update the qaPairs state directly, refreshing the view without a full page reload