Skip to content

About

Track research conference deadlines: calendar, countdowns, ICS export, Slack reminders

Topics

Resources

Stars

17 stars

Watchers

1 watching

Forks

Repository files navigation

LiGHT Events Radar

Discover conferences and events relevant to global health and humanitarian response. Track opportunities, key dates and submission deadlines to identify where LiGHT can contribute, present and engage. Calendar, timezone-aware countdowns, search and filters, ICS export, and a Slack bot that reminds you before you miss one.

conferences.light-laboratory.org

CI Deploy License: MIT Next.js 16

Homepage screenshot

Built by Omar Ziyad Azgaoui at LiGHT Lab, EPFL.

What it does

  • Deadline index. Every tracked venue with a live countdown, in your own timezone. Search by name or keyword, filter by year, type and subject.
  • Calendar. Month, week and list views covering conference dates and submission deadlines alike.
  • ICS export. Export a single venue or the whole calendar into Google Calendar, Apple Calendar or Outlook.
  • Speakers page. Lab members and the talks they are giving.
  • Slack bot. Slash commands, a Home tab, and opt-in DM reminders 30, 7 and 3 days before each deadline.
Calendar view

Slack bot

Slack bot daily digest

Daily digests in a channel, reminders in your DMs, and slash commands to search venues. It installs into any workspace via OAuth. Setup and command reference: SLACK_BOT_README.md.

How it works

There is no database. Conferences are authored as YAML and deployed as static files with the rest of the site; the browser fetches and parses them on page load. The Slack bot pulls the same files from the deployed site through the same parser and caches the result in Upstash Redis. Schema validation (pnpm validate) runs in CI on every PR, so malformed data never reaches either consumer.

Keeping deadlines fresh

Deadlines change all the time and updating them by hand gets old fast. Two monthly GitHub Actions handle it instead. Neither one writes to the site directly: both open a pull request that a human merges.

flowchart TB
    OR[OpenReview API] --> ORS[sync-openreview]
    WEB[venue websites] --> LLMS[sync-llm]
    ORS --> MERGE[merge]
    LLMS --> MERGE
    MERGE --> PR[pull request]
    PR -->|human review| MAIN[main]
    MAIN --> CI[CI checks]
    CI --> SITE[GitHub Pages]
    MAIN --> API[Vercel bot]
Loading

The merge step is deliberately narrow. It writes only what a source states for the factual fields (deadline dates, start, end, date, and place when an entry has none) and never touches curated ones like sub, note or link. A source reports typed deadlines; it never writes a label or an other item, and never removes or retypes one. Each reported deadline updates the entry's item of the same type, else its one abstract-family item (paper_abstract, abstract, poster), and is added only when no item of the same group falls on the same day. A field an entry pins with sync_pin, or a deadline pinned with pin: true, is left alone, and a disagreement (including a source naming another city) is reported in the PR body rather than overwritten. full_name is only filled in when an entry has none or a new edition is drafted, with any trailing year or acronym stripped; an existing one is never rewritten, and a source that names the conference differently is reported instead.

Both syncs also run by hand: --venue "<title>" syncs a single venue and --dry-run writes nothing, e.g. pnpm sync:openreview --dry-run --venue ICLR.

Quickstart

The project uses pnpm.

pnpm install
pnpm dev              # dev server
pnpm validate         # check the YAML data (run after any data edit)
pnpm test             # tests
pnpm build            # production build
pnpm sync:openreview  # pull deadline updates from OpenReview
pnpm sync:llm         # pull health-venue deadlines from their websites
pnpm discover:events  # propose new Swiss events for review

Conference data

All events live in three YAML files under public/data/:

  • conferences.yaml: academic conferences
  • summits.yaml: industry summits
  • workshops.yaml: workshops and smaller events

A fourth file, speakers.yaml, powers the Speakers page. It has its own format and is not checked by pnpm validate.

Schema

- title: ShortName              # e.g. NeurIPS, CVPR
  year: 2025
  id: shortname25               # lowercase title + 2-digit year
  full_name: Full Conference Name
  link: https://conference-website.com
  deadlines:                    # optional, in due order
    - type: paper_abstract
      due: 2025-05-14 20:00     # YYYY-MM-DD HH:MM, in the entry's timezone
    - type: paper
      due: 2025-05-21 20:00
      label: Full paper (main track)  # optional; overrides the type's label
      pin: true                 # optional; the syncs never change this date
  timezone: America/Los_Angeles # IANA timezone
  place: City, Country
  date: May 21-25, 2025
  start: 2025-05-21
  end: 2025-05-25
  paperslink: https://...
  sub: ML                       # subject tag
  note: Additional information  # optional
  type: conference              # conference | summit | workshop

Only title, year, id, type and timezone are required. Missing fields show as "TBA". See the list of IANA timezones.

Each deadline has a type saying what is due:

type label meaning
paper_abstract Paper abstract an abstract registered ahead of a full paper (OpenReview's "Abstract Registration")
paper Full paper a full paper or manuscript
abstract Abstract the abstract is the submission, for oral or poster presentation
poster Poster abstract a call for posters only
late_breaking Late-breaking abstract a late-breaking abstract
proposal Session proposal a workshop, panel, symposium or session proposal
other its label (required) anything else a reader must submit
early_registration Early-bird registration the last day of the reduced rate
registration Registration closes the last day to register at all
presenter_registration Presenter registration the day presenting authors must register by
grant Scholarship or travel grant a scholarship, travel grant or fee waiver application

Two items of one event cannot share both type and label. A page saying "before Oct 15" means a 23:59 deadline on Oct 14: write the last valid day.

Automated updates from OpenReview

Venues hosted on OpenReview (NeurIPS, ICML, ICLR, COLM, AAAI, CVPR, WACV, ECCV, LoG, UAI, MIDL, MLHC, CHIL) are kept fresh by the monthly pnpm sync:openreview Action, which reads deadlines, dates and location from the OpenReview API. Hand edits to deadlines and dates of these venues get overwritten by the next sync PR unless the entry pins them with sync_pin; anything not covered by a sync (summits, workshops, venues in neither config) is hand-maintained in the YAML. To sync another OpenReview venue, add one line to scripts/sync-openreview/venues.json.

Automated updates from venue websites

Most health conferences are not on OpenReview, so a second monthly Action (pnpm sync:llm) fetches each venue's important-dates page and asks an OpenAI model to pull out the deadlines, registration and scholarship dates included. Every deadline has to come with the exact sentence it was found in; the quote is checked against the page, must name what is due, and is shown in the PR body. A venue whose registration, fees or scholarship dates live on other pages lists them under pages in scripts/sync-llm/venues.json; those are read every run and never rewritten. When a venue moves its dates page (they love doing this every year), a fallback agent finds the new one and fixes scripts/sync-llm/venues.json in the same PR.

To run it locally, put OPENAI_API_KEY=... in .env.local. If a synced value keeps coming out wrong, pin it with sync_pin: [place] (or start, end, date) and both syncs will leave that field alone. A deadline is pinned on its own item with pin: true.

Discovering Swiss events

The syncs only update events the calendar already has. A third monthly Action (pnpm discover:events) looks for new ones: high-level events held in Switzerland on frontier science, policy, diplomacy, geopolitics, business, societal challenges or foresight (GESDA, the St. Gallen Symposium, the Geneva AI Summit). It reads the pages listed in scripts/discover-events/sources.json, then runs a few OpenAI web searches per topic. As with the syncs, dates, city and name must all appear on the page, and courses, talks, webinars and UN body sessions are skipped. Strong fits are drafted into the YAML of a pull request and remembered in scripts/discover-events/seen.json, so a draft deleted in review is not proposed again; possible fits are only listed in the PR body. What counts as a fit lives in scripts/discover-events/criteria.js. It uses the same model as the deadline sync (gpt-5.6-sol), and a run costs roughly $1 to $2; --dry-run writes nothing and --no-search reads the sources only.

Stack

Next.js 16, React 19, TypeScript, Chakra UI v3, FullCalendar, Luxon, js-yaml. The site is a static export deployed to GitHub Pages; the Slack API routes run on Vercel, with Upstash Redis backing bot state.

Contributing

To add a conference, either open an issue with the details, or send a PR:

  1. Edit the right YAML file in public/data/
  2. Run pnpm validate
  3. Open a PR

Keep IDs lowercase (title plus 2-digit year, e.g. neurips25) and use a valid IANA timezone.

License

MIT: see LICENSE.

Contact

omarziyad.azgaoui2005@gmail.com

About

Track research conference deadlines: calendar, countdowns, ICS export, Slack reminders

Topics

Resources

Stars

17 stars

Watchers

1 watching

Forks

Used by

Contributors

Languages