Static sites.
Run from Telegram.

The ready-made route would have taken a day: one external service for the form, another for the calendar. I turned it down. Form submissions carry people's personal data, and they would have landed on someone else's servers, while the calendar wanted a subscription on top. We wrote our own: slower to start, but the data never leaves our perimeter and the bill does not grow with traffic.

At first the site sat on free static hosting, and that was enough. The moment it needed our own form and calendar, free hosting stopped being an option: we needed a server running our own code. The second fork was whose infrastructure that would be. The more external layers, the more failures you cannot influence and rules that change without you. The VPS was already there, so everything moved onto it. The price of that choice: running the server myself, updates, TLS, firewall, monitoring. In exchange the site no longer depends on someone else's decision across the ocean.

Posts went through GitHub, and calendar edits through a separate form exposed to the internet behind a password. It worked, but it made the owner go where he did not want to go, and it kept an extra door open. I moved the entrance into Telegram. The door closed, and publishing stopped needing me: the owner sends a message from his phone and the site rebuilds itself. The system's state arrives in the same chat.

The hardest part was not in Telegram but in git. The bot writes files as its own user, I write as mine, and that has to line up locally and on the server without breaking ownership on files that already exist. Then backups that actually restore rather than merely run, and the ability to stand the whole system up from scratch on an empty machine. That took longer than publishing posts ever did.