fix(landing): improve feature preview section clarity

[Medhachalla]

Summary

Improves the landing page feature preview section to better communicate that these cards are feature listings rather than interactive functionality. The changes reduce misleading interaction cues and provide clearer context for unauthenticated users.

Closes #926

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 changes existing behavior)
• 📝 Documentation update
• ♻️ Refactor / code cleanup (no functional change)
• ⚡ Performance improvement
• 🔒 Security fix
• 🧪 Tests only

---

What Changed

• Updated the landing page feature preview section in src/components/landing/LandingPage.tsx to clarify that the displayed cards are previews and that full functionality is available after signing in
• Revised the feature section heading and descriptive text beneath it to better set expectations for unauthenticated users
• Removed visual interaction cues from the feature preview cards that could make them appear clickable or fully functional
• Adjusted feature preview card styling in the landing page components to better distinguish feature listings from actual application features

---

How to Test

1. Start the application locally
2. Navigate to the landing page while logged out
3. Scroll to the Feature Preview section

Expected result:

• Feature cards appear as informational previews rather than interactive components
• The section clearly communicates that features become available after signing in
• Cards no longer feel clickable or misleading to first time visitors

---

Screenshots / Recordings

Screenshots

Before	After

Recordings

Before (recording)

before.webm

After (recording)

after.webm

---

Checklist

• Linked the related issue above
• Self-reviewed my own diff
• No unnecessary console.log, debug code, or commented-out blocks
• npm run lint passes locally
• No TypeScript errors (npm run type-check)
• Added or updated tests where applicable
• Updated documentation / comments if behavior changed

---

Accessibility (UI changes only)

• Keyboard navigation works correctly
• Color contrast meets WCAG AA standard
• ARIA labels / roles added where needed
• Tested on mobile / responsive layout

---

Additional Context

This change focuses on setting appropriate user expectations for unauthenticated visitors by presenting the feature cards as listings rather than active functionality.

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[github-actions]

GSSoC Label Checklist 🏷️

@Umbrella-io — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus