Links:
- 📜 Data Format Specification
- 💎 Zod Schema, which generate:
- Redirector
- Web App (example app that uses the format & APIs)
- data-server (example wip server)
A big project consisting of other smaller projects to attempt to solve the issue of event information management.
Back when I started going to cosplay conventions, in Turkey specifically, I had issues finding events and gathering information (date, time, place, price) about them. I created an instagram profile for announcing any events I came accross so others could find them too. After a while, I realized one crucial issue: properties of events are volatile, and can change; instagram posts cannot.
To solve this issue, I started developing a website for keeping a list of these events where users could follow events and recieve push notifications whenever something changes. At first I entered all the data manually, but the main idea was that event organizers would authenticate and update event data themselves. After a while, I noticed the need for i18n and implemented it, along with some other niche features. Developing the website sure took a while but it gave me valuable insight for the current event data format we are defining right here.
This monorepo aims to fix these issues with the other related projects:
- A single master event data format to rule them all
- A way to share and open event information in your preferred application
- A default web app to view events from many sources
- A server that allows users to collaboratively store and update event data