fix: convert broken markdown tables to HTML in EloqDoc benchmark guide

[isaactony]

Pull Request

Summary

Fixes broken tables in the EloqDoc vs FerretDB vs MongoDB benchmark guide. The markdown tables for "Storage Layout" and "Disk performance" were not rendering correctly in MDX, so they were converted to HTML tables to match other blog posts and ensure proper display.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that causes existing functionality to change)
• Documentation update
• Refactoring/code cleanup
• Content update (blog posts, tools data, etc.)

Changes Made

• Replaced markdown tables with HTML tables in src/app/blog/eloqdoc-vs-ferretdb-vs-mongodb-benchmark-guide/page.mdx
• Updated Storage Layout table (System | Storage)
• Updated Disk performance table (Storage type | IOPS | Throughput)

Testing

• Local development tested
• Build passes (npm run build)
• No TypeScript errors
• No linting errors
• Manual testing completed

Database Changes (if applicable)

• Database migration included
• Migration tested locally
• Rollback plan documented

Content Changes (if applicable)

• Tool data updated in src/lib/toolData.json
• Blog post follows content guidelines
• Images optimized and properly sized
• SEO metadata updated

UI/UX Changes (if applicable)

• Responsive design tested
• Accessibility considerations addressed
• Dark mode compatibility verified
• Loading states implemented

Checklist

• Code follows project style guidelines
• Self-review completed
• Documentation updated if needed
• No new console warnings or errors
• Performance impact considered

Screenshots/Demo

Related Issues

Additional Notes

The project uses HTML tables in other MDX posts (e.g. eloqdoc-vs-mongodb-cloud-services, eloqdoc-vs-mongodb-feature-comparison), so this change aligns with existing patterns and uses the shared table styling from mdx-components.tsx.

Summary by CodeRabbit

• Documentation

  • Updated table markup in the benchmark guide blog post for improved rendering consistency.

• Style

  • Converted table formatting to HTML structure for better display presentation.

[vercel]

@isaactony is attempting to deploy a commit to the Ankur 's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The PR converts two Markdown tables to HTML table structures in a blog post about database benchmarking. The semantic content of both tables—storage layout and disk performance data—remains unchanged; only the markup style is modified from Markdown to HTML syntax.

Changes

Cohort / File(s)	Summary
Blog Post Table Markup Conversion src/app/blog/eloqdoc-vs-ferretdb-vs-mongodb-benchmark-guide/page.mdx	Replaced two Markdown tables with explicit HTML table markup. Storage layout and disk performance tables converted from Markdown to HTML structure while preserving all data and headers.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Feat: New article Eloqdoc vs FerretDB vs MongoDB #166 — Introduces the initial blog page file that this PR modifies for table markup conversion.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: converting broken markdown tables to HTML in the EloqDoc benchmark guide.
Description check	✅ Passed	The description includes all required template sections with substantive content: clear summary, bug fix type selected, specific changes listed, relevant testing completed, screenshots provided, and contextual notes about alignment with project patterns.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Important

Action Needed: IP Allowlist Update

If your organization protects your Git platform with IP whitelisting, please add the new CodeRabbit IP address to your allowlist:

• ✨ 136.113.208.247/32 (new)
• 34.170.211.100/32
• 35.222.179.152/32

Reviews will stop working after February 8, 2026 if the new IP is not added to your allowlist.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
devtoolsacademy	Ready	Preview, Comment	Feb 4, 2026 6:00pm

[tyaga001]

@nirnejak can you check if ok to merge

[nirnejak]

@tyaga001 looks good, we can merge