Kliku Kliku

A focus framework: The Pomodoro technique

Tue, 24 Mar 2026 00:00:00 +0000

Introduction

Have you ever wondered why your productivity drops so much after just a few hours of coding? I noticed something in my own workflow: the biggest enemy of focus isn’t a lack of knowledge. It is constant context switching.

Chat messages, emails, and “quick questions” from teammates constantly break our rhythm. I decided to look for a solution, and for the past few weeks, I have been testing the Pomodoro technique. Today, I want to share my findings with you.

OpenCode inside Docker: How to safely run AI in your local terminal?

Tue, 17 Mar 2026 00:00:00 +0000

Introduction

I’ve recently been looking into how to run AI tools safely within our local environments. Tools like OpenCode are great, but they give algorithms a lot of freedom to interact with our files. I usually follow the principle of limited trust, which led me to try running OpenCode inside a container. This way, it only has access to the specific files and directories it actually needs.

Why isolation matters

When we allow AI models to generate and run code, we are essentially giving them partial control over our terminal. Even if we trust the provider, a simple bug in a generated script could cause a mess in our file system. The solution? Containerization.

Cusdis Comments in Hugo: A Lightweight Solution Without Tracking

Tue, 10 Mar 2026 00:00:00 +0000

Introduction

While looking through comment systems for static blogs, I decided to check out Cusdis. It promises a “low-friction” approach: a simple widget, no ads, and no heavy tracking in the background. Cusdis positions itself as a lightweight, privacy-friendly alternative to Disqus. It is an open-source project with a self-hosting option and a managed version at cusdis.com. You can find a detailed guide on how to self-host Cusdis in a separate post: Self-Hosting Cusdis on a VPS.

Styling Cusdis: Taking Control of the Iframe Without Touching the Source

Tue, 03 Mar 2026 00:00:00 +0000

Introduction

I recently looked into implementing a comment system based on Cusdis. It’s a lightweight and privacy-friendly solution, but it comes with a UI challenge: the widget renders inside an iframe.

What does this mean for us? An iframe creates an isolated environment. The CSS styles we have in our project don’t leak inside. As a result, if our layout has specific branding, the default, minimalist Cusdis design looks like a part of something else.

Self-hosting Cusdis Comments with Caddy on a VPS

Tue, 24 Feb 2026 00:00:00 +0000

Introduction

When I was looking for a comment system, I quickly realized that most available solutions either track users, require heavy JavaScript, or simply cost money. Cusdis stands out from the crowd. It is lightweight, open-source, and built from the ground up with self-hosting in mind.

In this post, I show how to deploy Cusdis on any VPS using Docker and Caddy as a reverse proxy, with correctly configured CORS headers.

Giscus Comments in Hugo: Lightweight GitHub Discussions Integration

Tue, 17 Feb 2026 00:00:00 +0000

Introduction

As part of my review of comment solutions for static blogs, I decided to test Giscus. It is an open-source tool that uses GitHub Discussions as its backend.

I was intrigued mainly by the promise of high performance and privacy. Below, I present an analysis of this solution, an implementation guide for Hugo, and the conclusions from my performance tests.

What exactly is Giscus?

Giscus is a widget that connects your website directly to the GitHub API. When a reader leaves a comment under a post, the system automatically creates a new discussion (or adds a reply) in the connected GitHub repository.

Disqus Comments in Hugo: Setup Guide and Performance Analysis

Tue, 10 Feb 2026 00:00:00 +0000

Introduction

Disqus is probably the first solution that comes to mind when we think about comments on static sites. It has been with us since 2007, supports millions of websites, and takes the burden of building a backend off our shoulders.

I decided to check what its integration with Hugo looks like in 2026, but mostly, what the real cost of this convenience is. I ran performance tests on this blog, and the results might surprise you.

Hugo Optimization: Complete Guide

Tue, 03 Feb 2026 00:00:00 +0000

Introduction

Over the past few weeks, I conducted a comprehensive optimization of my Hugo-based website. What started as curiosity about whether I could squeeze more performance out of a static site generator turned into a series of experiments with concrete, measurable results.

The starting point was good. Hugo naturally generates fast pages. My Lighthouse score hovered around 92-94 points. However, analysis in Chrome DevTools revealed problems invisible to the naked eye. Nearly fifteen megabytes of transfer on the homepage. Fifteen separate CSS files generating one and a half seconds of delay. No caching strategy for returning visitors.

Hugo JS Optimization: Bundling, Fingerprinting, and Caching in 15 Minutes

Tue, 27 Jan 2026 00:00:00 +0000

Introduction

After cleaning up CSS styles and optimizing images, I focused on the JavaScript layer. At first glance, the situation looked innocent. The site was loading two files: a script from the theme and my own code for handling the color theme toggle. Together, they weighed less than three kilobytes. With such a small size, optimizing here might seem like overkill.

However, the real challenge was hidden in the HTTP headers. I noticed that both files had a one-year cache lifetime. Unfortunately, their names lacked a unique identifier, or a “fingerprint.” This created a serious risk. It meant that after deploying any fixes, users would still use the old version of the code saved in their browsers.

HTTP Server Optimization for Hugo: GZIP, Cache Headers, and Fingerprinting

Tue, 20 Jan 2026 00:00:00 +0000

Introduction

We often focus on HTML minification or CSS bundling, treating it as the end of optimization. However, I’ve noticed that even the best-prepared files can load slowly if we forget about the HTTP server layer. That’s where untapped potential lies, worth exploring.

In my practice, two configuration elements prove crucial. First, GZIP compression. From my experience, it can reduce text file sizes by sixty to seventy percent. Second, proper Cache headers. They eliminate unnecessary requests on subsequent user visits. Today I’ll show you how to configure a server for a Hugo-based site to squeeze maximum performance from static files.

CSS Optimization in Hugo: Minification and Bundling for Maximum Performance

Tue, 13 Jan 2026 00:00:00 +0000

Introduction

We often focus on optimizing JavaScript or images, while treating CSS styles as somewhat secondary. We assume that since individual files weigh just a few kilobytes, they’re not a problem. But that’s a false assumption. The way we deliver these files to the browser can have a crucial impact on how quickly users see the finished page.

When I looked into Chrome’s developer tools, I noticed a specific problem on my site. My page was loading fifteen separate CSS files. Combined, this generated a delay of around one point six seconds. Interestingly, the data size wasn’t the issue at all. GZIP compression was working correctly and reducing file weight by over sixty percent. The real bottleneck turned out to be the sheer number of HTTP requests. The browser was wasting time establishing connections instead of downloading content.

Hugo Image Processing: How I Reduced Page Size by 98%

Tue, 06 Jan 2026 00:00:00 +0000

Introduction

Images are usually the biggest obstacle to website performance. Although Hugo generates fast static sites by nature, unoptimized images can completely cancel out this advantage. I decided to investigate this using my own website as a case study.

Analysis in Chrome DevTools clearly showed the source of the problem. Images made up 96% of the total transfer, adding up to nearly 15 MB. I identified three large PNG files that caused most of this traffic and increased the load time to over 4 seconds. For mobile users, this meant a long wait and wasted data.

Symfony Quick Start: Docker & Makefile

Tue, 30 Dec 2025 00:00:00 +0000

Introduction

I recently spent a lot of time optimizing my local environment. I realized that I had fallen into the trap of overcomplicating things. I was building huge docker-compose files and hiding logic inside scripts. Because of this, I lost sight of what really matters.

I decided to go back to basics and focus on simplicity. My current setup for Symfony relies on two things: pure Docker and a Makefile. For the development image, I chose the latest PHP version and SQLite support. This allows me to start coding instantly. I do not have to waste time configuring heavy database containers.

Comment Systems Performance Test

Mon, 29 Dec 2025 12:09:04 +0100

This is a dedicated test post for measuring the performance impact of different comment systems on our Hugo site.

Testing Methodology

We’re comparing four popular comment systems:

Disqus - Popular third-party solution with cloud hosting
Giscus - GitHub Discussions-based, open source
Cusdis - Lightweight, privacy-focused solution
Remark42 - Self-hosted, privacy-focused with rich features

Performance Metrics

For each system, we measure:

Page Load Time - Total time to fully load the page
JavaScript Size - Amount of JS downloaded for comments
HTTP Requests - Number of network requests made
PageSpeed Score - Desktop and Mobile performance scores
Core Web Vitals - FCP (First Contentful Paint) and LCP (Largest Contentful Paint)

Test Environment

Hugo Version: v0.152.2 extended
Theme: Terminal v4.2.3
Browser: Chrome/Brave (latest)
Network: Real-world conditions via PageSpeed Insights
Cache: Hard reload (Ctrl+Shift+R) for accurate measurements

Baseline Measurement

Before testing any comment system, we capture a baseline measurement of the page without comments to understand the base performance.

Google Tag Manager in the Hugo Ecosystem

Tue, 23 Dec 2025 00:00:00 +0000

Introduction

I recently worked on adding analytics to a Hugo project. Usually, adding a tracking script takes just five minutes. But doing it the right way is a different story. If we want it to be fast and respect user privacy, it becomes a more interesting challenge.

Below, I have shared my notes and a step-by-step guide for Google Tag Manager and Google Analytics 4. I focused on keeping the code clean. I also made sure the Cookie Consent really works, rather than just looking like it does.

Hugo + GitHub Actions: a simple deployment pipeline

Tue, 16 Dec 2025 00:00:00 +0000

Introduction

The simplest way to automatically deploy a Hugo site is this: keep the whole project in a GitHub repository, and let GitHub Actions build the site on every push and upload the generated public/ directory to your server over SSH using rsync.

Assumptions

Here I assume two things.

First, you already have a working Hugo project locally. For example, you created it with hugo new site your_site and you checked that running the hugo command locally correctly generates the public/ directory.

Hugo vs Sulu

Tue, 09 Dec 2025 00:00:00 +0000

Introduction

In this article, we will look at two tools that follow completely different philosophies: Hugo and Sulu. Both are open‑source solutions for building websites, but they solve problems in very different ways.

Let’s start with Hugo. It is a static site generator written in Go. Its main job is to transform source files into ready‑to‑serve HTML, CSS and JavaScript, which we can then host on any server. What really sets Hugo apart is its speed – site builds are extremely fast. The community around the project has been growing dynamically and has already gathered over eighty‑five thousand stars on GitHub. It is, however, a very developer‑centric tool. Content is edited mainly in Markdown files stored in a Git repository, and the publishing workflow is tightly coupled with version control.

Pomodoro Timer

Mon, 01 Jan 0001 00:00:00 +0000

What's going on

Mon, 01 Jan 0001 00:00:00 +0000

Hi there

They say you need a strategy to start a project. Right now, I only have motivation and a keyboard.

I am not sure yet if this will be a technical guide or a developer diary. For now, I treat this place as my “external memory.” I collect solutions and ideas here that I want to save for the future, so I don’t have to search for them twice.