Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

footer layout for mobile #461

Merged
merged 3 commits into from
Nov 8, 2024
Merged

Conversation

jainaryan04
Copy link
Contributor

@jainaryan04 jainaryan04 commented Nov 4, 2024

closes #434

@RamakrushnaBiswal
fix footer layout for mobile
image

Summary by CodeRabbit

  • Documentation

    • Updated contributors' section in the README, adding new contributors and modifying existing entries.
  • Style

    • Adjusted layout and styling of the footer component for improved responsiveness across different screen sizes.

Copy link

vercel bot commented Nov 4, 2024

@jainaryan04 is attempting to deploy a commit to the bunty's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Contributor

coderabbitai bot commented Nov 4, 2024

Walkthrough

The changes in this pull request involve updates to the README.md file's contributors' section, adding new contributors and modifying existing entries. Additionally, the Content.jsx file has undergone layout and styling adjustments to improve the footer component's responsiveness, particularly for mobile devices, ensuring better alignment and spacing.

Changes

File Change Summary
README.md Updated contributors' section: added Ashwini_ab, Souvik Kumar Pramanik, Shivam, Hem Raj; modified entries for Mahera Nayan, Tyarla Shirisha, Sourabh Singh Rawat, and Abhinandan.
frontend/src/components/Shared/footer/Content.jsx Modified layout and styling of the footer component for better responsiveness; adjusted padding and margin properties for various screen sizes, particularly in the Nav component and "Contact Us" section.

Assessment against linked issues

Objective Addressed Explanation
Center the footer layout for mobile (#434)
Adjust left and right margins of footer (#434)

Possibly related PRs

Suggested labels

bug, enhancement, level1, gssoc-ext, good first issue

Suggested reviewers

  • RamakrushnaBiswal

Poem

In the meadow where rabbits play,
New friends join us every day.
Contributors gather, names anew,
With every change, our project grew.
Hops and clicks, we work with glee,
Together we build, just you and me! 🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between f2d8f0d and 454169e.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • README.md

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

github-actions bot commented Nov 4, 2024

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
README.md (1)

283-284: Replace hard tabs with spaces for consistent formatting.

Several lines in the table structure use hard tabs instead of spaces. While this doesn't affect the rendered output, it's best to maintain consistent indentation using spaces throughout the markdown file.

-		</tr>
-		<tr>
+    </tr>
+    <tr>

Also applies to: 327-328, 371-372, 591-592, 635-636

🧰 Tools
🪛 Markdownlint

283-283: Column: 1
Hard tabs

(MD010, no-hard-tabs)


284-284: Column: 1
Hard tabs

(MD010, no-hard-tabs)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 7112e3a and f2d8f0d.

📒 Files selected for processing (2)
  • README.md (7 hunks)
  • frontend/src/components/Shared/footer/Content.jsx (3 hunks)
🧰 Additional context used
🪛 Markdownlint
README.md

283-283: Column: 1
Hard tabs

(MD010, no-hard-tabs)


284-284: Column: 1
Hard tabs

(MD010, no-hard-tabs)


327-327: Column: 1
Hard tabs

(MD010, no-hard-tabs)


328-328: Column: 1
Hard tabs

(MD010, no-hard-tabs)


371-371: Column: 1
Hard tabs

(MD010, no-hard-tabs)


372-372: Column: 1
Hard tabs

(MD010, no-hard-tabs)


591-591: Column: 1
Hard tabs

(MD010, no-hard-tabs)


592-592: Column: 1
Hard tabs

(MD010, no-hard-tabs)


635-635: Column: 1
Hard tabs

(MD010, no-hard-tabs)


636-636: Column: 1
Hard tabs

(MD010, no-hard-tabs)

🔇 Additional comments (5)
frontend/src/components/Shared/footer/Content.jsx (3)

9-9: LGTM! Responsive layout improvements

The changes to the main container's layout classes improve the mobile experience by:

  • Properly centering content on mobile with items-center
  • Maintaining left alignment on desktop with md:items-start
  • Using appropriate padding with md:px-12

202-202: LGTM! Improved contact section alignment

The contact section's alignment has been improved with:

  • Centered alignment on mobile with items-center
  • Left alignment on desktop with md:items-start
  • Better spacing with pb-8

170-170: Verify the margin adjustments

The margin changes look good and address the uneven margin issue mentioned in #434. Let's verify the implementation across different screen sizes.

✅ Verification successful

Margin adjustments are correctly implemented

The margin changes in the footer component are consistent and well-structured:

  • The main container uses responsive margins (mx-[40px] md:ml-[30px] md:mr-0) for proper alignment
  • The newsletter section uses mx-auto for centered positioning
  • The Google Translate image margin (mr-[65px]) is currently commented out

The implementation properly addresses the uneven margin issue (#434) while maintaining a consistent responsive layout.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any other margin-related classes that might need similar adjustments

# Search for margin classes that might need responsive variants
rg -g '*.jsx' -g '*.js' 'className="[^"]*m[lrxy]-\['

Length of output: 310


Script:

#!/bin/bash
# Let's check the entire footer component for margin-related classes to ensure consistency
rg -g '*.jsx' -g '*.js' -A 2 -B 2 'className="[^"]*\b(m[lrxy]|margin)[^"]*"' frontend/src/components/Shared/footer/

Length of output: 1489

README.md (2)

276-282: LGTM! New contributor entries are well-structured.

The additions and modifications to the contributors section maintain consistent formatting with existing entries. Each entry properly includes:

  • GitHub avatar
  • Profile link
  • Contributor name

Also applies to: 293-297, 307-311, 314-318, 425-429, 432-436, 577-583, 584-590, 637-642


Line range hint 276-642: Verify contributor profile links.

The changes look good, but it's important to ensure all GitHub profile links are correct and active.

✅ Verification successful

All GitHub profile links are valid and active

All the checked GitHub profiles are accessible and active. Each profile link correctly maps to an existing GitHub user account with recent activity, confirming the validity of the contributors' section.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all new/modified GitHub profile links are valid
# Test: Check HTTP status codes for new/modified profile URLs

echo "Verifying GitHub profile links..."
gh api \
  -H "Accept: application/vnd.github+json" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  /users/Ashwinib26 /users/itznayan /users/Shirisha-16 /users/Sourabh782 \
  /users/AE-Hertz /users/Navneetdadhich /users/souvikpramanikgit /users/myselfshivams \
  /users/Hemraj-7

Length of output: 364


Script:

#!/bin/bash
# Check GitHub profiles one by one
echo "Checking GitHub profiles..."

for user in Ashwinib26 itznayan Shirisha-16 Sourabh782 AE-Hertz Navneetdadhich souvikpramanikgit myselfshivams Hemraj-7; do
    echo "Checking $user..."
    gh api -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" "/users/$user"
done

Length of output: 14112

🧰 Tools
🪛 Markdownlint

283-283: Column: 1
Hard tabs

(MD010, no-hard-tabs)


284-284: Column: 1
Hard tabs

(MD010, no-hard-tabs)

@RamakrushnaBiswal
Copy link
Owner

@jainaryan04 resolve the conflicts

@jainaryan04
Copy link
Contributor Author

done @RamakrushnaBiswal

@jainaryan04
Copy link
Contributor Author

@RamakrushnaBiswal pls merge

@RamakrushnaBiswal RamakrushnaBiswal merged commit 13955cc into RamakrushnaBiswal:main Nov 8, 2024
3 of 4 checks passed
@RamakrushnaBiswal RamakrushnaBiswal added level1 for 10 points gssoc-ext gssoc-extd program hacktoberfest accepted hacktoberfest-accepted repo labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gssoc-ext gssoc-extd program hacktoberfest accepted hacktoberfest-accepted repo level1 for 10 points
Projects
None yet
Development

Successfully merging this pull request may close these issues.

footer layout for mobile
2 participants