fix: improve blog typography (Issue #1594)

[bhavya-tyagi20]

Description

Improved blog typography to deliver a cleaner and more readable blog experience aligned with the reference design.

The changes focus on text hierarchy, spacing, and content structure while keeping the scope limited to blog pages only.

Fixes #1594

Type of Change

• New feature
• Bug fix
• UI/UX improvement
• Performance optimization
• Documentation update
• Other (please specify):

---

Changes Made

-Updated blog CSS for improved typography and spacing

• Adjusted font sizes and line-height for better readability
• Refined spacing between sections and text elements
• Improved responsiveness of blog layout
• Added minor UI enhancements to align with design expectations

---

Dependencies

No new dependencies added.

---

Screenshots

---

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 an assigned issue.

[vercel]

Someone 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 #1594:

• Labels: contributor-workshop, good first issue, Enhacement, gssoc:approved, type:docs, type:design, type:refractor
• Milestone: recode:launch 3.0

[Adez017]

Hi @bhavya-tyagi20 did you attached the right screenshots ? i dont think so .
The issue attached clealry states that we are talkin about the blog content pages ,font style and layout and i dont find any chnages there .

CC: @sanjay-kv

[bhavya-tyagi20]

Hi @bhavya-tyagi20 did you attached the right screenshots ? i dont think so . The issue attached clealry states that we are talkin about the blog content pages ,font style and layout and i dont find any chnages there .

CC: @sanjay-kv

Apologies,I understand the concern. I’ll fix the PR scope and update it to include only blog content page typography changes as required. I’ll also attach correct screenshots of blog article pages after applying the changes.

[github-actions]

✅ Synchronized metadata from Issue #1594:

• Labels: contributor-workshop, good first issue, Enhacement, gssoc:approved, type:docs, type:design, type:refractor
• Milestone: recode:launch 3.0

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
recode-website	Ready	Preview, Comment	May 21, 2026 1:20pm

[sanjay-kv]

@bhavya-tyagi20 thats alright.

take your time, and you can make changes in the same PR.

• make sure you pull and push next time :)
  so you have updated version of website on local system :) happy coding

[bhavya-tyagi20]

@bhavya-tyagi20 thats alright.

take your time, and you can make changes in the same PR.

• make sure you pull and push next time :)
  so you have updated version of website on local system :) happy coding

Thanks for the feedback! I’ve pulled the latest changes, updated my branch, and addressed the requested fixes. Please review.