Jaishree2310/GlassyUI-Components

BUG: Text Visibility Issue on Stories Page Due to White Background

Open

#539 opened on May 17, 2026

View on GitHub
 (14 comments) (0 reactions) (0 assignees)TypeScript (217 forks)auto 404
good first issuegssoc'26gssoc:approvedlevel:beginnertype:bug

Repository metrics

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

Description

Preliminary Check

  • I have searched the existing issues
  • This issue is reproducible

Bug Summary

The Stories/Experience page has a visibility issue where the background is white/light, but important text elements are also rendered in very light colors. This causes headings and messages to become difficult or impossible to read.

Affected text includes:

  • Main heading: “Real Stories, Real Advice: Share Your Experience”
  • Empty state message: “No posts yet. Share your experience!”

This reduces readability and negatively affects user experience.

Steps to Reproduce

  1. Open the Stories page.
  2. Observe the page background and text colors.
  3. Notice that the heading and informational text blend into the white/light background.
  4. Try viewing under normal brightness/light mode conditions.

Expected Behavior

The Stories page should use the same dark background theme as other pages in the application. Text should remain clearly visible with proper contrast. Theme styling should stay visually consistent throughout the app.

Screenshots/Logs

Additional Information

  • I agree to follow this project's Code of Conduct
  • I'm a GSSOC'24 contributor
  • I want to work on this issue
  • I can provide more details if needed

Contributor guide

Research direction
Locate the Stories page component and verify it uses the same dark background theme as other pages. Ensure text colors have sufficient contrast against the background.
Tech stack
typescript
Domain
frontend
Issue type
Bug
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-3 hours
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75