Skip to main content

Modules Documentation

Future enhancements

Backlog of planned features.

Complete

The current Calendar is feature-complete for v1. The next-quarter roadmap focuses on three themes: ingestion (lowering the cost of adding events), personalization (helping each user surface their relevant subset faster), and ecosystem syndication (becoming an upstream data provider, not just a consumer-facing app).

Ingestion enhancements

  1. URL paste import: editor pastes an organizer’s event page URL → server-side scraper proposes the field map → editor confirms 3-gate verification. Cuts manual entry time by ~70% for well-structured event pages.
  2. iCal feed subscription: organizers who maintain a public .ics feed (most major accelerators do) can register the feed once; new events from that feed land in the pending queue auto-populated.
  3. Auto re-verification: weekly cron pings sourceUrl on every verified future event. If the source page is gone (404) or the page text has changed substantially, the event is flagged for human re-verification.

Personalization enhancements

  1. Saved filters: authenticated founders can save filter combinations (e.g. "Egypt + accelerator + seed stage") and get a weekly email digest when new matches are verified.
  2. Reminders: per-event "remind me" button. Stores a userId + eventId + lead time (1 day / 1 week before deadline). Email + in-app notification fire.
  3. Stage-based defaults: pre-seed founder logged in → landing rails reorder to surface incubator + seed events first; growth-stage founder → enterprise conferences + investor meetups first.

Syndication enhancements

  1. Public iCal export per scope: every listing URL gets a .ics counterpart. Subscribe to /calendar/events/countries/egypt.ics in Google/Apple Calendar → events auto-appear in the user’s personal calendar.
  2. Partner widget: embeddable HTML/JS widget that renders the calendar (filterable) on partner sites (accelerators, ecosystem agencies). Brings Calendar reach beyond the platform without duplicating the dataset.
  3. Public read-only API: GET /api/calendar/events with filtering by country/category/audience/stage. Rate-limited, attribution required. Lets researchers + ecosystem analysts use the verified data programmatically.