Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancements and Fixes: User Flow, and Bug Fixes, implementing quick testing #9

Open
5 of 9 tasks
dhextras opened this issue Nov 14, 2023 · 2 comments
Open
5 of 9 tasks

Comments

@dhextras
Copy link

dhextras commented Nov 14, 2023

Issue Title: Enhancements and Fixes: User Flow, UI Updates, and Bug Fixes

What Needs To Change:

  1. Features to Add:
    - Add Issue template to the root directory .github/issue_template.md.
    - Modify the home page layout:
    - Display the sign-in option prominently.
    - Replace "Getting Started" with a "Test" button for quick access.
    - Implement testing functionality without requiring sign-in.
    - Prompt users to sign in after completing a test to save progress.
    - Upon login, redirect users to the navigation page /nav instead of the home page.
    - Separate the test and exercise sections within the /nav page for user convenience.
    - Introduce a brief pause between each question during tests for a more comfortable experience.
    - Check and rectify the issue causing an everlasting loop in exercises, possibly due to a mismatch between the number of test exercises and the daily quota.
    - Add proper instructions to each exercise for clear guidance and understanding.
  1. Bugs to Fix:
    - Ensure the signup page redirects to the home page upon successful verification, even if verification occurred on another device.
    - Keep users directed to the Nav page once logged in until they choose to log out, preventing redirection to the home page.

Definition of Done:

  • Features Added:

    • The home page should prominently display sign-in and a direct "Test" button.
    • Users can undergo testing without initial sign-in, prompted to sign in after completion.
    • Navigation structure in the Nav page separates test and exercise sections for user clarity.
    • Introduce a short pause between questions in tests for a more comfortable user experience.
    • Upon login, users land on the Nav page instead of the home page.
    • Resolve the everlasting loop issue in exercises due to potential mismatch in exercise numbers.
    • Proper instructions added to each exercise for clear guidance.
  • Bugs Fixed:

    • Verification on the signup page successfully redirects users to the home page, even if verified on another device.
    • User remains on the Nav page post-login until choosing to log out, preventing redirection to the home page.

Expected Behavior:

  • The home page previously showed "Getting Started" and lacked a direct sign-in option.
  • After implementation, the home page features a prominent sign-in button and a direct access button for testing.
  • Users can test without signing in initially, with prompts to sign in for progress saving.
  • Upon login, users are directed to the Nav page instead of the home page.
  • The Nav page neatly separates test and exercise sections for user convenience.
  • Tests now include brief pauses between questions, improving the testing experience.
  • The fix resolves issues causing endless loops in exercises due to potential exercise count mismatches.
  • Successful verification on the signup page redirects users to the home page, regardless of verification device.
  • Post-login, users remain on the Nav page until opting to log out, preventing home page redirection.
  • Proper instructions are provided for each exercise, ensuring clear guidance for users.

Note: Gpt Touched for better wording :D

@JasonBoyett
Copy link
Owner

can you give me a bit more info about the "everlasting loop issue" you mentioned?

@dhextras
Copy link
Author

can you give me a bit more info about the "everlasting loop issue" you mentioned?

Well i havent checked recently but then i did last time there were only 14 total tests there( in ur code) but u were set it up for 15 weeekly tests and that messes up things and after i finish 14 tests it then just showing me the same test even if i complete forver

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants