feat(docs): implement custom hero animations and visual demo - #46
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
🚧 Files skipped from review as they are similar to previous changes (2)
📝 WalkthroughWalkthroughAdds two CSS animation definitions ( ChangesHomepage Animation & Visual Demo
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🧹 Nitpick comments (1)
website/src/css/custom.css (1)
82-112: ⚡ Quick winAdd a reduced-motion fallback for the new entrance/float animations.
The new default animations (including infinite float) should be disabled when users request reduced motion.
Suggested fix
+@media (prefers-reduced-motion: reduce) { + .animate-fade-in-up, + .animate-float { + animation: none !important; + opacity: 1; + transform: none; + } +}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@website/src/css/custom.css` around lines 82 - 112, The animations defined in the animate-fade-in-up, delay-1 through delay-4, and animate-float classes do not account for users who have enabled the prefers-reduced-motion accessibility preference. Add a media query using `@media` (prefers-reduced-motion: reduce) that disables all animations for users with this preference by setting animation to none on the .animate-fade-in-up and .animate-float classes, and removing animation-delay from the delay utility classes when this preference is active.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@website/src/css/custom.css`:
- Around line 71-85: The keyframe definition uses camelCase naming (fadeInUp)
but the configured stylelint rule requires kebab-case format. Rename the
`@keyframes` fadeInUp definition to `@keyframes` fade-in-up, and update the
corresponding animation property reference in the .animate-fade-in-up class to
use fade-in-up instead of fadeInUp to maintain consistency and satisfy the
linting requirement.
In `@website/src/pages/index.tsx`:
- Around line 108-113: The onMouseOut event handler is resetting the box-shadow
to an incomplete value that does not match the original base style box-shadow
defined earlier in the element's style object. Update the box-shadow assignment
in the onMouseOut handler to use the exact same two-layer shadow value that was
set in the base style (which includes both the main shadow and the secondary
shadow layer), so that cards properly return to their original visual appearance
when the mouse leaves.
- Around line 44-55: Replace the onMouseOver and onMouseOut event handlers with
onMouseEnter and onMouseLeave on the Link components to prevent event bubbling
issues. Additionally, add onFocus and onBlur handlers to both the "Get Started"
and GitHub Link elements that apply the same style transformations (transform
and boxShadow changes) to ensure keyboard users receive the same visual feedback
when tabbing through buttons and interactive elements.
---
Nitpick comments:
In `@website/src/css/custom.css`:
- Around line 82-112: The animations defined in the animate-fade-in-up, delay-1
through delay-4, and animate-float classes do not account for users who have
enabled the prefers-reduced-motion accessibility preference. Add a media query
using `@media` (prefers-reduced-motion: reduce) that disables all animations for
users with this preference by setting animation to none on the
.animate-fade-in-up and .animate-float classes, and removing animation-delay
from the delay utility classes when this preference is active.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 831f337b-66e1-4f78-8716-19458a74561c
⛔ Files ignored due to path filters (1)
website/static/img/claritty-clarctl-1.pngis excluded by!**/*.png
📒 Files selected for processing (2)
website/src/css/custom.csswebsite/src/pages/index.tsx
|
📖 Description
Resolves #42.
This PR overhauls the Claritty website's homepage, completely replacing the static hero section with a dynamic, highly-animated, and visually stunning landing page designed to maximize user engagement and "wow" factor.
💡 What Changed
clarctl scanterminal screenshot prominently beneath the hero CTA buttons. The image is housed within a sleek, custom-built Mac-style floating window container.custom.css):fade-in-upkeyframes with staggered animation delays so the headline, subtitle, buttons, and feature cards load sequentially.floatanimation on the Y-axis.translateY) and scale up, emitting a glowing purple box-shadow when hovered over.claritty-clarctl-1.pngfrom the root repository intowebsite/static/img/to ensure it is bundled correctly by Docusaurus.✅ Checklist
cd website && npm run build).Summary by CodeRabbit
New Features
Style
SEO / Page Metadata