coronation.xyz is a site that visualizes the progress of the COVID-19 infection around the globe. It uses features of global data to highlight and modify the globe to reflect the status of the infection over time.
I decided to go with web for this project because it’s a universal platform and I figured if I was building something to reflect on the global situation then I shoul make it as globally available as possible.
Though my recent web projects (see maudern and monoform) have largely been built with p5js, I decided to go with three.js instead. I didn’t do this based on the library features per se, instead I did it based on the availability of a key package. I knew the hardest part about this would be to construct a 3d globe, overlay it with geojson data, and have the ability to update parts of that overlay based on the geojson data so I looked for js implementations of such globes and eventually found three-globe. After looking at the docs, I confirmed that it should do everything I needed then dove into a quick example to make sure I could get it working. Once that proved fruitful, I decided to go with it - threejs is something I’ve wanted to play around with for awhile and the globe thing was pretty full-featured.
For projects like this I’ve historically gone the single page app route, using ReactJS, SemanticUI, and NextJS (see thevalueofmoney, mineforgood, and willigetcancer) but I’d just done a major revamp of my sites so Hugo - the static site generator I use to build my sites - was top of mind.
I thought about what my site really needed to have - a landing page on which to display my canvas and a way to style things non-manually - and realized that Hugo offered all of these features plus the benefit of having a significantly ligher payload. The smaller payload is important to me as I just ran the calculations and found that I can serve about half a million users / month for free in my current hosting paradigm but this is based on the bandwidth I use so adding additional payload would substantially eat into this number of users. I ran a quick test and found that one of my sites using my previous stack of ReactJS, SemanticUI, and NextJS clocked in at around 234kb per page (served by me) whereas my Hugo builds were closer to 107kb - meaning I’d reduce my user capacity by half to ~230k / month. In hindsight, Hugo was a pretty good choice as the geojson I’m using is 138 kb, bringing my Hugo-based site to a total of ~247 kb vs the ~372 kb required if using the previous stack.
All in all, doesn’t really matter as I’d just offload some of my big payload items (css and geojson) to my static resource repo if I started getting close to the Netlify free tier cap, but saving ~30% of used bandwidth per load isn’t half bad either.
As implied in the previous section, I’m again using Netlify to host this project. It’s easy and it just works. Plus free. Did I mention free?
Hi I'm Hamilton and I wrote / built this! I like doing lots of things, but mostly I like to build (and then share those buildings). Some things I'm currently building: art, software, and prose. To stay up-to-date with my latest buildings, subscribe to my email list or follow one of my many other accounts. #buildit #shipit #justhamit