Skip to content

Conversation

PraneetBose
Copy link

@PraneetBose PraneetBose commented Jul 17, 2025

📝 Description:

Updated the "Why Choose Inpact AI?" section cards and gives a more better visibility to the test and button of the footer section.

🔧 Changes Made

The following changes are been made ;-

  1. A New and fresh design for the two card under " Why Choose Inpact AI? " section
    • It features a new 3D Hover Effect.
    • Added soft coloured Underglow to it to make the design of the website more appealing.
  2. Made Changes in the font effect in the footer section , Now its more visible to the eyes due the addition of white text glow effect.

📷 Screenshots or Visual Changes (if applicable)

image image

✅ Checklist

  • I have read the contributing guidelines.
  • I have added tests that prove my fix is effective or that my feature works.
  • I have added necessary documentation (if applicable).
  • Any dependent changes have been merged and published in downstream modules.

Summary by CodeRabbit

  • New Features

    • Introduced a new TiltedCard component that adds a 3D tilt effect to cards on mouse movement.
  • Enhancements

    • Updated the "Why Choose" section on the homepage to use interactive TiltedCard components with under-glow and blurred shadow effects.
    • Improved footer visuals with enhanced glow, drop-shadow effects, and updated link styling for better visibility.
  • Chores

    • Updated the framer-motion dependency to the latest version.
    • Adjusted TypeScript path alias configuration for improved module resolution.

Copy link
Contributor

coderabbitai bot commented Jul 17, 2025

Walkthrough

A new TiltedCard React component was introduced to provide a 3D tilt effect using framer-motion. The dependency version for framer-motion was updated. The HomePage was refactored to use TiltedCard for specific cards, enhancing their visual effects and footer styling. The TypeScript alias path for @/* was slightly adjusted in the configuration.

Changes

File(s) Change Summary
Frontend/package.json Updated framer-motion dependency version from ^12.5.0 to ^12.23.6.
Frontend/src/components/TiltedCard.tsx Added new TiltedCard component with 3D tilt effect using framer-motion.
Frontend/src/pages/HomePage.tsx Refactored to use TiltedCard for "For Brands" and "For Creators" cards; added visual effects and updated footer styling.
Frontend/tsconfig.json Changed @/* alias path from "./src/*" to "src/*".

Sequence Diagram(s)

sequenceDiagram
  participant User
  participant TiltedCard
  participant framer-motion

  User->>TiltedCard: Mouse moves over card
  TiltedCard->>framer-motion: Update motion values (x, y)
  framer-motion-->>TiltedCard: Provide animated rotation (rotateX, rotateY)
  TiltedCard-->>User: Render tilted card with smooth 3D effect
  User->>TiltedCard: Mouse leaves card
  TiltedCard->>framer-motion: Reset rotation to zero
Loading

Poem

A tilt and a twirl, a card in the breeze,
With framer's new motion, it moves with such ease.
The HomePage now sparkles, the footer aglow,
While rabbits hop by, admiring the show!
With paths now aligned, our code’s hopping fine—
Onward we tilt, to the future we shine!
🐇✨

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@PraneetBose PraneetBose marked this pull request as draft July 17, 2025 10:25
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: 2

🧹 Nitpick comments (2)
Frontend/src/components/TiltedCard.tsx (1)

1-57: Well-implemented 3D tilt component with smooth animations.

The TiltedCard component is well-structured with proper TypeScript typing and clean framer-motion integration. The math for mouse position normalization is correct, and the spring animations provide smooth user interaction.

Consider these minor enhancements:

+// Add accessibility support
+import { ReactNode, useRef, useCallback } from "react";

 const TiltedCard = ({ children, className = "" }: TiltedCardProps) => {
+    // Memoize handlers for better performance
+    const handleMouseMove = useCallback((e: React.MouseEvent) => {
         const rect = ref.current?.getBoundingClientRect();
         if (!rect) return;
         // ... rest of the logic
-    };
+    }, [x, y]);

+    const handleMouseLeave = useCallback(() => {
         x.set(0);
         y.set(0);
-    };
+    }, [x, y]);

     return (
         <motion.div
             ref={ref}
             onMouseMove={handleMouseMove}
             onMouseLeave={handleMouseLeave}
+            role="presentation"
+            aria-hidden="true"
             // ... rest of props
Frontend/src/pages/HomePage.tsx (1)

441-441: Remove duplicate comment block.

The closing comment is redundant and should be removed for cleaner code.

-{/* Edited the cards for "why choose inpact ai? " */}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between a3be437 and 6adfa5f.

⛔ Files ignored due to path filters (1)
  • Frontend/package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (4)
  • Frontend/package.json (1 hunks)
  • Frontend/src/components/TiltedCard.tsx (1 hunks)
  • Frontend/src/pages/HomePage.tsx (3 hunks)
  • Frontend/tsconfig.json (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: Saahi30
PR: AOSSIE-Org/InPactAI#98
File: Frontend/src/pages/CollaborationDetails.tsx:234-234
Timestamp: 2025-07-14T11:45:01.864Z
Learning: In frontend-only PRs, hardcoded URLs (like dummy PDF URLs for contracts) and mock data are acceptable and intentional placeholders for UI development, to be replaced during backend integration phase.
🪛 Biome (1.9.4)
Frontend/src/pages/HomePage.tsx

[error] 337-338: This block statement doesn't serve any purpose and can be safely removed.

Standalone block statements without any block-level declarations are redundant in JavaScript and can be removed to simplify the code.

(lint/complexity/noUselessLoneBlockStatements)


[error] 338-339: This block statement doesn't serve any purpose and can be safely removed.

Standalone block statements without any block-level declarations are redundant in JavaScript and can be removed to simplify the code.

(lint/complexity/noUselessLoneBlockStatements)

🔇 Additional comments (4)
Frontend/tsconfig.json (1)

10-10: LGTM: Path mapping configuration updated correctly.

The change from "./src/*" to "src/*" is a standard TypeScript configuration adjustment that aligns with modern module resolution practices and supports the new component imports.

Frontend/package.json (1)

33-33: Framer-Motion v12.23.6: Version & Security Verified

  • npm confirms framer-motion@12.23.6 exists and is the current stable release.
  • npm audit reports zero moderate-or-higher vulnerabilities after generating a lockfile.
  • This bump (12.5.0 → 12.23.6) is a semver-compatible minor update within major version 12, so there should be no breaking changes.

No further action required.

Frontend/src/pages/HomePage.tsx (2)

2-2: Import statement correctly added for TiltedCard component.

The import path and statement are properly structured for the new component.


964-1000: Footer styling enhancements look good.

The addition of glow effects using drop-shadow CSS provides better visibility and visual appeal. The implementation is clean and maintains consistency across all footer elements.

@PraneetBose PraneetBose marked this pull request as ready for review July 17, 2025 10:38
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

♻️ Duplicate comments (2)
Frontend/src/pages/HomePage.tsx (2)

337-338: Remove useless block statements.

These standalone block statements serve no purpose and should be removed as previously identified.


352-435: Fix TiltedCard props mismatch.

The props passed to TiltedCard don't match the component's interface as previously identified. Remove the invalid props from both TiltedCard instances.

🧹 Nitpick comments (1)
Frontend/src/pages/HomePage.tsx (1)

964-964: Clean up comment formatting.

The comment has formatting and grammar issues that should be cleaned up for better readability.

-        {/* Changed the footer all text with glow elements , for proper visibility------- By Praneet " */}
+        {/* Added glow effects to footer text for improved visibility - by Praneet */}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6adfa5f and 725ce78.

📒 Files selected for processing (1)
  • Frontend/src/pages/HomePage.tsx (3 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: Saahi30
PR: AOSSIE-Org/InPactAI#98
File: Frontend/src/pages/CollaborationDetails.tsx:234-234
Timestamp: 2025-07-14T11:45:01.864Z
Learning: In frontend-only PRs, hardcoded URLs (like dummy PDF URLs for contracts) and mock data are acceptable and intentional placeholders for UI development, to be replaced during backend integration phase.
🪛 Biome (1.9.4)
Frontend/src/pages/HomePage.tsx

[error] 337-338: This block statement doesn't serve any purpose and can be safely removed.

Standalone block statements without any block-level declarations are redundant in JavaScript and can be removed to simplify the code.

(lint/complexity/noUselessLoneBlockStatements)


[error] 338-339: This block statement doesn't serve any purpose and can be safely removed.

Standalone block statements without any block-level declarations are redundant in JavaScript and can be removed to simplify the code.

(lint/complexity/noUselessLoneBlockStatements)

🔇 Additional comments (2)
Frontend/src/pages/HomePage.tsx (2)

2-2: Import statement looks good.

The TiltedCard import is correctly structured and follows standard conventions.


976-997: Footer styling enhancements look good.

The glow effects using drop-shadow utilities are properly implemented and should improve text visibility on the dark footer background. The color changes from gray to white with purple hover effects are appropriate for the design.

@PraneetBose PraneetBose changed the title FIX : added a new Card design and changed text elements in footer FIX : Added a new Card design and changed text elements in footer Jul 17, 2025
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.

1 participant