Technology · Hugo

Welcome to Hugo (from Jekyll)

How I got started with Hugo and stopped using Jekyll

Welcome to my wholly reworked website! This time, I've dropped the complexity of Wordpress and opted for something significantly simpler: Jekyll Hugo and GitHub.

Having now hosted the site in GitHub Pages, here was the process I started with Hugo:

  1. Created the Github Pages repo (rterakedis.github.io) -- this is where github pages looks for the blog's generated site files.
  2. Created a 2nd Github repo: rterakedis.github.io.hugo -- this repo holds the source files for Hugo to parse and generate the site.
  3. Added the GH Pages repo (rterakedis.github.io) as a submodule for rterakedis.github.io.hugo
  4. Edited the config.toml in the hugo files to include the following:
  • baseURL = "https://terakedis.dev/"
  • publishdir = "rterakedis.github.io"
  1. Add the CNAME file into the rterakedis.github.io repo and enable the custom name/https in the repo settings
  2. Ensure the output from hugo builds into the rterakedis.github.io directory in my local rterakedis.github.io.hugo directory
  3. Commit and push everything to GitHub

A few quick links that I found particularly helpful when I was working with Jekyll:

Read More...

2026.08 leanwheel-skills, Round Four: Fewer Guardrails, More ProofRound four of leanwheel-skills: aligning with Anthropic's skill-authoring guidance, gates that can prove they're able to fail, and protecting hard-won field knowledge from well-meaning refresh passes. 2026.08 leanwheel-skills, Round Three: Skip the Docs, Keep the DisciplineRound three of leanwheel-skills: a doc-free single-goal lane that keeps the verification discipline, some context-debt paydown, and two proposals I wrote down instead of building. 2026.07 Knowledge Pitfalls in Productivity - Lessons LearnedWhy do organizations still struggle with Knowledge Management?