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

new footer design #1017

Merged
merged 7 commits into from
Jan 23, 2025
Merged

new footer design #1017

merged 7 commits into from
Jan 23, 2025

Conversation

mdumond
Copy link
Contributor

@mdumond mdumond commented Jan 22, 2025

Summary by CodeRabbit

  • UI/UX Improvements
    • Enhanced footer text prominence by updating link sizes.
    • Simplified footer link presentation by removing icons.
    • Adjusted footer layout and padding for improved design.
    • Updated footer's responsive design for better adaptability across screen sizes.
    • Modified styling approach in the BaseContainer for a more streamlined design using baseClassNames.

Copy link

vercel bot commented Jan 22, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
public ⬜️ Ignored (Inspect) Visit Preview Jan 23, 2025 6:43pm

Copy link

coderabbitai bot commented Jan 22, 2025

📝 Walkthrough

Walkthrough

The pull request modifies the Footer component in footer.tsx, implementing several visual and structural changes. Key updates include adjusting typography sizes for footer links, removing social media icons, updating the BaseContainer component to use a baseClassNames prop instead of backgroundColor, and eliminating a FooterClient component that was previously visible on smaller screens. These modifications contribute to a more streamlined design and layout for the footer.

Changes

File Change Summary
website/src/components/footer/footer.tsx - Removed Icon prop from FooterLink components
- Changed Typography size from "sm" to "xl" for footer links
- Updated BaseContainer with baseClassNames="theme-blue" and reduced top padding from pt-16 to pt-10
- Changed section typography sizes from "lg" to "sm" for "follow-us," "resources," "our-work," and "about-us"
- Removed FooterClient component that was displayed on smaller screens (using md:hidden class)
ui/src/components/containers/base-container.tsx - Removed backgroundColor property from BaseContainerProps
- Added baseClassNames property to BaseContainerProps
website/src/app/[lang]/[region]/(website)/arts/section-2.tsx - Replaced backgroundColor with baseClassNames in BaseContainer component usage

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b38bf17 and 2966c67.

📒 Files selected for processing (1)
  • ui/src/components/containers/base-container.tsx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Prettify
🔇 Additional comments (2)
ui/src/components/containers/base-container.tsx (2)

4-4: LGTM! Type definition is clear and appropriate.

The optional string type for baseClassNames is well-defined and properly named.


10-12: Consider restructuring class application.

The current implementation applies classes to both outer and inner divs, which could lead to styling conflicts. Consider consolidating styles into a single container.

-<div className={baseClassNames}>
-  <div className="mx-auto max-w-6xl px-3 md:px-6">
-    <div className={className} ref={ref} {...props}>
+<div className={twMerge(baseClassNames, "mx-auto max-w-6xl px-3 md:px-6")}>
+  <div className={className} ref={ref} {...props}>

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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

@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

🧹 Nitpick comments (2)
website/src/components/footer/footer.tsx (2)

44-44: Avoid using !important override for background.

The !bg-background override suggests a specificity issue. Consider restructuring the CSS to avoid using !important.


52-74: Consider keeping social media icons for better UX.

Social media icons help with quick visual recognition. Their removal might impact user experience and accessibility.

 <FooterLink
   label="Instagram"
   url="https://www.instagram.com/so_income"
+  Icon={SiInstagram}
   target="_blank"
 />
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b2706b0 and 2eefac1.

📒 Files selected for processing (1)
  • website/src/components/footer/footer.tsx (3 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Test website
  • GitHub Check: Prettify
  • GitHub Check: Security checks (typescript)
🔇 Additional comments (2)
website/src/components/footer/footer.tsx (2)

23-23: Verify typography size change impact across screen sizes.

The typography size increase from "sm" to "xl" is significant. Ensure this doesn't cause layout issues on mobile devices.


48-48: LGTM! Consistent typography updates.

The typography size changes are applied consistently across all section headers, creating a clear visual hierarchy.

Also applies to: 78-78, 92-92, 107-107

@mdumond
Copy link
Contributor Author

mdumond commented Jan 23, 2025

I forgot to add here that I did not manage to get the line height from Figma considering the font-size, because as far as I could tell they were linked together in the code.

@ssandino
Copy link
Member

Looking good. Don't worry about line height, it's not pixel perfect on Figma either. It's even better to start with the default. And only make exception when really needed.

Copy link

@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: 1

🧹 Nitpick comments (2)
ui/src/components/containers/base-container.tsx (1)

5-5: Consider using a union type for baseClassNames.

Switching from a typed backgroundColor to string reduces type safety. Consider using a union type to maintain type checking.

-baseClassNames?: string;
+type ThemeClass = 'theme-blue' | 'bg-yellow-50';
+baseClassNames?: ThemeClass;
website/src/app/[lang]/[region]/(website)/arts/section-2.tsx (1)

15-15: Use theme classes consistently.

Using hardcoded bg-yellow-50 contradicts the new theming approach. Consider using a theme class for consistency.

-<BaseContainer baseClassNames="bg-yellow-50" className="flex flex-col space-y-1 py-16 md:px-20">
+<BaseContainer baseClassNames="theme-yellow" className="flex flex-col space-y-1 py-16 md:px-20">
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d2259bb and b38bf17.

📒 Files selected for processing (3)
  • ui/src/components/containers/base-container.tsx (1 hunks)
  • website/src/app/[lang]/[region]/(website)/arts/section-2.tsx (1 hunks)
  • website/src/components/footer/footer.tsx (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • website/src/components/footer/footer.tsx
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Test website

Comment on lines 11 to 13
<div className={baseClassNames}>
<div className="mx-auto max-w-6xl px-3 md:px-6">
<div className={twMerge(backgroundColor, className)} ref={ref} {...props}>
<div className={twMerge(baseClassNames, className)} ref={ref} {...props}>
Copy link

Choose a reason for hiding this comment

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

🛠️ Refactor suggestion

Prevent duplicate class application.

baseClassNames is applied to both outer and inner divs, which could cause styling conflicts.

-<div className={baseClassNames}>
+<div className={baseClassNames}>
   <div className="mx-auto max-w-6xl px-3 md:px-6">
-    <div className={twMerge(baseClassNames, className)} ref={ref} {...props}>
+    <div className={twMerge(className)} ref={ref} {...props}>
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<div className={baseClassNames}>
<div className="mx-auto max-w-6xl px-3 md:px-6">
<div className={twMerge(backgroundColor, className)} ref={ref} {...props}>
<div className={twMerge(baseClassNames, className)} ref={ref} {...props}>
<div className={baseClassNames}>
<div className="mx-auto max-w-6xl px-3 md:px-6">
<div className={twMerge(className)} ref={ref} {...props}>

Copy link
Contributor

@mkue mkue left a comment

Choose a reason for hiding this comment

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

nice! thank you :)

I added a little change that you can directly set the theme on the base class container. I don't think we need the restriction to just allow setting the background color.

@mkue mkue merged commit a9fe18c into main Jan 23, 2025
16 checks passed
@mkue mkue deleted the footer branch January 23, 2025 18:47
@mdumond
Copy link
Contributor Author

mdumond commented Jan 24, 2025

oh nice thanks! I was a bit unhappy with the background overrides

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants