feat: Settings Page UI with Profile, Security & Notifications tabs #1

Open
tanjdev7614 wants to merge 0 commits from feature/settings-page into main
Owner

Summary

Creates a production-ready Settings page component with three tabs:

Features

  • Profile tab: First/last name, email, username, bio, avatar upload
  • Security tab: Password change form, 2FA toggle, session timeout, login notifications
  • Notifications tab: Channel toggles (email, push, SMS) and type toggles (security alerts, mentions, comments, weekly digest, marketing)
  • Reusable ToggleSwitch component with accessible role="switch" and keyboard support
  • Save button with loading spinner and success confirmation
  • Fully responsive layout (mobile → desktop) using Tailwind CSS
  • TypeScript interfaces for all settings types
  • Clean component architecture with SectionCard abstraction

Tech

  • React/Next.js with use client directive
  • TypeScript with strict typing
  • Tailwind CSS for styling
  • No external UI library dependencies

Task ID: cmo0327r20003oi12h8hu82z8

## Summary Creates a production-ready Settings page component with three tabs: ### Features - **Profile tab**: First/last name, email, username, bio, avatar upload - **Security tab**: Password change form, 2FA toggle, session timeout, login notifications - **Notifications tab**: Channel toggles (email, push, SMS) and type toggles (security alerts, mentions, comments, weekly digest, marketing) - **Reusable ToggleSwitch** component with accessible `role="switch"` and keyboard support - **Save button** with loading spinner and success confirmation - **Fully responsive** layout (mobile → desktop) using Tailwind CSS - **TypeScript** interfaces for all settings types - Clean component architecture with SectionCard abstraction ### Tech - React/Next.js with `use client` directive - TypeScript with strict typing - Tailwind CSS for styling - No external UI library dependencies Task ID: cmo0327r20003oi12h8hu82z8
This branch is already included in the target branch. There is nothing to merge.
You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.
git checkout -b feature/settings-page main
git pull origin feature/settings-page

Step 2:

Merge the changes and update on Gitea.
git checkout main
git merge --no-ff feature/settings-page
git push origin main
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tanjdev7614/test-fixes#1
No description provided.