About this project

This repository holds the source of a personal blog and website that is generated as a static site with Jekyll and the Chirpy theme. The site is published through GitHub Pages, and the README points to the main site, a separate development/preview deployment, and an external documentation index. Content organisation The blog aggregates posts from several historical sources, including the current site, a group of Kubernetes-related GitHub Pages sites, and two older Linux-focused blogs whose content dates back to 2009. The README tabulates the distribution of posts by source and year, and lists 14 categories and 55 tags with per-source counts. Recurring subject areas include Linux, Kubernetes, networking, cloud, security, DevOps, OpenWrt, virtualization, storage, Android, photography and Windows. Tag counts show which topics appear most often, such as kubernetes, amazon-eks, security, eksctl, bash, cert-manager, wifi and pxe. Category and tag index pages are generated so posts can be browsed by topic. Theming and site generation The site is based on the open-source Chirpy theme, and the README links to both the theme repository and a companion site describing tips and best practices for using it. Build and quality tooling Local builds can be reproduced in a container: the documented command installs build tooling, Ruby and Bundler, then runs bundle install and jekyll build with output directed to the public directory. Linting is handled by MegaLinter, which can be run through its runner with a codebase-wide validation flag. Two GitHub Actions workflows are surfaced via status badges: one for linting the code base and one for building and deploying to GitHub Pages. The project also displays OpenSSF Scorecard and OpenSSF Best Practices badges, indicating participation in those supply-chain and project-health programmes. Testing conventions The README documents a container-based test command that installs utilities and Docker, sets up the mise tool manager with additional plugins and tasks, and then invokes a post-creation task. A convention around fenced code blocks controls what happens in the post-test workflow: code blocks marked as bash are executed during the creation phase, blocks marked as sh are executed during the clean-up or destroy phase, and blocks marked as shell are only displayed on the rendered pages and never executed. This lets tutorial-style posts double as runnable scenarios. Notes and limits The repository is a website and content project rather than a reusable application or library. Its documented capabilities are limited to static site generation, content categorisation, container-based builds, linter configuration, CI workflows and convention-driven command execution inside posts.