Context
Event discovery can be fragmented, event data can be inconsistent, and manual publishing can be difficult to scale. Search and distribution also need to fit the product.
CASE STUDY / PRODUCT ENGINEERING
ocalendar: connecting event discovery with publishing operations
An event discovery product where software, data quality, publishing operations, and distribution meet.
01CASE RECORD
Public scope
An event discovery product where software, data quality, publishing operations, and distribution meet.
My role
I founded the product and led its product and engineering work, from planning and software through data workflows, automation, content operations, and organic distribution.
Constraint
The product depended on usable event data and a publishing process that could support discovery without relying on repeated manual work. The underlying growth and automation figures remain unverified.
System
The work included product planning, frontend and backend engineering, a CMS and data model, event ingestion and normalization, automation, content operations, SEO, and deployment.
Evidence boundary
The case is supported by product and engineering artifacts and the recorded scope of my ownership. Traffic history and the reported publishing-time change are excluded until their sources and methods are reconciled.
Learning
For a discovery product, data quality and the operating workflow shape the user experience as much as the visible interface does.