A fun idea. I've been playing with all sorts of ideas for static websites and trying to figure out ways to make them feel more "live".
I was wondering about the heartbeat updates and replaying the data in "real-time" the next day is a really nice touch and allows a single deployment a day.
Thanks! Curious what other ways to make them feel more "live" you've thought of already.
The 24h replay started as a constraint and turned into the design. Anything closer to live means a server holding a websocket open and my watch draining its battery to feed it. My homepage is markdown and a GitHub Action, and I wanted to keep it that way.
Thanks! I've been working out regularly for her past three years and eating clean and have noticed a steady decline in my rhr from the high 70s to the late 40s now.
A fun idea. I've been playing with all sorts of ideas for static websites and trying to figure out ways to make them feel more "live".
I was wondering about the heartbeat updates and replaying the data in "real-time" the next day is a really nice touch and allows a single deployment a day.
Thanks! Curious what other ways to make them feel more "live" you've thought of already.
The 24h replay started as a constraint and turned into the design. Anything closer to live means a server holding a websocket open and my watch draining its battery to feed it. My homepage is markdown and a GitHub Action, and I wanted to keep it that way.
Right now the HR is showing 48 bpm, so this has the fun side effect of demonstrating that the author is in pretty good shape.
Thanks! I've been working out regularly for her past three years and eating clean and have noticed a steady decline in my rhr from the high 70s to the late 40s now.
there is a neko too! :D