UPDATE, January 2022: Bridgetown 1.0 beta has been released! 🎉 I've updated the setup instructions below.
Sarcasm aside, Jekyll seems to be built on a solid enough foundation, but unfortunately it has not received a lot of updates in recent years. Is this another arena where, as they say, Ruby is dead?
Enter Bridgetown, a fork of Jekyll which aims to compete toe-to-toe with its modern JS cousins, providing even more Ruby tools for building static sites. Very exciting.
Many of Bridgetown's Ruby upgrades are already released, so I (happy for any chance to write Ruby) rebuilt and extended this blog with Bridgetown. Here's how I did it. Note that these instructions apply to Bridgetown 1.0, the latest version at the time of writing. Also note that a knowledge of Ruby is assumed here, but not necessarily any prior experience in building a static site.
- Follow the steps on Bridgetown's Getting Started page.
- To create the site, I ran
bridgetown new blog -t erb. The added option is to use ERB tempates, rather than the default of Liquid.
- See also all the command line options.
- If you already know of some bundled configurations that you need (see below), you can include them in the
newcommand. In my case:
bridgetown new blog -t erb -c turbo,stimulus,bt-postcss
- To create the site, I ran
- Add bundled configurations that you need. In my case:
- Turbo for faster page transitions.
- Recommended PostCSS plugins. I also installed this extra PostCSS plugin that adds support for inline comments in CSS files.
- Install plugins that you need. In my case:
- Set your preferred permalink style.
- Set up pagination.
- Set your site's info in
- Kickstart your site's design with a CSS theme. I chose holiday.css, a classless stylesheet for semantic HTML. Or you could use an actual Bridgetown theme, such as Bulmatown. (That's the only Bridgetown theme as of January 2022, but I expect more will come soon from the community.)
- Add a Pygments CSS theme for code syntax highlighting.
- Either download one of the handily premade CSS files, or pick from the full list then install Pygments and make it generate a CSS file. (I picked one of the premade stylesheets and then created a second one to override some of the colors.)
- Place the CSS file in
- Import it into
frontend/styles/index.css: for example, for Monokai place
@import "monokai.css";near the top of
Next I designed and built my site, a process which was mostly unremarkable, except for one thing: I built a Ruby component and plugin for a complex, data-heavy part of a page. For simpler parts of a page I just used partials, such as
_tweet_button.erb. But for any significant manipulation of data prior to rendering, building a Ruby component makes more sense. In my case, I wanted a "Reading" page that lists titles from my
reading.csv file (my homegrown alternative to Goodreads), including only books that I rated at least a 4 out of 5.
Following the doc on Ruby components, I created a
ReadingList component in
_components/reading_list.rb, and its template
Then I fleshed out
reading_list.rb to load my reading list and provide data for the template
reading_list.erb. The CSV-parsing code is pretty complex, so I separated it out into a gem.
Thanks to a tip (one of many) from the Bridgetown creators on the Discord server, I realized my Ruby component had way too much logic in it which should be separated out into a plugin. So I dove into the docs on plugins and moved nearly all of my component's code into a plugin.
So now the plugin parses my CSV file (using my parsing gem) and saves it into the site's data. Then my component's
.rb file pulls that data into instance variables. Finally, the ERB template uses the instance variables as it displays the reading list.
If you create a plugin and want to make it more easily available to other Bridgetown site creators, you should make it into a gem and possibly create an automation for it. I didn't for my reading list plugin, because the intersection of people who track their reading in a CSV file and people who will make a Bridgetown site is… very few people, I'm sure.
One possible improvement remains. Currently, to update the reading list I must delete it (
_data/reading.yml) and rebuild the site locally (so that my
reading.csv can be re-parsed) before pushing it to be built and deployed on Netlify. I could avoid these manual steps by taking advantage of the fact that my
reading.csv is automatically synced to Dropbox: I could change my plugin to connect to Dropbox and update the list from there instead of from the copy on my local machine.
Now in October, three months later, I've made the improvement proposed above. My Bridgetown plugin now connects to my Dropbox account, reads my
reading.csv file from there, parses newly added items, and adds them to my site's data. I'm storing my Dropbox keys in Netlify environment variables, which are passed into Bridgetown in
ENV. Now my reading list can be updated in a Netlify build, without me having to first build it locally and push it.
This paved the way for an even cooler improvement: I followed this guide to setting up automatic Netlify redeploys via GitHub Actions, and now my site rebuilds itself every week. This means that my site's Reading page is synced weekly to my
reading.csv, and it's completely automatic! Now I'm starting to see how static sites, in spite of their simplicity, can feel quite dynamic if they are automatically rebuilt often, using content added via APIs.
But what I really loved was using what I already knew (Ruby) in a completely new way. Bridgetown is doing a wonderful job of bringing the joy of Ruby into the world of modern static site generators.