improve landing page UI visibility and accessibility

[Rashi1404]

Description

This PR improves the overall UI/UX and accessibility of the landing page while preserving the existing futuristic design aesthetic.

Changes Made

• Fixed cursor visibility issue by improving cursor contrast and glow visibility.
• Updated navbar branding (DEVTRACK) with darker styling for better readability.
• Improved hero section text contrast and visibility.
• Enhanced button accessibility with better hover and focus states.
• Improved spacing and visual balance across the landing page.
• Added smoother UI interactions and transitions.
• Maintained responsiveness across different screen sizes.

UI Improvements

• Better visual hierarchy
• Improved readability
• Cleaner accessibility support
• More polished landing page experience

Type of Change

UI Improvement

Accessibility Enhancement

Responsive Design Fix

Bug Fix

Screenshots

before

after

Notes

The existing design language and layout structure were preserved while improving visibility, accessibility, and user experience.

[vercel]

@Rashi1404 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

[Priyanshu-byte-coder]

PR includes pnpm-lock.yaml. Project uses npm — committing pnpm lockfiles causes Vercel to switch package managers and fail builds with ERR_PNPM_OUTDATED_LOCKFILE. Remove pnpm-lock.yaml (and pnpm-workspace.yaml if present), run npm install to update package-lock.json, then rebase on main.

[Rashi1404]

@Priyanshu-byte-coder

i have Implemented the requested changes:

• Removed pnpm-lock.yaml
• Updated package-lock.json using npm
• Rebases the branch with latest main

The PR has been updated successfully.

[Rashi1404]

Hi @Priyanshu-byte-coder,
i have Implemented the requested changes. The PR has been updated successfully.

[Rashi1404]

Hi @Priyanshu-byte-coder
I've updated the branch as requested:

• Removed pnpm-lock.yaml
• Updated package-lock.json using npm
• Rebased the branch on the latest main
• Resolved merge conflicts and force-pushed the updated branch

Please re-review when convenient.
Thank you!

[Priyanshu-byte-coder]

This PR now has merge conflicts with main due to recent merges. Please rebase onto the latest main branch and resolve all conflicts to proceed with merging.

[Rashi1404]

Hi @Priyanshu-byte-coder
I have updated the branch and rebased onto the latest main.

Changes made:

• Removed pnpm-lock.yaml
• Updated package-lock.json
• Resolved merge conflicts with the latest main branch
• Force-pushed the updated branch

Please re-check the PR.
Thank you!

[Priyanshu-byte-coder]

This PR has merge conflicts with main. Please rebase your branch against the latest main and force-push to resolve. Run: git fetch upstream && git rebase upstream/main

[Rashi1404]

Hi @Priyanshu-byte-coder ,

I've synced this PR with the latest upstream changes, resolved the reported conflicts, and updated the branch. The changes are ready for review.

Whenever possible, I'd appreciate a review and any feedback.
Thank you!

[Rashi1404]

Rebased the branch onto the latest main and resolved merge conflicts. The PR Labeler workflow appears to be failing due to repository permission/configuration (Resource not accessible by integration), which seems unrelated to the changes in this PR.

[Priyanshu-byte-coder]

This PR has developed merge conflicts after recent merges to main. Please rebase onto the latest main branch, resolve all conflicts, and force-push. Once the PR is conflict-free it will be reviewed for merging.

[Rashi1404]

Hi @Priyanshu-byte-coder ,

I have rebased my branch with the latest main and resolved all merge conflicts that were appearing in LandingPage.tsx, GoalTracker.tsx, and package-lock.json. I have also force-pushed the updated branch.

This PR has been open for a few days, and because the repository is very active, new commits are causing conflicts to reappear frequently. I have synced the branch with the latest changes again and would appreciate a review when time permits.

Thank you for your time and for maintaining the project.

[Rashi1404]

Hi @Priyanshu-byte-coder
Kindly review this.
Thank you!!

[Priyanshu-byte-coder]

Closing this PR due to the following issues found during review:

1. Package dependency stripping — the diff removes many packages from package.json/package-lock.json (dompurify, idb-keyval, react-markdown, class-variance-authority, @ducanh2912/next-pwa, tailwind-merge, etc.) that are used elsewhere in the codebase. This would break the build.
2. 9,519 additions / 13,930 deletions in package-lock.json — the vast lock file churn makes this PR very risky to merge and nearly impossible to safely review.
3. PR is behind main — the branch has diverged significantly.

The landing page UI improvements (CustomCursor.tsx, LandingPage.tsx, globals.css) look good in principle. Please open a fresh, focused PR that only includes those 3 files, rebased onto current main, without touching package.json or package-lock.json.

[Karanjot786]

Hey @Rashi1404! Saw your work on GSSoC 2026.

We are building TermUI, a TypeScript terminal UI framework with React-style hooks and JSX, rendered entirely in the terminal.

We have 74 unassigned GSSoC issues open, including new widgets, hooks, and CLI tooling. Your TypeScript background transfers directly.

• Open issues (GSSoC 2026)
• TermUI on GSSoC

Karanjot, TermUI maintainer