Recurrence, done properly
A public event calendar and admin panel — Go and Postgres behind it, real iCal recurrence rules, Indonesian public holidays seeded on first boot.
A Go (chi) API on PostgreSQL with golang-migrate, S3 attachments and HS256 sessions, plus a Next.js front end with a TipTap editor that speaks images, audio, YouTube and file attachments.
Recurrence is the part everyone gets wrong. Events carry iCal RRULE strings, expanded server-side up to two years out, with children regenerated whenever the parent rule changes. On first boot it fetches this year's and next year's Indonesian public holidays in the background.
where the effort went
the numbers
expanded 2 years out
built with
delivery record
The organization needed a public schedule that staff could maintain without manually copying recurring events or Indonesian public holidays.
Public month and event views backed by a Go API
Administrative event workflow with rich TipTap media
RFC 5545 recurrence stored as RRULE strings
Two-year server-side recurrence expansion and regeneration
Indonesian holiday seeding on first boot
S3 attachments, PostgreSQL migrations, Docker, and release workflows
The constraints mattered as much as the finished interface.
after shipping
Recurring events are generated state and need a clear parent, horizon, and regeneration rule.
Calendar correctness lives in timezone and exception semantics more than in the month grid.