Community Activity Dashboard

[gxjansen]

Showing community activity on our homepage:

• Recent / Popular forum posts
• Past / Upcoming events

[netlify]

✅ Deploy Preview for spryker-community ready!

Name	Link
🔨 Latest commit	7465a30
🔍 Latest deploy log	https://app.netlify.com/sites/spryker-community/deploys/674432bbe576220009949941
😎 Deploy Preview	https://deploy-preview-135--spryker-community.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[gxjansen]

I've reimplemented the VanillaForumPosts component using Astro Islands architecture, which provides several key improvements:

1. True Client-Side Hydration:

• The component is now a React component that gets hydrated on the client side using client:load
• This means the forum posts will update dynamically without requiring server-side rendering
• The rest of the page remains static, following the Islands Architecture pattern

2. Better State Management:

• Uses React's useState and useEffect hooks for proper state management
• Handles loading and error states more effectively
• Provides a smoother user experience with loading indicators

3. Component Organization:

• Split into smaller, more maintainable components (DiscussionCard)
• Clear separation of concerns between data fetching and presentation
• TypeScript for better type safety and developer experience

4. Performance Benefits:

• Only this component is hydrated with JavaScript, while the rest of the page remains static
• Data fetching happens on the client side, reducing server load
• Loading states provide better user feedback
• The implementation now follows Astro's Islands Architecture pattern, where this interactive component is isolated while the rest of the page remains static HTML, providing the best balance of interactivity and performance.

[gxjansen]

Todo with VanillaEvents / VanillaForumPosts:

• remove console.logs, leave console.error
• extract individual components: EventCard & DiscussionCard
• no .tsx files, move all to .astro
• put components in subfolder
• rename api/forum folder api/vanilla

review files with double extensions (.json.ts .ico.ts), what is the logic here

[fsmeier]

we should directly filter by upcoming events and by previous events