fix: restore missing feature cards in Why CommitPulse section

[devansh6107]

Description

Fixes #5372

Restored the missing feature cards in the "Why CommitPulse?" section on the landing page.

• Restored the three feature cards:

  • Real-time Sync
  • Theme Engine
  • Isometric Math

• Restored the corresponding icons for each feature card.

• Moved WallOfLove below the feature cards section.

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

Before: The "Why CommitPulse?" section displayed only the heading, with the feature cards missing.

After: The three feature cards are rendered correctly and the Wall of Love section appears below them.

Checklist before requesting a review:

• I have read the CONTRIBUTING.md file.
• I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
• I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
• My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
• I have updated README.md if I added a new theme or URL parameter.
• I have started the repo.
• I have made sure that i have only one commit to merge in this PR.
• The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
• (Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.

[vercel]

@devansh6107 is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Aamod-Dev]

Thanks for restoring the missing feature cards in the 'Why CommitPulse' section! It looks much better now with the complete set of cards rendering correctly.

Your code is perfect. However, the CI pipeline will currently fail due to an unrelated test divergence in lib/svg/themes.test.ts on the main branch.

To get a green build, simply run git pull --rebase origin main and force push your branch. I'll be ready to merge once that runs!

Labels Applied:

• level:beginner: Simple DOM rendering and component usage.
• type:bug: Restored missing content.
• quality:clean: Flawless syntax.
• mentor:Aamod007

[Aamod-Dev]

Thanks for the contribution. I went through the changes and the overall approach looks good.

[github-actions]

🚨 Hey @devansh6107, the CI Pipeline is failing on this PR and it has been marked as status:blocked.

Please fix the issues before this can be reviewed. Here's how:

1. Run checks locally before pushing:

npm run format:check   # Check Prettier formatting
npm run lint           # Run ESLint
npm run typecheck      # TypeScript type check
npm run test           # Run unit tests (Vitest)
npm run build          # Verify production build passes

2. Auto-fix common issues:

npm run format         # Auto-fix formatting with Prettier
npm run lint -- --fix  # Auto-fix lint errors where possible

3. Check the full failure log here:
👉 View CI Run

Once you push a fix and the CI passes, the status:blocked label will be removed automatically. 💪

[github-actions]

🎉 Congratulations @devansh6107! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨

[Aamod-Dev]

Good catch! I went through the changes and restoring the missing feature cards brings back the essential informational elements of the landing page.
Labels applied:

• level:intermediate: Layout restoration.
• quality:clean: Simple effective DOM fix.
• ype:bug: Fixes missing UI elements.