feat: Integrate AuroraBackground and GlowingEffect components across … - #37
feat: Integrate AuroraBackground and GlowingEffect components across …#37wiatrM wants to merge 1 commit into
Conversation
…various pages - Added AuroraBackground component to enhance visual aesthetics on multiple service pages. - Implemented GlowingEffect component in contact forms and service sections for improved interactivity. - Updated package dependencies, including framer-motion and added motion package for animations. - Introduced tailwind.config.js for custom styling and animations. - Enhanced overall UI consistency and user experience across the application.
There was a problem hiding this comment.
Pull Request Overview
This PR introduces two new UI components—AuroraBackground and GlowingEffect—and integrates them across a range of pages and sections to enhance visual aesthetics and interactivity.
- Wrapped key service and content pages with AuroraBackground for animated gradient backdrops.
- Applied GlowingEffect overlays on cards, forms, and demos for interactive glow animations.
- Updated animation dependencies (framer-motion → v11.18.2, added motion package).
Reviewed Changes
Copilot reviewed 22 out of 24 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| package.json | Bumped framer-motion version and added motion. |
| components/ui/glowing-effect.tsx | Added new GlowingEffect component implementation. |
| components/ui/aurora-background.tsx | Added new AuroraBackground component implementation. |
| onClick={handleProjectClick} | ||
| > | ||
| <GlowingEffect glow={true} disabled={false} borderWidth={1} /> | ||
| <GlowingEffect glow={true} disabled={false} borderWidth={1} /> |
There was a problem hiding this comment.
Duplicate GlowingEffect components detected; one instance should be removed to avoid redundant rendering and performance overhead.
| <GlowingEffect glow={true} disabled={false} borderWidth={1} /> |
| ...props | ||
| }: AuroraBackgroundProps) => { | ||
| return ( | ||
| <main> |
There was a problem hiding this comment.
Using a
element inside AuroraBackground may lead to multiple tags per page, which is semantically incorrect. Consider replacing it with a| <main> | |
| <div> |
| const handleScroll = () => handleMove(); | ||
| const handlePointerMove = (e: PointerEvent) => handleMove(e); | ||
|
|
||
| window.addEventListener("scroll", handleScroll, { passive: true }); |
There was a problem hiding this comment.
Each GlowingEffect instance adds its own global scroll and pointermove listeners, which can cause performance issues when many instances are rendered. Consider centralizing these listeners or using a shared context/provider.
There was a problem hiding this comment.
Bug: Duplicate Components Cause DOM Overlap
Two identical GlowingEffect components are rendered on the same Card element with identical props (glow={true} disabled={false} borderWidth={1}). This accidental duplication creates redundant DOM elements and may lead to performance issues or visual artifacts.
components/enhanced-projects-heavy.tsx#L164-L166
cloudfloo.io/components/enhanced-projects-heavy.tsx
Lines 164 to 166 in 88a6d4f
Bug: Framer Motion Version Conflict
Dependency version conflict: package.json lists framer-motion@^11.18.2 and motion@^12.23.0. However, motion@12.23.0 internally depends on framer-motion@^12.23.0, causing two different versions of framer-motion to be installed. This can lead to runtime conflicts and unpredictable behavior.
package.json#L68-L82
Lines 68 to 82 in 88a6d4f
Bug: Semantic HTML Violation: Multiple `` Tags
The AuroraBackground component incorrectly uses a <main> tag as its root, violating HTML semantics by creating multiple <main> elements when used. Furthermore, the AIMachineLearningClient component now redundantly wraps its content with AuroraBackground, even though it's already wrapped by AuroraBackground in its parent page. This leads to nested AuroraBackground components and multiple <main> tags, causing potential rendering and accessibility issues. The AuroraBackground component's root element should be a <div>.
components/ui/aurora-background.tsx#L17-L53
cloudfloo.io/components/ui/aurora-background.tsx
Lines 17 to 53 in 88a6d4f
app/services/ai-ml/client.tsx#L88-L271
cloudfloo.io/app/services/ai-ml/client.tsx
Lines 88 to 271 in 88a6d4f
Bug: GlowingEffect Misplacement Causes Layout Chaos
Eight GlowingEffect components are incorrectly placed as standalone elements between various page sections. These components are designed for absolute positioning within a parent container, not as top-level siblings. This misplacement results in a lack of proper positioning context, causing layout issues, unintended rendering, redundant visual effects, and DOM clutter.
app/page.tsx#L56-L75
Lines 56 to 75 in 88a6d4f
BugBot free trial expires on July 22, 2025
You have used $0.00 of your $5.00 spend limit so far. Manage your spend limit in the Cursor dashboard.
Was this report helpful? Give feedback by reacting with 👍 or 👎
…various pages