But for a static site, it would be a pain to need to compile and deploy after every tweet. Luckily, by stitching together some simple tools, this can all happen automagically whenever a new tweet is posted.
My site, this site, is made with Jekyll. Perhaps the most popular static site generator. I already have a few bits of Gulp as part of my build automation and the whole thing is hosted on Netlify, my very favorite static site hosting service.
Pulling tweets into the codebase
To bring recent tweets into the site, I add a gulp task which requests my recent tweets from Twitter's API, and stashes them in a YAML Data file. Jekyll makes YAML Data files available to its templates so I can use the content however I need.
So far, so simple. Now to trigger a build and deployment whenever I tweet.
Netlify can run your build for you in their environment in exactly the same way that as it runs in your local development environment. The output then gets deployed to their distributed CDN.
Triggering the build
There are lots of ways to trigger a Netlify build, but what we need here is webhook. In Netlify's site settings, we create a webhook and now we have a URL which will trigger a build and deployment whenever it recieves a POST request.
Now to monitor a Twitter feed. I'm trying to keep away from the need to host any server or service myself, so I just turn to If This Then That, the service automation... um... service.
IFTTT has channels to monitor twitter feeds, and also has the ability to make requests to Webhooks, so all that is required it to configure an IFTTT Applet to tie these things together.
Pulling it all together
- IFTTT monitors activity from my twitter feed
- New tweets result in a call to a webhook
- POST requests to the specified webhook invoke a new build on Netlify
- The site build pulls in recent tweets from the Twitter API and includes them in the home page of the site
- Victory dance