Skip to content

About

My blog

Resources

Stars

0 stars

Watchers

1 watching

Forks

Repository files navigation

arphox.github.io

My blog, built with Jekyll and the minima theme, hosted on GitHub Pages at https://arphox.github.io.

The Sass files in _sass/ and assets/main.scss are local overrides of Minima 2.5.2: no newer official release fixed its Sass deprecations when they were migrated. They use modern Sass APIs while preserving the generated CSS. When upgrading Minima, check whether these overrides can be removed or need updating.

The blog, CV and Local Tools follow the OS color preference using CSS only. Shared light/dark colors and syntax highlighting live in _sass/_theme.scss; tool styles use the same color variables. Dark colors apply only to screens, so printing (including the generated CV PDF) keeps the light palette.

Link previews use the shared static assets/social-card.jpg (1200 × 630), with assets/social-card.svg as its editable source. The image default in _config.yml is inherited by new posts and tools; their existing titles and descriptions supply the preview text. Local Tools use tool-social-meta.html without inline scripts to preserve their CSP.

Running locally

Requires Ruby (see .ruby-version) and Bundler. CI reads the same Ruby version file. The committed Gemfile.lock includes Windows and Linux platforms so local development and deployment use the same gem versions.

bundle install
bundle exec jekyll serve

Then open http://localhost:4000. On Windows, run _start_local_hosting.bat; it installs missing gems and RubyInstaller build tools when needed. Refresh the browser manually after changes.

Writing a post

Add a Markdown file to _posts/ named YYYY-MM-DD-title.md with front matter:

---
layout: post
title: "Your title"
date: 2026-01-01 09:00:00 +0100
---

The CV page (/cv/)

The CV lives at https://arphox.github.io/cv/ and is rendered at build time from its Markdown source — no runtime fetching, no client-side rendering.

  • assets/cv.md is not the source of truth — it's a published copy. The canonical version is maintained separately and copied in here; this repo is just the publish surface that renders it and serves the "Download Markdown".
  • PDF download: .github/workflows/pages.yml prints the built /cv/ page to _site/assets/cv.pdf with headless Chrome during the deploy, then validates its text. The PDF ships with the deploy artifact and is never committed, so it can't drift from cv.md.
  • Locally, the PDF is not generated — the "Download PDF" button only works on the deployed site. Use bundle exec jekyll serve to check the page render and Markdown download; verify the PDF on the live site after a deploy.

Note: cv.md is passed through Liquid when rendered, so avoid literal {{ }} / {% %} in the CV text (or escape them). The raw Markdown download is a verbatim copy and is unaffected.

Local Tools (/local-tools/)

Browser-only tools. See local-tools/README.md for development guidelines.

Deployment

Every push to master is built and deployed automatically by the GitHub Actions workflow with the locked Jekyll version.

Updating dependencies

Run bundle update --all, then bundle exec jekyll build and review changes to Gemfile.lock. If adding a deployment platform, use bundle lock --add-platform to keep the lockfile portable. GitHub Actions are pinned to release commit hashes; update the hash and version comment together after checking the upstream release. On Windows, use ridk exec bundle update --all when gems need native compilation.

About

My blog

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages