# GitHub Pages GitHub Pages is a static site hosting service that publishes HTML, CSS, and JavaScript files from a GitHub repository. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## One-shotting a Raccoon Heist game using Claude Fable 5 DevFeed: [One-shotting a Raccoon Heist game using Claude Fable 5]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-08-05T19:42:38Z Content type: tutorial Language: en Sources: [Simon Willison]() Topics: [Claude](), [Claude Code](), [GitHub Pages](), [GitHub](), [Code]() Tags: [ai](), [ai-2-235](), [anthropic](), [anthropic-336](), [browser](), [claude](), [claude-310](), [claude-code](), [claude-mythos-fable](), [claude-mythos-fable-41](), [code](), [coding-agents](), [coding-agents-248](), [fable](), [game-design](), [game-design-22](), [generative-ai](), [generative-ai-1-981](), [github](), [github-pages](), [iphone](), [llms](), [llms-1-947](), [prompt-engineering](), [prompt-engineering-197](), [text-to-image](), [text-to-image-47](), [vibe-coding](), [vibe-coding-97]() ### AI overview The article describes an experiment in which Claude Fable 5, running through Claude Code for web, built a Raccoon Heist game from an older GPT-3 game concept and screenshots. It also explains using GitHub Pages to preview work from Claude Code for web and notes that published content from a private repository may be viewable by anyone who guesses the repository name. ### Source excerpt Back in 2022 I tweeted screenshots of a game concept generated by GPT-3 and some concept "art" created using DALL-E. Today, on the fourth anniversary of that tweet, I decided to see if Claude Fable 5 (running in Claude Code for web) could build the entire game from the content of that tweet. It did a pretty good job of it! You can play the game here. Here's the GitHub repo, and a short video demo: Your browser does not support HTML5 video. How I built this This is the August 5th, 2022 tweet: My GPT-3 prompt back then was: Write a detailed product description of a computer game where a team of raccoons go on heists. This was in the text completion days, where you asked GPT-3 to complete the rest of the text. It completed: In "Raccoon Heist", you and your team of thieving raccoons are tasked with pulling off a series of daring heists. From robbing banks to stealing priceless art, no job is too big or too small for your furry crew. You'll need to use your wits and your skills to avoid the police and make a clean getaway with the loot. With exciting gameplay and a charming cast of characters, "Raccoon Heist" is the perfect game for anyone looking for a light-hearted caper. My prompt to DALL-E was short: Screenshot from a video game where a team of raccoons go on a heist Today's experiment: can I dump those screenshots into Fable 5 with a prompt telling it to write a game, then leave it to its own devices and get a working game at the end? Setting Claude Code for web up to use GitHub Pages A frustrating thing about Claude Code for web is that it can be hard to test what it's working on while it's still working. I've been using GitHub Pages to work around that limitation, and found it to work really well. Here's my process: Create a new repository for the project at https://github.com/new - this can be public or private, the trick works equally well for both. Start a Claude Code for web session, in the Claude iPhone or Desktop apps or in the browser at https://claude.ai/c ## A fresh start for michaelcrump.net and a return to writing in public DevFeed: [A fresh start for michaelcrump.net and a return to writing in public]() Original publisher: [Read original article]() Published: 2026-07-22T20:30:14Z Content type: opinion Language: en Sources: [Michael Crump]() Topics: [Website](), [GitHub Pages](), [Development](), [Tooling]() Tags: [development](), [github-pages](), [public](), [writing]() ### AI overview The author introduces a newly simplified michaelcrump.net, built with static pages, a small stylesheet, and GitHub Pages. The site will share practical notes about software development, developer tools, AI, and ongoing experiments. ### Source excerpt A fresh start for michaelcrump.net and a return to writing in public. ## Good Data For Bad Golf DevFeed: [Good Data For Bad Golf]() Original publisher: [Read original article]() Author: jgamblin Published: 2026-05-13T14:05:06Z Content type: article Language: en Sources: [Jerry Gamblin]() Topics: [Python](), [CSV](), [GitHub Pages](), [GitHub Actions](), [Self-hosted]() Tags: [analytics-pipeline](), [csv](), [github-actions](), [github-pages](), [pipeline](), [python](), [self-hosted](), [uncategorized]() ### AI overview The article presents jgamblin/golf, a self-hosted Python analytics pipeline that converts Garmin Golf app CSV exports into a multi-page GitHub Pages dashboard. It describes features including session analysis, club-level consistency, session replay, gapping, coaching recommendations, and data-quality tracking, with deployment automated through GitHub Actions. ### Source excerpt I play golf. I am not good at golf. But I have a Garmin Approach R10 launch monitor, a Python interpreter, and too much free time, so naturally I spent way more time building a dashboard to analyze my swing data than I did actually swinging a club. The result is jgamblin/golf, a self-hosted analytics ... Read more ## Migrating from GitHub Pages to Netlify in an Evening DevFeed: [Migrating from GitHub Pages to Netlify in an Evening]() Original publisher: [Read original article]() Published: 2026-03-25T00:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [migration](), [GitHub Pages](), [Netlify](), [GitHub](), [GitHub Actions](), [hosting](), [Astro]() Tags: [astro](), [dns](), [environment-variables](), [github](), [github-actions](), [github-pages](), [hosting](), [migration](), [netlify](), [secrets](), [ssl](), [workflow]() ### AI overview A first-person guide to migrating a static Astro blog from GitHub Pages to Netlify. It covers connecting the repository, transferring environment variables, moving DNS and SSL, restoring Mailgun email-forwarding records, and replacing a scheduled GitHub Actions rebuild with a Netlify build hook. ### Source excerpt Another hosting migration I'd been putting off for years, done in 30 minutes with Claude Code. ## I Shipped a Feature From My Phone During Lunch DevFeed: [I Shipped a Feature From My Phone During Lunch]() Original publisher: [Read original article]() Published: 2026-03-25T00:00:00Z Content type: opinion Language: en Sources: [Alex Korbonits]() Topics: [Claude Code](), [Vibe coding](), [JavaScript](), [Astro](), [GitHub Pages](), [API]() Tags: [api](), [astro](), [build](), [claude-code](), [development](), [github-pages](), [javascript](), [ml]() ### AI overview A developer describes building and deploying a stock price dashboard from a phone with Claude Code during a lunch break. The experience showed that AI can make implementation faster, while product judgment--such as choosing a useful data source--still requires human oversight. ### Source excerpt I shipped a working stock price dashboard from my phone during a lunch break using Claude Code -- and learned that execution is getting cheaper while judgment stays expensive. ## One GitHub Account, Many Domains: Deploying Family Sites with GitHub Pages DevFeed: [One GitHub Account, Many Domains: Deploying Family Sites with GitHub Pages]() Original publisher: [Read original article]() Published: 2026-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [GitHub](), [GitHub Pages](), [GitHub Actions](), [domain](), [Astro](), [hosting]() Tags: [astro](), [domain](), [github](), [github-actions](), [github-pages](), [hosting]() ### AI overview A practical guide to hosting multiple family-domain placeholder sites from one GitHub account using separate repositories, GitHub Pages custom domains, Astro, GitHub Actions, and DNS configuration. ### Source excerpt How I spun up four placeholder sites for family domains in under an hour using GitHub Pages, Astro, and GitHub Actions -- all from a single account. ## Building a /now Page That Updates Itself DevFeed: [Building a /now Page That Updates Itself]() Original publisher: [Read original article]() Published: 2026-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [Astro](), [GitHub Actions](), [GitHub API](), [GitHub Pages](), [RSS Feed](), [builds]() Tags: [api](), [astro](), [github](), [github-actions](), [github-pages](), [javascript](), [rss]() ### AI overview A tutorial on building an Astro /now page that fetches GitHub activity and Goodreads data at build time, then uses scheduled GitHub Actions rebuilds to keep the page current. It also covers local SSL issues and manually maintained content. ### Source excerpt How I added a /now page to my Astro blog that pulls live GitHub activity and Goodreads data at build time -- and rebuilds itself every morning without me touching anything. ## How to Migrate IPFS Websites from Fleek to Modular Infrastructure DevFeed: [How to Migrate IPFS Websites from Fleek to Modular Infrastructure]() Original publisher: [Read original article]() Author: Marcin Rataj Published: 2026-01-06T00:00:00Z Content type: tutorial Language: en Sources: [IPFS]() Topics: [IPFS](), [hosting](), [content addressed store](), [GitHub Pages](), [Self-hosted](), [GitHub Actions]() Tags: [cloudflare](), [github-actions](), [github-pages](), [guide](), [how-to](), [infrastructure](), [ipfs](), [migrate](), [object-object](), [self-hosted]() ### AI overview This practical guide explains how the IPFS Project migrated more than 15 websites from Fleek after its hosting service was discontinued. It describes a modular setup combining GitHub Pages for HTTPS hosting, Kubo for CID and CAR creation, IPFS Cluster for pinning, and DNSLink for URL mapping, providing both HTTP and IPFS access. ### Source excerpt A how-to guide for future-proofing your content-addressed website hosting. ## Orchestrate Sphinx projects with Bazel DevFeed: [Orchestrate Sphinx projects with Bazel]() Original publisher: [Read original article]() Published: 2025-03-25T00:00:00Z Content type: tutorial Language: en Sources: [technicalwriting.dev]() Topics: [bazel](), [Tutorial](), [Documentation](), [GitHub](), [GitHub Pages](), [Bash](), [Linux](), [Extension](), [Template]() Tags: [bash](), [bazel](), [build-system](), [docs](), [extension](), [github](), [github-pages](), [linux](), [repository](), [sphinx](), [tutorial]() ### AI overview An end-to-end tutorial on managing a Sphinx project with Bazel, including setup, documentation builds, local preview, extensions, and deployment to GitHub Pages. ### Source excerpt An end-to-end tutorial on managing a Sphinx project with Bazel. ## Why I Created a Personal Blog and Chose Zola with GitHub Pages DevFeed: [Why I Created a Personal Blog and Chose Zola with GitHub Pages]() Original publisher: [Read original article]() Author: Stanko Published: 2025-01-18T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [GitHub Pages](), [Website](), [static-site-generator](), [hosting](), [Programming](), [GitHub](), [WordPress]() Tags: [blog](), [github](), [github-pages](), [hosting](), [jekyll](), [programming](), [static-site-generator](), [website](), [wordpress]() ### AI overview The author explains why they created a personal blog, describing it as a way to maintain a personal website and share programming projects outside social networks. They discuss moving from Jekyll to Zola, keeping the site on GitHub Pages, and their interest in eventually building a static site generator with interactive posts and JSX. ### Source excerpt I've seen this challenge on Herman's blog. I liked it, so I decided to do my own version, even though I'm not using the bear blog. For the same reason, I slightly adapted the original questions. Why did you make the blog in the first place? # Since I first got online, I've wanted a personal website - a piece of internet I can call my own. I had a few websites over the years, but none of them are online anymore (and I don't have backups). Then, in my late twenties, I decided to try again. As someone who loves programming and making things, I've gathered plenty of material to share over the years. I also wanted to change the fact that I hadn't written much since high school. I've never been a fan of social networks, so starting a blog felt like the perfect thing for me -- I could have my own website and share the things I'm working on. This blog has been up since 2016, and I'm really proud of it. While the frequency of my posts has gone down, I like to think the quality has gone up. Why did you choose Bearblog Zola and GitHub Pages? # Before Zola, I used Jekyll, which is tightly coupled with GitHub Pages. GitHub Pages restricts you to the default Jekyll configuration, so I couldn't customize all the stuff I wanted. I started looking for a replacement and stumbled on Zola. It seemed very nice -- fast, a single binary, with a sane templating language. After trying it, I really liked it and decided to stick with it. I kept it deployed on GitHub Pages because I think they're great. Free and fast hosting, and the fact that I don't have to mess with deployments myself -- thanks, GitHub folks! However, for a long time now, I've wanted to write my own small static site generator. It would support interactive posts/components and use JSXI think that JSX is a great templating language. If I ever do it, I'll open-source it. Have you blogged on other platforms before? # As mentioned above, this blog used to be a Jekyll blog. Before that, I tried keeping a blog a few times, but only ## How I migrated a dev.to blog to a personal domain DevFeed: [How I migrated a dev.to blog to a personal domain]() Original publisher: [Read original article]() Author: Zach Klippenstein Published: 2024-07-06T19:34:26Z Content type: tutorial Language: en Sources: [Zach Klippenstein's Blog]() Topics: [Website](), [Development](), [Markdown](), [GitHub Pages](), [RSS Feed](), [ActivityPub]() Tags: [blog](), [github-pages](), [markdown](), [migrate](), [rss]() ### AI overview A personal account of migrating a blog from dev.to to a site on the author's personal domain. It describes requirements including customizable URLs, minimal maintenance, Markdown support, low cost, ActivityPub integration, and an RSS feed, along with reasons for wanting control over hosting and redirects. ### Source excerpt About a week ago, I migrated my blog to a New blog site! As I explained in that post, I was previously posting on dev.to, and while it mostly worked fine to post the content, I did not like having my content live on a domain name and I ## Optimizing Hugo static site redirects with Cloudflare Pages DevFeed: [Optimizing Hugo static site redirects with Cloudflare Pages]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Hugo](), [GitHub Pages](), [Cloudflare](), [hosting](), [Website]() Tags: [cloudflare](), [cloudflare-pages](), [cloudflare-redirect-rules](), [configuration](), [deploy](), [github-pages](), [hosting](), [how-to](), [hugo](), [hugo-redirects](), [hugo-site-redirects](), [seo](), [static-site](), [static-site-optimization]() ### AI overview This tutorial explains how to generate a redirects file from Hugo aliases, add custom redirects, and deploy it with Cloudflare Pages. It presents the approach as a way to handle more redirects than the author could support with GitHub Pages and Cloudflare's Free plan limitations. ### Source excerpt Learn how to optimize Hugo static site redirects using Cloudflare Pages, overcoming limitations of GitHub Pages and Cloudflare Free plan. ## Maximizing page performance and security with Cloudflare tuning DevFeed: [Maximizing page performance and security with Cloudflare tuning]() Original publisher: [Read original article]() Author: Tom Published: 2024-01-11T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Cloudflare](), [GitHub Pages](), [Security](), [Website]() Tags: [cloudflare](), [cloudflare-tuning](), [configuration](), [github-pages](), [how-to](), [http](), [http-3](), [https](), [https-configuration](), [page-performance](), [performance](), [security](), [static-site-optimization](), [tls](), [website-security]() ### AI overview A practical guide to tuning Cloudflare for a statically generated blog hosted on GitHub Pages. It covers HTTPS, HSTS, TLS versions, Brotli, and related settings, recommending that readers enable changes incrementally and measure their effects. ### Source excerpt Learn how to maximize page performance and security by tuning Cloudflare settings, specifically for a statically generated blog hosted on GitHub Pages. ## How to get a free .tech domain, connect it to GitHub pages and get a free SSL certificate DevFeed: [How to get a free .tech domain, connect it to GitHub pages and get a free SSL certificate]() Original publisher: [Read original article]() Author: Sanskar Agrawal Published: 2021-12-31T15:21:54Z Content type: tutorial Language: en Sources: [Sanskar's Stuff]() Topics: [GitHub Pages](), [SSL](), [Cloudflare](), [Website]() Tags: [cloudflare](), [copy](), [dns](), [domain](), [free](), [github](), [github-pages](), [how-to](), [ssl](), [technology](), [web-development]() ### AI overview A tutorial explains how developers can obtain a free .tech domain through the GitHub Student Developer Pack, connect it to a GitHub Pages site with DNS records, and configure Cloudflare nameservers to obtain a free SSL certificate. ### Source excerpt .tech domains are excellent personal domain names for developers because they basically put up your tech role upfront without even having to open your website. You can get one for free (for a year) by signing up for the GitHub Student Developer Pack ... ## I redesigned my site DevFeed: [I redesigned my site]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2021-06-24T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [Website](), [generative art](), [Web Components](), [HTML](), [JavaScript](), [Jekyll](), [GitHub Pages]() Tags: [components](), [generative-art](), [github-pages](), [html](), [ibm](), [javascript](), [jekyll]() ### AI overview The author explains why they redesigned their personal website: they were publishing fewer blog posts, wanted to showcase generative art, and replaced an outdated emoji custom element with a simpler implementation. The site continues to use Jekyll through GitHub Pages without a build step or minification. ### Source excerpt The last time I changed something big on my site was 3+ years ago. I was really into gradient rainbow text and IBM Plex Mono. It was a mild increment over whatever I had before, which was just a cleaned up and colourful version of Left from like 6 years prior. Anyway, what I'm saying is: this website had hella split ends. Here's the before and after: ↓ But also, why? I used to write a lot of blog posts, so my website was very blog focused. Originally the home page was just a listing of posts with some copy sprinkled in. As the pandemic hit, I started writing fewer and fewer posts, so having the one post of 2020 show up as a listing was ridiculous. On top of that, this year I started focusing a lot more on making generative art and I thought it was sad I wasn't showing that anywhere on the site! The beauty of generative art is that you can just keep generating it over and over again, and my site was a long white column of text. No more! git diff Ok so hear me out, this looks bad and that's because: it is bad. One cute thing my old site had was a custom element. You pressed it and got a rain of emoji. Brilliant. The problem is that I wrote that in like 2017, and used the well deceased v0 version of the web components spec. As a result, it had a gazillion dependencies (rip bower_components) and polyfills and ancient trash. 23906 lines of trash to be exact. Gooood riddance. The added 1580 lines are a bit of a bore: 100 of these are this post. another 300 is the HTML Ipsum from CSS tricks because I'm always scared I'm going to break a style on some ancient post. 300 lines of JavaScript for the header art that I don't minify because I'd like to be able to read this in the future to fix whatever mistakes past Monica made, and I don't have a build step set up. I'm still using the Jekyll that comes out of the box with GitHub pages and I am never looking back. the rest is actual code that I touched! There was some really horrifying markup on the project/talks/tem ## Running a blog with iPad DevFeed: [Running a blog with iPad]() Original publisher: [Read original article]() Author: Marco Gomiero Published: 2021-01-11T00:00:00Z Content type: article Language: en Sources: [Posts on Marco Gomiero]() Topics: [Hugo](), [Markdown](), [GitHub Pages](), [GitHub](), [hosting]() Tags: [blog](), [github](), [github-action](), [github-pages](), [hugo](), [markdown](), [static-site-generator]() ### AI overview The author explains a personal writing setup for maintaining a blog with an iPad, alongside the site's Hugo-based technology stack. The blog uses Markdown content, is built into a static website, and is published through a GitHub Action to GitHub Pages. ### Source excerpt It's been a few years since I started writing this blog, and I quite like sharing my thoughts and experiences. After a short while spent on Medium, I decided I wanted to be the sole owner of my content, so I started experimenting with different solutions and ideas. After I finally landed on the "perfect" tech architecture (I know, I'm lying. There's no perfect solution and Future Me will most likely refactor and (over)re-engineer the current solution), I started to seek the "perfect" writing setup. ## Jekyll & GitHub Actions DevFeed: [Jekyll & GitHub Actions]() Original publisher: [Read original article]() Author: JD Porterfield (jd.porterfield@alumni.rice.edu) Published: 2020-11-07T00:00:00Z Content type: tutorial Language: en Sources: [JD Porterfield | Articles]() Topics: [GitHub Pages](), [Jekyll](), [GitHub Actions](), [GitHub]() Tags: [github](), [github-actions](), [github-pages](), [jekyll]() ### AI overview This tutorial explains the limitations of deploying Jekyll sites directly through GitHub Pages, including its restricted support for Jekyll plugins and gem versions. It presents GitHub Actions as a way to build the site automatically on commits and publish the generated content. ### Source excerpt The standard GitHub Pages process imposes limitations on which Jekyll plugins we can use. Let's avoid this issue using GitHub Actions instead. ## Migrating From Jekyll to Hugo, deploying with Github Pages DevFeed: [Migrating From Jekyll to Hugo, deploying with Github Pages]() Original publisher: [Read original article]() Author: brice.dutheil@gmail.com (Brice Dutheil) Published: 2020-04-20T21:42:10Z Content type: tutorial Language: en Sources: [The Coffee Workshop]() Topics: [Jekyll](), [Hugo](), [migration](), [GitHub Pages](), [Markdown](), [WordPress]() Tags: [github-pages](), [hugo](), [jekyll](), [markdown](), [migration](), [wordpress]() ### AI overview This tutorial describes migrating a blog from Jekyll to Hugo and deploying it with GitHub Pages. It discusses challenges including preserving article links and comments, adapting templates and themes, local generation, and importing existing Jekyll content. ### Source excerpt Moving away form Jekyll. Import is easy, but tackling important details (conserve links to article, conserve comments, migrate some jekyll liquid template, theme tweaking deployment) has been challenging sometime. Motivation When started this blog in 2010 I went like a lot other to Wordpress as this was the one of the most common and easy way to write and publish something, then I got pissed at Wordpress as it was a pain to maintain and to write code, not to mention the speed, it was bad, then Github announced Github Pages, this was a revelation : articles written in pure Markdown, no database or server to maintain, fast writing, fast page thanks to static files. There were quite a few things that were icky like theme modifications, and some Wordpress plugins that were simply not there, but once done it was a robust machine. ## Adding Staticman Comments DevFeed: [Adding Staticman Comments]() Original publisher: [Read original article]() Author: Travis Downs (travis.downs@gmail.com) Published: 2020-02-05T00:00:00Z Content type: tutorial Language: en Sources: [Performance Matters]() Topics: [GitHub](), [GitHub Pages](), [Bot](), [Pull Request](), [Heroku](), [personal access token](), [hosting](), [repo]() Tags: [blog](), [file](), [github](), [github-pages](), [guide](), [heroku](), [hosting](), [meta](), [personal-access-token](), [pull-request](), [static-site](), [staticman]() ### AI overview A tutorial explaining how to add Staticman comments to a static blog. It covers the submission flow, deploying the API bridge on Heroku, using GitHub pull requests to store comments, and republishing through GitHub Pages. ### Source excerpt Adding static comments to a static blog using staticman. Static. ## Automating trivago's Tech Blog Deployment Process DevFeed: [Automating trivago's Tech Blog Deployment Process]() Original publisher: [Read original article]() Author: Busra Koken Software; Backend Engineer; Learning Every Day; Writing Stories Published: 2017-12-07T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Deployment](), [Automation](), [Hugo](), [Jenkins](), [GitHub Pages](), [Markdown](), [DevOps](), [Pull Request](), [Code review]() Tags: [automation](), [backend](), [code-review](), [deployment](), [devops](), [github-pages](), [hugo](), [markdown](), [release-engineering]() ### AI overview This article explains how trivago maintained its Hugo-generated tech blog, hosted it on GitHub Pages, and automated its deployment process. It describes the previous manual workflow, its bottlenecks, and improvements including storing a Jenkins pipeline in the blog repository. ### Source excerpt We do think that our tech blog is full of interesting things powered by our engineers' great stories. Let us take you on a journey of how we maintain trivago tech blog from the technical perspective and how we recently automated its deployment process. ## Jekyll Blog Setup DevFeed: [Jekyll Blog Setup]() Original publisher: [Read original article]() Author: Stanko Published: 2017-09-27T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [GitHub Pages](), [static-site-generator](), [Markdown]() Tags: [github-pages](), [jekyll](), [markdown](), [static-site-generator]() ### AI overview An outdated personal tutorial describing a Jekyll-based static blog hosted on GitHub Pages. It explains static-site generation, Markdown-based authoring, and starting from a quickstart guide or the Lanyon theme. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. Update, March 2020 # This post is outdated and I simplified my setup a lot. I'll try to cover my current setup in one of the future blog posts. Original post # Few days ago I got a following message on LinkedIn. Hi Stanko! I'm a junior front-end web developer and I recently found your amazing blog and fell in love with it. Since you don't have any other social media, I decided to contact you trough here even if it's not ideal. I was wonder what CMS you were using and if you could do a blog post about it ? So here it is, post about my blog setup. Jekyll # I'm not using a dynamic CMS but a static site generator called Jekyll. Static site generators take different approach to making websites. Instead of having a database, pulling data from it and dynamically building your pages, static site generators generate all the pages only when there are changes to the site. No moving parts, just plain HTML files. This approach is more secure, makes caching much easier and boosts performance. Smashing Magazine has a post on why static sites are awesome. Static sites are not limited to blogs. Bigger websites are also easy to build, once you get a hold of it. There are agencies that are even doing it for client work. It comes at the price that once it's built you need to deploy it somewhere. And you don't have fancy CMS interface, only good ol' markdown files. Build and deployment part is easy, just let GitHub pages1 do that for you. Handling a git repo with a bunch of markdown files should be fairly straight forward for any developer or tech savvy person. If you feel this is a big burden, then static site generators might not be for you. 1 There is Netlify as well, which I never used myself, but I've heard good things about it. How to start your own # I keep this blog on GitHub pages (obviously) and I would recommend you to do the same. If you want to start from scratch, start with official quickstart g ## Continuous Deployment: Hugo + Travis CI -\> GitHub Pages DevFeed: [Continuous Deployment: Hugo + Travis CI -\> GitHub Pages]() Original publisher: [Read original article]() Author: Chris Hager Published: 2017-04-25T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [CI/CD](), [Continuous Deployment (CD)](), [GitHub Pages](), [Hugo](), [Travis CI](), [GitHub](), [Git](), [Go Language](), [container]() Tags: [builds](), [ci](), [continuous-deployment](), [deployment](), [git](), [github](), [github-pages](), [go](), [how-to](), [hugo](), [travis-ci]() ### AI overview A tutorial on automating Hugo static website builds and deployment to GitHub Pages with Travis CI. Builds run when changes are pushed to Git, and deployment occurs after a successful build on the master branch. ### Source excerpt This post shows how to automate building and deployment of Hugo static websites to GitHub Pages using Travis CI. Builds are automatically triggered when pushing to the Git repository, and deployment when a build on the master branch succeeds. Hugo is a static website generator written in Go, and only requires a single binary. The easiest way to run Hugo in the Travis CI container is by including the specific hugo binary with which to build the site as part of the repository (eg. ## Setting up Travis, Jekyll and GitHub pages DevFeed: [Setting up Travis, Jekyll and GitHub pages]() Original publisher: [Read original article]() Author: Stanko Published: 2016-10-24T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [Travis CI](), [GitHub](), [GitHub Pages](), [ci](), [Ruby]() Tags: [ci](), [github](), [github-pages](), [github-personal-access-token](), [jekyll](), [ruby](), [security](), [travis](), [travis-ci]() ### AI overview This tutorial explains how to use Travis CI to build a Jekyll site and publish the generated files through GitHub Pages. It describes branch setup, webhook activation, a GitHub Personal Access Token, Ruby gem configuration, and a Rake task. The author warns that the setup may be outdated and no longer uses it. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. Update, November 2017 # I don't use this setup anymore, it might be outdated, proceed with caution. Original post # As I already mentioned, GitHub pages do not work with the Jekyll plugins. It is a security measure. So I researched it a bit, and colleague of mine proposed a simple solution - Travis CI. There is a great repo with instructions how to set everything up - jekyll-travis. But few steps are kinda confusing, and it took me 10 failed builds to make it work. So I'll try to help you with those. I copied the steps from the original repo and updated steps where I got stuck. Be sure to check the original readme as well. Flow # When you push to your GitHub repo, it triggers Travis Travis starts up a virtual machine and installs all required software (mostly Ruby gems). We use a custom rake task to tell Travis how to build our Jekyll site and push the updated content back to Github Travis clones a source branch (usually master or source, in my case source) Travis runs jekyll build on the source branch Travis does a git push to the branch holding static site files (usually gh-pages or master, in my case master) Github Pages starts serving the updated site Steps to make it work # Move your Jekyll source files to the source branch (name it as you like). We'll use master or gh-pages branch to host generated HTML website. Make sure you have enabled your source repo in the Travis CI admin dashboard so that the webhook is triggered Create a GitHub Personal Access Token from you profile page. If you haven't already, create a Gemfile, and add rake gem to it. source "http://production.cf.rubygems.org/" gem "rake", "~> 10.1.1" gem "jekyll-paginate" gem "jekyll-archives" We have seen intermittent timeouts fetching gems from Rubygems.org. install: bundle install lets Travis CI automatically retry, and we are using source "http://production.cf.rubygems.org/" in Gemfile to point to a different reposito ## Blog redesign and new features DevFeed: [Blog redesign and new features]() Original publisher: [Read original article]() Author: Stanko Published: 2016-10-20T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Jekyll](), [JavaScript](), [JSON](), [Pull Request](), [GitHub Pages](), [Jenkins](), [GitHub]() Tags: [also](), [blog](), [features](), [github-pages](), [javascript](), [jekyll](), [json](), [new-features](), [pull-requests](), [redesign](), [static-site]() ### AI overview The author describes a redesign of a personal blog and newly added features, including category pages, moderated comments through pull requests, JavaScript fuzzy search over post titles, estimated reading time, and sharing buttons. The article also discusses Jekyll plugins, GitHub Pages limitations on custom plugins, and planned build automation with Jenkins or Travis. ### Source excerpt Please note that I'm not using Jekyll anymore, so this post might be outdated. As you probably noticed I redesigned my blog and added some new features. This is a list of the new stuff. New design Category pages Comments Search Reading time Share buttons New design # My friend Nikola, from MIDA digital agency, helped me a lot with this one. I gave him a basic idea what I wanted, and he came up with this simple but beautiful design. It might go through some smaller changes in the future, but nothing major. Hope you like it. Category pages # These are accessible from the main menu, or by clicking on the category link at the end of the post. Obviosly, they list all of the posts for the selected category. This is the plugin I used: jekyll-archives. Comments # Staticman brings user generated content to the static site generators. You can add their bot to your repo, and then hitting specific endpoint will generate a pull request (or push directly) with the data user entered. My comments are going through pull requests, which enables me to moderate them. Search # Also accessible from the main menu. Search is done by JavaScript and it goes through JSON object with post titles. It uses fuzzy search algorithm, so it will find every title that has all of the letters you entered. Longer word matched will give higher priority to a result. (Try typing SASS for example.) Reading time # At the top of each post, you'll see estimated reading time. It is a very simple plugin I found somewhere on the internet and modified a bit. Here it is: # Outputs the reading time # Read this in "about 4 minutes" # Put into your _plugins dir in your Jekyll site # Usage: Read this in about "page.content | reading_time" module ReadingTimeFilter def reading_time( input ) words_per_minute = 180 words = input.split.size; minutes = ( words / words_per_minute ).floor minutes_label = minutes === 1 ? " minute" : " minutes" minutes > 0 ? "about #{minutes} #{minutes_label}" : "less than 1 minute" end end Liqui [Next page]()