Adds About and Social API

[kmuralidharan91]

🚀 Add V2 APIs for About and Social Links

Summary

Adds new V2 API endpoints to serve About section and Social media links data, enabling mobile app consumption and maintaining consistency between web and mobile platforms.

Changes

• New APIs:

  • GET /api/v2/about - Returns structured about information
  • GET /api/v2/social - Returns array of social media links with icons and URLs

• Architecture:

  • Follows existing project patterns with GenericResponse<T> wrapper
  • Structured response models (AboutResponse, SocialResponse)
  • Integrated with V2 API routing

• Web Integration:

  • Updated templates to use API data with hardcoded fallbacks
  • Modified HomeContext to include about and social data
  • Ensures backward compatibility

API Responses

// /api/v2/about
{
  "data": {
    "title": "About",
    "description": ["Founded by Adam Rush...", "..."],
    "foundedYear": "2019",
    "founderName": "Adam Rush",
    "founderTwitter": "https://twitter.com/Adam9Rush"
  }
}

// /api/v2/social  
{
  "data": {
    "socialLinks": [
      {
        "id": "twitter",
        "name": "Twitter", 
        "url": "https://twitter.com/swift_leeds",
        "icon": "bx bxl-twitter",
        "displayName": "@Swift_Leeds",
        "order": 1
      }
      // ... 5 more social links
    ]
  }
}

Testing

• ✅ APIs return correct JSON structure
• ✅ Web templates render with API data
• ✅ Fallbacks work when API unavailable
• ✅ Ready for mobile app consumption

Ready for production deployment 🎯

[Sherlouk]

Let's remove all the duplication caused by the optionality, as it's adding a tonne of complexity.

[Sherlouk]

I gave the teams API #159 a free pass because it wasn't decoding JSON, but we absolutely should not be calling our own internal APIs through the service and then parsing JSON responses - it's extremely wasteful on bandwidth, memory, and compute cycles.

I'd recommend pulling the data out into a more accessible location first, and accessing it from the API and HomeRouteController.

[Sherlouk]

We're adding a lot of complexity to the views to handle the fact these are optional. Let's make them required, which will be easier when we address the other PR comment, and then simplify the UI to always use it.

[Sherlouk]

What's the purpose of extracting these values? How can we leverage the new team API to prevent duplicating data?

[Sherlouk]

I don't think this is needed, we can add Spotify. There was no reason for it to be header only aside from I missed it.

[Sherlouk]

Feel free to re-open once changes have been made, and rebased on top of latest main.