refactor(testimonials): better design, with logos, and add new quote#153
refactor(testimonials): better design, with logos, and add new quote#153oycyc wants to merge 2 commits into
Conversation
✅ Deploy Preview for masterpoint ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Review limit reached
Next review available in: 55 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughTestimonial entries now include company branding metadata, the slider renders configurable logos, and testimonial styling is updated for centered portrait layouts, revised CTAs, Flexslider alignment, and a centered home-section background. ChangesTestimonial branding and layout
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant TestimonialContent
participant TestimonialsSlider
participant Browser
TestimonialContent->>TestimonialsSlider: provide company and logo metadata
TestimonialsSlider->>TestimonialsSlider: compute logo sizing styles
TestimonialsSlider->>Browser: render testimonial logo and CTA
Browser->>Browser: apply centered portrait and home-section styling
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (1)
content/testimonials/travis-mcpeak.md (1)
9-9: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winTrack the
case_studyTODO.The commented-out
# case_study: TODO!means the "Read the case study" CTA won't render for this testimonial. The template handles this gracefully, but the TODO should be tracked so the link is added once the case study page exists.Would you like me to open a new issue to track this, or help generate the case study content?
🤖 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 `@content/testimonials/travis-mcpeak.md` at line 9, Track the missing case study CTA for the Travis McPeak testimonial by creating a follow-up issue for the commented-out case_study field, documenting that the link should be enabled once the case study page exists.
🤖 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.
Nitpick comments:
In `@content/testimonials/travis-mcpeak.md`:
- Line 9: Track the missing case study CTA for the Travis McPeak testimonial by
creating a follow-up issue for the commented-out case_study field, documenting
that the link should be enabled once the case study page exists.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 5b6f4b5f-3092-4680-8b94-9d2ec0dd79a1
⛔ Files ignored due to path filters (4)
static/img/logos/cursor-25d-dark-mode.svgis excluded by!**/*.svgstatic/img/logos/leadership-analytics-group.pngis excluded by!**/*.pngstatic/img/logos/staples.svgis excluded by!**/*.svgstatic/img/testimonials/travis-mcpeak.jpegis excluded by!**/*.jpeg
📒 Files selected for processing (8)
assets/css/custom.scsscontent/testimonials/adam-pallin.mdcontent/testimonials/alec-baker.mdcontent/testimonials/gunter-pfau.mdcontent/testimonials/liam-egan.mdcontent/testimonials/nathan-wade.mdcontent/testimonials/travis-mcpeak.mdlayouts/partials/testimonials-slider.html
1 participant
before:
after:
inspired by google (https://workspace.google.com/products/meet/#customers):
Summary by CodeRabbit
New Features
Improvements