feat: Add reading time to blog listing cards (#1766)

[ida-jemi]

Description

Fixes # 1766

Type of Change

• New feature (e.g., new page, component, or functionality)
• Bug fix (non-breaking change that fixes an issue)
• UI/UX improvement (design, layout, or styling updates)
• Performance optimization (e.g., code splitting, caching)
• Documentation update (README, contribution guidelines, etc.)
• Other (please specify):

Changes Made

• Added Reading Time field to all blog entries in src/database/blogs/index.tsx, calculated from the actual MDX source files using the same words / 200 formula that Docusaurus uses internally
• Fixed src/pages/blogs/index.tsx - BlogCard was using usePluginData("blog-reading-time-plugin") which doesn't exist, causing it to always fall back to 1 min read. Now reads from blog.readingTime directly
• Fixed src/components/blogCarousel/blogCard.tsx - removed the usePluginData lookup and replaced with readingTime ?? 1
• Fixed src/components/blogCarousel/blogCarousel.tsx - was passing read time calculated from the short description excerpt instead of the stored value
• Fixed src/components/BlogSearch/index.tsx - replaced hardcoded 5 min read with actual readingTime from the blog database

Dependencies

• No new dependencies added.

Checklist

• My code follows the style guidelines of this project.
• I have tested my changes across major browsers and devices
• My changes do not generate new console warnings or errors .
• I ran npm run build and attached screenshot(s) in this PR.
• This is already assigned Issue to me, not an unassigned issue.

** npm run build crashes locally due to a GLib/Windows environment issue unrelated to these changes. Verified all changes work correctly via npm start - blog cards on /blogs page, carousel, and search all display correct read times.

[vercel]

@ida-jemi is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

1. Get free Consultation use code recode50 to get free: Mentorship for free.

2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[github-actions]

✅ Synchronized metadata from Issue #1766:

• Labels: enhancement, level 1, recode, Enhacement, gssoc:approved
• Milestone: None

[Karanjot786]

Hey @ida-jemi! Saw your work on GSSoC 2026.

We are building TermUI, a TypeScript terminal UI framework with React-style hooks and JSX, rendered entirely in the terminal.

We have 67 unassigned GSSoC issues open, including new widgets, animations, and CLI tooling. Your JavaScript background transfers directly.

• Open issues (GSSoC 2026)
• TermUI on GSSoC

Karanjot, TermUI maintainer