Data Driven Site
I’m quite proud of my homepage. As I said before, I used to use services like Flavors.me and About.me for my main page because they did something particular…that gathered my info in one place. From social sites to image sites, these tools did that easily. But I started to realize I wasn’t showing what I really wanted…additionally I was having a hard time keeping those connections up as well. So it was time to make my own.
I had some initial requirements. There’s weren’t hard requirements, but based on my previous experiences, I found that I should listed to a number of these.
Easy Inclusion into My Tool-Chain
First question is: “What’s your tool-chain?” In simplest terms, I switched from Pelican’s excellent static site generator, to Hugo. If I couldn’t get the system to work in Hugo, it would mean looking at a new system. Functionally, we are good.
No or Minimal Back-end Work
Where I can setup any back-end tool I want on my VPS, I didn’t want to maintain it. There is a possibility I could use Firebase, but I wasn’t sure on the details and restrictions on the free-tier. So I needed a tool that provides my back-end. This site does this through some creative wrangling (more on this later).
Complete Integration with My Notebook
I didn’t want Hugo to handle my notebook (blog) and then some other system for my main page. But separating the two wasn’t out of the question. This would be like I did before, but my goal was to keep everything in order.
Ok, so let’s move down the page and talk about what/how/why/etc.
Interactive Title Banner
Fitbit and Dash
This was hard. I was determined to get more detailed Fitbit and driving data (using Dash) on the page. But getting to it without exposing a personal API key seemed impossible. This is where some nice tools came in. I didn’t need 100% of the data, just last month or so. So I am using IFTTT to send updates to a Google Spreadsheet. From there I was just going to ping the sheet, but Google restricts getting data cleanly due to CORS restrictions, so I hit my first hurdle.
I actually was able to make a personal API. Using APISpark from Restlet, I’m able to use Google Spreadsheets as my data store and make them accessible from an API call.
Check it out. There’s nothing on that I don’t care being out in the open, but it’s pretty need to see what’s happening. I have one for Fitbit, Dash, my Book reading, my Music (more on that later), and Twitter statuses. If I want more, it only requires me to see what IFTTT can offer and push it to a Spreadsheet.
(Later on, I may dump the spreadsheet entirely and have IFTTT post directly to the API…but my Google Sheet is doing some calculation legwork for me at times and I’d have to be able to replicate that. I think I’ll work on an additional post for this later…)
Another hurdle was figuring out how to present the data. After looking through some options, I like my CSS only slider style “Tabs”. It hides other information but brings it forward when you want. It’s a little bit of flair that I like to see.
Again, grabbing my latest tweet from Twitter’s API required me creating some back-end pass-through or exposing my API token. So I use IFTTT to dump my latest tweet into a Spreadsheet and get the data from my Personal API. Same for Goodreads, although I have to use Goodread’s RSS feed and do some wicked work on the formatting because of this…but it looks good. Github was a letdown. The details I wanted aren’t easily available. So I’m using the contributions graph third-party service which gets me an image. Also, I’m hosting this site’s source code on GitLab for now, I’m trying it out as an alternative but will probably move it to Github soon.
Utilizing my Personal API, I gather my listening data from Last.fm. Last.fm!?! Still? Yes, I pretty much listen to all my music exclusively through Amazon Music. And there’s really no way to get it out, except for scrobblers on my phone and on the web. Being a Prime customer, Amazon Music is an amazing system. I wish they had an easy way to get user stats out…oh well. Scrobbling is why Last.fm still gets my data. From there it’s to a spreadsheet! Movies and Television data come from Trakt. I’ve been using Trakt for a long time and recently realized it has really help me keep track of what season I’m on in various shows. And I’ve just started recording my movie watching with it. So I might as well use the data!
Lastly, I have some random bits I wanted to include. I’ve always shown my PGP data in one form or fashion, but this allowed me full control. So I’ve got my data right there to see and available for anyone to use. If there are questions about identity, I really like Keybase’s (I have invites…) form of identity management. Although recent news claims that BitCoin is having a rocky time, I figure it’s not completely dead and feel free to send me money.
So this doesn’t disappear…still need to host the site. I still serve everything on a VPS, so I still need a webserver. Why I bring this up is that I found Caddy. Caddy is a single executable that works comparably to Nginx, but is so much simpler to use. It also has some integrated features for Hugo and more. Additionally, it automatically integrates HTTPS with Let’s Encrypt so I have fully encrypted site (save some of the images from above) without the hassle of dealing with a CA and server setup. It was the fastest I got from, clean VPS install to up and running I have ever had…I’m still amazed.
That’s the gist. It’s pretty neat to have a semi-dynamic site that is built with a static site generator. I plan on playing more with Restlet’s APISpark to see what else I can make it do, but for now the Google Sheets is doing fine. I might also explore Firebase or Stamplay in the future, but happy with what Restlet is providing. Stamplay may allow me to embed of the code that Google’s Spreadsheet is handling and I can have a fully integrated API.
Since I cannot really beta test a personal site, if you run into any bugs, ping me. I’m still learning and hope to have some better idea as things go…might even add more info…more data!!