Navigation from Settings to Dashboard

[AaryanSingh31]

Summary

Closes #900

Improved the settings page navigation UX by adding responsive "Back to Dashboard" navigation buttons for both top and bottom sections of the page.

Type of Change

• Bug fix
• New feature
• Documentation update
• Refactor / code cleanup

Changes Made

• Added a responsive "Back to Dashboard" button at the top of the settings page
• Added a secondary navigation button at the bottom for better long-page usability
• Improved mobile responsiveness with a compact circular button on smaller screens
• Added subtle hover and click animations for smoother interaction feedback
• Improved layout alignment and spacing for tablet/mobile devices

How to Test

Steps for the reviewer to verify this works:

1. Run the project locally
2. Navigate to /dashboard/settings
3. Verify the top navigation button redirects to the dashboard
4. Scroll to the bottom and verify the secondary button also redirects correctly
5. Test responsiveness on mobile/tablet widths
6. Verify hover/click animations work properly

Screenshots

Checklist

• Linked issue in summary
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Self-reviewed the diff
• Added/updated tests if applicable

[vercel]

@AaryanSingh31 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[AaryanSingh31]

Hi @Priyanshu-byte-coder 👋
Just a gentle reminder to check workflow and review the PR. Suggest me changes if needed. Thank you!