Skip to content

fix: improve Contact Us page heading and input styling#1458

Closed
Xenon010101 wants to merge 1 commit into
Sachinchaurasiya360:mainfrom
Xenon010101:fix/issue-1318-contact-ui
Closed

fix: improve Contact Us page heading and input styling#1458
Xenon010101 wants to merge 1 commit into
Sachinchaurasiya360:mainfrom
Xenon010101:fix/issue-1318-contact-ui

Conversation

@Xenon010101
Copy link
Copy Markdown
Contributor

What

Improve the Contact Us page UI — add animated green underline to the heading and fix input backgrounds to match the glass-morphism design.

Root cause

The "Contact Us" heading lacked the decorative green underline animation seen on other pages (e.g., Terms & Conditions), and input/textarea backgrounds were opaque white/gray-800, breaking the form card's glass-morphism aesthetic.

Changes

  • Added framer-motion import and animated green underline (bg-lime-400) to the "Us" portion of the heading
  • Changed all input/textarea backgrounds from bg-white dark:bg-gray-800 to bg-transparent so they inherit the card's backdrop-blur effect

Verification

  • Visually matches the pattern used in TermsPage.tsx for heading underline
  • Inputs now blend into the form card's glass-morphism style
  • No regressions — all form functionality unchanged

CI failures

N/A

Before

Heading had no underline decoration; inputs had opaque white/dark backgrounds.

After

Heading has a smooth green underline animation on load; inputs are transparent, matching the card's backdrop-blur glass-morphism style.

Closes #1318

Adds green underline animation to heading heading, changes input/textarea backgrounds to bg-transparent to match glass-morphism card style. Closes Sachinchaurasiya360#1318

Signed-off-by: Xenon010101 <xenon010101@users.noreply.github.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 5, 2026

Warning

Review limit reached

@Xenon010101, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 36 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9ee1b684-ed45-4969-8960-ffcd473d068c

📥 Commits

Reviewing files that changed from the base of the PR and between 0c176ae and 16937a4.

📒 Files selected for processing (1)
  • client/src/module/legal/ContactPage.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions Bot added level:beginner Good for first-time contributors quality:exceptional Exceptional implementation quality type:bug Bug fixes type:design UI/UX or design-related updates gssoc:approved Approved for GSSoC scoring scope:frontend Changes to client-side / UI code bug Something isn't working gssoc labels Jun 5, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 5, 2026

Hi @Xenon010101, thanks for contributing to InternHack! 🎉

I have automatically:

  • 👤 Assigned this PR to you.
  • 🏷️ Applied the gssoc:approved label.

Our workflows will now analyze your changes to classify:

  • 📈 PR Difficulty: level:*
  • 🧩 PR Type: type:*
  • 🌟 PR Quality: quality:*

Tip

Ensure your PR description references the issue it resolves (e.g. Closes #123). This allows the bot to inherit any additional labels from that issue!

Happy coding! 🚀

@ARPANPATRA111
Copy link
Copy Markdown
Contributor

@Xenon010101 well deserved 👏

Learn to respect someone's work. stealing issue will eventually result in this only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working gssoc:approved Approved for GSSoC scoring gssoc level:beginner Good for first-time contributors quality:exceptional Exceptional implementation quality scope:frontend Changes to client-side / UI code type:bug Bug fixes type:design UI/UX or design-related updates

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG]: Contact Us page UI design issue

3 participants