Refactor Data Fetching to Use Centralized API Layer with Proper Error Handling & Revalidation

[Shalini828]

Currently, data (events, blog, etc.) is imported directly from local dummy files or handled inconsistently across components. Refactor the project to introduce a centralized API/data layer using server utilities with proper error handling, caching strategy, and revalidation support (Next.js App Router compliant).

What Needs To Be Done:

Create a dedicated /lib/api or /services layer

Move event/blog fetching logic into reusable server functions

Add proper try/catch error handling

Implement revalidate or cache strategies

Handle failed fetch scenarios gracefully

Ensure compatibility with i18n routing

I would like to work on this issue.

Kindly assign this to me under Apertre 3.0.
Thanks !