A production needed one operational source of truth.
Weather, transport, purchases, documents, technical tools and communication can easily end up split across chats, spreadsheets and links. Jona's operations hub brought those areas into one interface to reduce search overhead and coordination mistakes.
Forecast comparison by day, time and area.
Vehicles, routes and meeting points.
Scripts, plans, call sheets and inventories in one place.
Camera, lighting, sound and backup tools centralized.
Weather was operational data, not decoration.
The preserved weather system combined INUMET, MetSul, ECMWF and GFS through Python and GitHub Actions. The goal was to compare sources and maintain a useful per-day, per-location view instead of depending on one app or manual check.
When production ended, the periodic workflow was removed. Historical weather data remained, but the automation did not keep running without an operational need.
Turning systems off is part of operating them well.
At production close, names, transport assignments, internal document links, call sheets, communication access and other private operational data were removed. Offline behavior was disabled and old caches were explicitly cleared.
The public archive keeps project structure, locations and dates, but must not expose phone numbers, email addresses, medical data, payment information or other personal identifiers.
Technical operations from setup through shutdown.
Jona demonstrates more than building a page: understand what information an operation needs, centralize it, automate repetitive work, keep it useful for a defined window and retire it correctly when that window ends.