Improved landing page with text visibility

[Chandrika987]

Summary

Improved the landing page visual hierarchy, readability, and accessibility contrast by enhancing typography visibility, button distinction, spacing, and feature card styling while preserving the existing layout and functionality.

Closes #261

Type of Change

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

Changes Made

• Improved heading and subtitle contrast for better readability
• Refined spacing and typography hierarchy in the hero section
• Added subtle UI polish for a cleaner landing experience

How to Test

Steps for the reviewer to verify this works:

1. Run the project locally using npm run dev
2. Observe the landing page hero section
3. Verify improved visibility of:
   • Application title
   • Description text
   • Secondary CTA button
   • Feature cards
4. Test responsiveness across different screen sizes

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]

@Chandrika987 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!

[Chandrika987]

Hello @Priyanshu-byte-coder ,
The update focuses on improving the initial screen’s readability and accessibility by enhancing text contrast, button visibility, spacing, and overall visual hierarchy while keeping the existing design structure intact.
I also ensured the changes remain responsive and visually consistent across different screen sizes and themes.
Please review it whenever convenient. Thank you!

[Priyanshu-byte-coder]

Please fix before merging:

Hardcoded colors bypassing CSS variable system — replace all of these:

• text-slate-* → text-[var(--muted-foreground)]
• text-white → text-[var(--foreground)]
• bg-white/* → bg-[var(--card-muted)]
• dark:* utility classes → not needed when using CSS vars (vars already handle dark mode)
• Any text-gray-*, bg-gray-*, border-gray-* → use var(--border), var(--muted-foreground)

All colors must use CSS vars defined in globals.css so dark/light theming works automatically.

[Chandrika987]

Hi @Priyanshu-byte-coder,

Thank you for the review and guidance.
I’ve updated the landing page styling to use the existing CSS variable system from globals.css and removed the hardcoded color utilities and unnecessary dark: classes to maintain proper theme consistency across light and dark modes.

The requested changes have now been pushed. Please review whenever convenient.