LF Events API: Add missing fields needed for the AAIF website events integration

[pariola-anyday]

Context

We recently merged the events integration on the AAIF website (staging). It
consumes the LF Events API and renders an events listing with map pins, country
flags, and event cards.

During the build we found several fields that our previous Sanity-backed model
had but the API doesn't return. We've worked around what we could, but a few
gaps are filled with curated/hardcoded data that won't scale as the event list
grows. This issue requests adding those fields upstream so we can drop the
workarounds.

Current API response (for reference)

{
  "id": 278373,
  "name": "Open Source Summit North America",
  "start_date": "2026/05/18",
  "end_date": "2026/05/20",
  "location": {
    "city": "Minneapolis",
    "country": "United States",
    "virtual": false
  },
  "url": "https://pr-1108-lfeventsci.pantheonsite.io/open-source-summit-north-america/",
  "menu_background_color": "#325560",
  "menu_gradient_color": "#003942",
  "menu_dropdown_color": "#003942"
}

Requested additions (priority order)

1. Latitude / longitude — highest priority

• Needed for: map pins on the events map.
• Current workaround: a hand-curated CITY_GEO lookup table keyed by city
  name. Not sustainable — every new event in a new city requires a manual
  code change, and city-name collisions/spelling are fragile.
• Ask: add location.lat and location.lng (or a coordinates object).
  Even city-centroid precision is fine; we only need it for the pin.

"location": {
  "city": "Minneapolis",
  "country": "United States",
  "virtual": false,
  "lat": 44.98,
  "lng": -93.27
}

2. Event image

• Needed for: event cards and the listing hero.
• Current state: API returns only theme colors (menu_background_color,
  etc.); we fall back to a generic placeholder image for every event.
• Ask: add an image (or banner / thumbnail) URL field.

3. Summary / description

• Needed for: card copy and previews.
• Current state: absent — cards have no descriptive text.
• Ask: add a short summary (and/or description) field.

4. Venue name & address

• Needed for: event detail / location display beyond city + country.
• Current state: absent.
• Ask: add location.venue_name and location.address.

5. Time-of-day on dates

• Needed for: showing start/end times, not just dates.
• Current state: start_date / end_date are date-only (YYYY/MM/DD).
• Ask: include start/end times (ideally full ISO-8601 datetimes with
  timezone), e.g. start_at: "2026-05-18T09:00:00-05:00".

Gaps we've already solved on our side (no API change needed)

These are listed only so the scope is clear — please don't prioritize them:

• ISO 3166-1 country code (for flags): solved with a complete curated
  COUNTRY_CODE_BY_NAME map. Sustainable, no API change required — though if a
  country_code field is ever added, we'd happily drop our map.
• Categories: we repurposed this into a status filter (all / upcoming /
  past) plus an event type filter (virtual vs. in-person, derived from the
  existing location.virtual flag). No API change needed.

Summary of the ask

Field	Needed for	Priority
location.lat / location.lng	Map pins	High
image / banner URL	Event cards & hero	High
summary / description	Card copy	Medium
location.venue_name / address	Location detail	Medium
Start/end time (ISO datetime)	Time display	Medium

[cjyabraham]

Thanks for the issue. The problem with many of the fields you're asking for is that they don't actually exist on the Events site in a structured way. The editorial team there may add them to page copy at various points but not in a way that can easily be extracted and exported. To be more precise, here are the fields your requested:

• lat/lng: We currently don't have this data anywhere on the site. Maybe this is something you'll need to generate for now if you need it.
• image/banner url: which image are you wanting here? The event logo or the background image of an event? or both?
• summary/description: these doesn't exist
• location venue/address: this may appear on some event pages in the copy but not in a consistent way that can be exported
• start/end times: this may appear on some event pages in the copy but not in a consistent way that can be exported

So from all fields, the only one that is easy to export currently is the image. All others would need a change to how we store data for each event.

[pariola-anyday]

Image - both would be ideal if they're cheap to expose, but they map to different needs on our side:

• Background / banner image is the priority. It's what fills the event card thumbnail in our listing, so this one field alone closes the main visual gap.
• Event logo as a secondary field if it's easy - we'd use it as a small mark/avatar on the card and the event detail header.

If only one is feasible right now, the background image is the one we need.

Everything else - understood! We'd update data structure on our end to match yours

• lat/lng - we'll figure it out ourselves then, it's highly required by the event map to pin events to different coordinates on the map.
• summary / description, venue name / address, start / end times - since they aren't stored consistently enough to export, we might have to depreciate them or manage from our end

So the only ask that stays on the API side is the image, ideally background + logo, but the background image alone covers our main need.

Thanks for digging into this!

[cjyabraham]

I see you are using buttons for "Register" "Speak" and "Sponsor". Do you want the metadata we have for each of those? We have the following set for each event:

• CTA Register URL (This CTA button will be displayed until the Event end date.)
• CTA Speak URL (This CTA button will be displayed during the Call For Proposal date range.)
• CFP for Event (boolean)
• CFP start date
• CFP end date
• CTA Sponsor URL (This CTA button will be displayed whenever a url is provided and until the following end date, if one is provided)
• CTA Sponsor end date (Sponsor button is hidden after this date)

We also have fields for a black logo and a white logo for the event. Additionally we have a setting for "Menu Text Color" which determines which version of the logo is used in the menu. Events don't necessarily provide both versions of the logo. I can output all fields if that's useful and you can choose which to use?

And it does look like we have a "description" for each event. So I'll include that.

[pariola-anyday]

Yes please, go ahead and output all the fields. Having the full set means we can wire up the richer CTA logic on our side without another round-trip, even if we don't use every field on day one.

To confirm the ones you listed are all useful to us:

• CTA Register / Speak / Sponsor URLs - plus their associated date ranges (CTA Sponsor end date, the CFP start/end window for Speak). We'd like to mirror your display rules (Register until event end, Speak during the CFP range, Sponsor while a URL is set up to the end date), so the dates matter as much as the URLs.

• CFP for Event (boolean) + CFP start/end date - yes.

• Black logo / white logo + Menu Text Color - yes, include all three. We'll fall back gracefully when only one logo version is
  provided.

• Description - great, please include it.

  Thanks!

[cjyabraham]

Ok, can you inspect this updated PR before I merge it in?