Module overview

Events Coverage is the platform’s post-event editorial surface. Every coverage article is anchored to a parent CalendarEvent — there is no orphan coverage. It is where conferences, demo days, pitch competitions, and accelerator cohorts produce lasting editorial value beyond the day they happened: who won, what was announced, which founders broke through, which trends crystallised.

Module identity

Visual feel

Magazine-style. Wide cover image at the top, dek beneath title, bodyHtml renders pre-rendered HTML (not markdown). Coverage cards on listings show the parent event chip prominently — every reader sees which event this is covering.

Cadence

Event-driven. New articles cluster after major demo days, pitch competitions, and conferences. A single big event might produce 1 recap + 1 analysis + 1 highlights + 1 pitch-result piece — four CoverageArticles, all sharing parentEventId.

Canonical card

<app-coverage-card> with kind badge (recap / analysis / highlights / pitch-result / sponsor-spotlight) + parent event chip + author byline + publishedAt + readingTimeMinutes. Reused on the parent event details page, founder/startup profiles, and editorial cross-rails.

parentEventId is required

Unlike most cross-module references which are optional, parentEventId is the one non-nullable structural link on a CoverageArticle. No event = no coverage article. This contract enforces the "post-event editorial" identity of the module.