Jaishree2310/GlassyUI-Components

UI/UX : UI inconsistency across Sponsor, About Us & Stories pages

Open

#460 opened on May 10, 2026

View on GitHub
 (7 comments) (0 reactions) (1 assignee)TypeScript (217 forks)auto 404
good first issuegssoc'26

Repository metrics

Stars
 (114 stars)
PR merge metrics
 (PR metrics pending)

Description

Problem

The Sponsor, About Us, and Stories pages currently use noticeably different UI styles, making the overall experience feel inconsistent.

Observation

  • Each page has a different layout, spacing, and visual structure
  • Glassmorphism effects are not consistently applied across pages
  • Some sections feel visually disconnected from the main design system

Proposed Solution

Refactor the UI of these pages to follow a more consistent design while preserving their individual functionality.

Implementation:

  1. Standardize spacing, typography, and container styling
  2. Align glassmorphism effects and theme usage across pages
  3. Improve visual consistency for forms, cards, and content sections
  4. Ensure responsive behavior remains intact

Expected Outcome

  1. More consistent and polished UI/UX
  2. Better visual alignment with the overall project theme
  3. Improved user experience across all pages
  4. Cleaner and more maintainable frontend structure

I'd like to work on this issue. Please assign it to me.

Contributor guide

Research direction
Examine the current UI of Sponsor, About Us, and Stories pages. Identify inconsistencies in layout, spacing, typography, and glassmorphism effects. Refactor to align with the project's design system, standardizing styles while preserving functionality.
Tech stack
typescript
Domain
frontend
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactCSS
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70