Use Github Actions to deploy to Pages (#7)

* deploy to github pages

* add bundle install

* set branches to master

Author: burden

.github/workflows/deploy.yml

@@ -0,0 +1,56 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - master
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          ruby-version: '2.5.3'
+
+      - name: Setup Node
+        uses: actions/setup-node@v4
+        with:
+          node-version: '18'
+
+      - name: Install dependencies
+        run: |
+          bundle install
+          yarn install
+
+      - name: Setup outbound link tracking
+        run: |
+          npm install -g autotrack
+          mkdir -p src/_assets/vendor/ga
+          autotrack -o src/_assets/vendor/ga/out.js -p outboundLinkTracker
+
+      - name: Build Jekyll
+        run: bundle exec jekyll build --config _config.yml,_config.production.yml --trace
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: ./www
+
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

src/_posts/2025-11-12-cobwebs.md

@@ -0,0 +1,22 @@
+---
+layout: post
+title:  "Clearing out the cobwebs"
+date:   2025-11-12
+categories: updates
+---
+
+**Out with the old.** When this post is published, it will mark the end of a chapter for burden.cc. One where production was a `git pull origin master` directly on a DigitalOcean droplet. 
+
+**In with the new**. Today, I have the CDN itch. It's actually been on the task list since 2020 and it's really about shouldering the hosting and administrative burden onto someone else, since hosting a static site from a VPS feels like playing with fire. 
+
+So let's fix that. Github Pages is going to scratch the CDN itch. 
+
+Here's the rub. I'm already using Github Pages for a stage. 
+
+Netlify offers some interesting solutions for branch deploys, so I'm going to give them a shot. I have it setup so that when I push to the `staging` branch, I get a deploy. Also when I push to branches prefixed with `wip-`. 
+
+**tl;dr**  
+Removed: Travis CI, and Bower
+Added: Netlify, Yarn
+
+You won't, but [stay tuned](https://burden.cc/feed.xml) for more updates. I don't like the way Netlify is currently configured to deploy, and I would love to get some checks in place.