Skip to content

Refine Community Engagement Section Alignment and Spacing#1786

Closed
srushti-panara wants to merge 11 commits into
recodehive:mainfrom
srushti-panara:feature/community
Closed

Refine Community Engagement Section Alignment and Spacing#1786
srushti-panara wants to merge 11 commits into
recodehive:mainfrom
srushti-panara:feature/community

Conversation

@srushti-panara
Copy link
Copy Markdown
Contributor

Description

This PR refines the Community Engagement section by improving alignment, spacing, hover interactions, and overall visual consistency. The changes enhance readability, improve component positioning, and provide a more polished user experience.

Fixes #1771

Type of Change

  • New feature (e.g., new page, component, or functionality)
  • Bug fix (non-breaking change that fixes an issue)
  • UI/UX improvement (design, layout, or styling updates)
  • Performance optimization (e.g., code splitting, caching)
  • Documentation update (README, contribution guidelines, etc.)
  • Other (please specify):

Changes Made

  • Improved alignment of Community Engagement section elements.
  • Refined spacing between cards, badges, and content blocks.
  • Enhanced visual hierarchy and layout consistency.
  • Improved hover effects and card interactions.
  • Refined button styling and interaction feedback.
  • Enhanced dark mode appearance and transitions.
  • Improved overall responsiveness and user experience.

Dependencies

  • No new dependencies added.
  • No package versions were updated.
  • No additional configuration changes required.

Checklist

  • My code follows the style guidelines of this project.
  • I have tested my changes across major browsers and devices
  • My changes do not generate new console warnings or errors .
  • I ran npm run build and attached screenshot(s) in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

Before Screenshot

622E0EA4-9358-4902-B135-02DF95E2097D_1_105_c

After Screenshot

Screenshot 2026-05-30 at 1 21 38 AM

Before Screenshot

A063B7EE-9816-4F2A-A807-903AB8F863CA_1_105_c

After Screenshot

Screenshot 2026-05-30 at 1 30 46 AM

Screenshot 2026-05-30 at 1 31 30 AM

Screenshot 2026-05-30 at 1 31 55 AM

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 29, 2026

@srushti-panara is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@github-actions github-actions Bot added in-review The current changes are in review and would need approval and testing before merging level 1 10 points recode this is label for leaderboard labels May 29, 2026
@github-actions github-actions Bot added this to the recode:launch 3.0 milestone May 29, 2026
@github-actions github-actions Bot added Enhacement gssoc26 label gssoc:approved gssoc label high priority gssoc26 label level2 gssoc26 label medium gssoc26 label labels May 29, 2026
@github-actions
Copy link
Copy Markdown

✅ Synchronized metadata from Issue #1771:

  • Labels: level 1, recode, Enhacement, high priority, level2, medium, gssoc:approved
  • Milestone: recode:launch 3.0

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 30, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
recode-website Ready Ready Preview, Comment May 30, 2026 1:41am

@@ -1,4 +1,4 @@
import React, { useState, useEffect } from "react";
import React, { useEffect, useState } from "react";
import Layout from "@theme/Layout";
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@srushti-panara

Hi not trying to discourage, the way you contributed is amazing, especially feature upgrade push on different commits.

Image this shows you have spent some time on this pr.

but the expected behaviour didnt match.
This is completly revamp of the page and reduced readability, + vibe coded feel to it.

So in future any UI change, lets dicusss more changes in the same issue along with development.
because once it go production many people will use it so as a product perspective its not good.

Image

https://recode-website-h8imx1wn7-recode-9c2fd7df.vercel.app/community

so here is what you can do i will be rejecting this PR. but you can raise new pr with change reademe.md by doing a
and i will merge and give same level 3 and merge it for your effort

cc: @Adez017

dont get discouraged, this is part of opensource journey

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the detailed feedback and encouragement. I really appreciate you taking the time to review my work and explain the concerns from a product perspective.

This was a valuable learning experience for me, especially understanding the difference between refining an existing UI and unintentionally redesigning it. I'll definitely discuss larger UI changes more thoroughly before implementation in the future.

Regarding the README contribution you mentioned, could you please guide me on which section you would like me to improve or update? I'd be happy to work on it and raise a new PR.

Also, for future contributions, if I limit the scope to minor UI refinements such as alignment, spacing, responsiveness, and subtle interaction improvements while preserving the existing design language, would it be appropriate to create a new PR for similar UI-related issues?

Thank you again for the guidance and support.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@srushti-panara you can change a word in readme or adding a space works

@sanjay-kv sanjay-kv closed this May 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Enhacement gssoc26 label gssoc:approved gssoc label high priority gssoc26 label in-review The current changes are in review and would need approval and testing before merging level 1 10 points level2 gssoc26 label medium gssoc26 label recode this is label for leaderboard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

🐞[Bug]: Refine Community Engagement Section Alignment and Spacing

3 participants