Add EloqData as new sponsor

[tyaga001]

Summary by CodeRabbit

• New Features

  • Redesigned sponsor section with richer header, responsive grid, improved CTA, and hover interactions.
  • Added a new sponsor to the roster and updated sponsor spacing/layout in documentation.
  • Improved external link security/accessibility for sponsor links.

• Documentation

  • Updated blog content to emphasize balancing AI speed with human context in code reviews.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
devtoolsacademy	Ready	Preview	Comment	Oct 31, 2025 2:12pm

[coderabbitai]

Walkthrough

Inserted two content lines into a blog article emphasizing balancing AI and human reviewers; redesigned the CurrentSponsors component into a multi-section layout with a new EloqData sponsor and security attributes; updated README sponsor row to add EloqData and adjust spacing.

Changes

Cohort / File(s)	Summary
Blog content update src/app/blog/state-of-ai-code-review-tools-2025/page.mdx	Two inline content insertions emphasizing pairing AI speed with human reviewer context; no deletions or logic changes.
Sponsors component redesign src/components/CurrentSponsors.tsx	Replaced minimal sponsor display with header + responsive sponsors grid and CTA; added EloqDataLogo import and EloqData entry; added hover transitions and rel="noopener noreferrer" on external links.
README sponsor row update README.md	Added EloqData sponsor card, adjusted CodeRabbit card width (350px → 300px), inserted spacer cells to preserve horizontal spacing.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Areas to check:
  • src/components/CurrentSponsors.tsx: responsive grid behavior, image imports/paths, link targets and rel attributes, hover and focus states for accessibility.
  • src/app/blog/.../page.mdx: ensure inserted sentences flow and don’t break MDX rendering (line breaks, punctuation).
  • README.md: visual layout consistency in rendered markdown (table/spacer cell alignment).

Possibly related PRs

• Added State of AI Code Review Tools in 2025 blog post #150 — Adds the initial blog page that this PR modifies with additional content emphasis.
• update README structure #142 — Modifies README sponsorship/layout content; related to the README sponsor-row edits.
• enhance: improve README and footer for better visibility #100 — Also updates README sponsor layout and spacing, overlapping changes to sponsor cards.

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request has no description provided, when the repository template requires multiple key sections including Summary, Type of Change, and Changes Made. Given the nature of this PR, the Content Changes section (for the blog post update) and UI/UX Changes section (for the redesigned sponsors component) are particularly relevant but entirely absent. The complete lack of any description means essential context about motivation, testing status, and change categorization is missing, preventing reviewers from understanding the full scope and intent of the work.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "Add EloqData as new sponsor" is clear, concise, and directly relates to the primary objective of the changeset. The title accurately describes the main focus of the changes, which include adding EloqData as a new sponsor in the CurrentSponsors component and README.md. While the changeset includes additional content updates to a blog post about AI code review tools, the title appropriately captures the core purpose of the PR. The title is specific enough that reviewers scanning git history would immediately understand the primary change.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/add-eloqdata-sponsor

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/components/CurrentSponsors.tsx (1)

11-13: Remove the empty Props interface.

The empty Props interface serves no purpose and is flagged by static analysis. Since this component doesn't accept any props, you can simplify the code.

Based on static analysis hints.

Apply this diff to remove the unnecessary interface:

-interface Props {}
-
-const CurrentSponsors: React.FC<Props> = () => {
+const CurrentSponsors: React.FC = () => {

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cca96a8 and f598489.

⛔ Files ignored due to path filters (1)

• src/assets/eloqdata.png is excluded by !**/*.png

📒 Files selected for processing (2)

• src/app/blog/state-of-ai-code-review-tools-2025/page.mdx (2 hunks)
• src/components/CurrentSponsors.tsx (1 hunks)

🧰 Additional context used

🪛 Biome (2.1.2)

src/components/CurrentSponsors.tsx

[error] 10-11: An empty interface is equivalent to {}.

Safe fix: Use a type alias instead.

(lint/suspicious/noEmptyInterface)

🔇 Additional comments (6)

src/app/blog/state-of-ai-code-review-tools-2025/page.mdx (2)

89-89: LGTM!

The added sentence effectively reinforces the article's theme about balancing AI and human code reviewers, and the internal link provides valuable cross-reference to related content.

---

534-534: LGTM!

This content addition appropriately emphasizes the importance of combining AI speed with human contextual understanding in the best practices section. The internal link to the comparison article is well-placed.

src/components/CurrentSponsors.tsx (4)

15-28: LGTM!

The new section header with gradient title and responsive typography enhances the visual presentation and provides clear context for the sponsors section.

---

30-55: LGTM!

The sponsors grid is well-structured with:

• Proper security attributes (rel="noopener noreferrer") on all external links, mitigating potential security risks when opening links in new tabs
• Consistent hover effects and responsive design
• Clean, maintainable structure for all sponsor entries

---

58-69: LGTM!

The enhanced CTA section features smooth transitions, appropriate hover states, and effective use of the next-view-transitions Link component for improved user experience.

---

7-7: Asset file verified and present.

The eloqdata.png file exists at src/assets/eloqdata.png (186K). The import is valid.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

88-96: Minor visual inconsistency: EloqData image height differs from other sponsors.

The EloqData sponsor card uses an image height of 55px (line 90) while CodeRabbit and Stream both use 50px. For visual consistency across the sponsor row, align the height to 50px unless the EloqData logo requires the extra space for legibility.

Apply this diff if standardization is desired:

-        <img src="https://raw.githubusercontent.com/tyaga001/devtoolsacademy/main/src/assets/eloqdata.png" alt="EloqData" height="55" style="margin-bottom: 15px;" />
+        <img src="https://raw.githubusercontent.com/tyaga001/devtoolsacademy/main/src/assets/eloqdata.png" alt="EloqData" height="50" style="margin-bottom: 15px;" />

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f598489 and 5b59d34.

📒 Files selected for processing (1)

• README.md (3 hunks)

🔇 Additional comments (2)

README.md (2)

62-104: Layout and styling look good overall.

The sponsor table layout is well-structured with consistent spacing (30px spacers), uniform card widths (300px), and standardized styling across all three sponsors. Links include appropriate security attributes (rel="noopener noreferrer"), and the visual hierarchy is maintained.

---

88-96: EloqData asset and referral link verified.

Both the image asset (src/assets/eloqdata.png) exists in the repository and the referral URL returns HTTP 200, confirming the link is functional.