Problem Statement
Currently, we're using Algolia for both entity list pages (search/ranking/sorting) and entity detail pages. However, for detail pages, we can optimize by fetching data directly from the database via GraphQL instead of hitting Algolia.

Scope
Pages to migrate:

• Project details page
• Chapter details page
• Committee details page
• User details page

List pages will continue using Algolia for search functionality.

Current Implementation

• All entity data is being fetched from Algolia
• Detail pages don't require Algolia's search/ranking features
• Unnecessary Algolia API calls for direct lookups

Proposed Changes

1. Create GraphQL queries for each entity type:

2. Modify detail page components to use GraphQL instead of Algolia:

   • Replace Algolia hooks with GraphQL queries
   • Ensure all necessary data is available via GraphQL
   • Update loading states and error handling

3. Modify the incoming data from the graphql to adapt pages

4. Entity types to update:

   • Projects
   • Chapters
   • Committees
   • Users

Required Chnages

• frontend
• backend
• (tests)

Benefits

• Reduced Algolia API usage
• More direct and efficient data fetching
• Lower latency for detail pages
• Reduced costs (fewer Algolia operations)