The weather pipeline behind Forecastly
Forecastly doesn't hit one neat endpoint and call it done. It geocodes an address, walks the Weather.gov API, reshapes multiple responses, and caches the result at the boundary that matters.

Forecastly doesn't hit one neat endpoint and call it done. It geocodes an address, walks the Weather.gov API, reshapes multiple responses, and caches the result at the boundary that matters.
The Fahrenheit/Celsius switch in Forecastly is small, but it draws a useful line: keep presentation state in the browser, keep data ownership on the server.
I wanted Forecastly to feel smooth without turning it into a React app. Turbo Frames, lazy loading, and a couple of small Stimulus controllers were enough.