how it's built

A portfolio should show how I work, so this site is a small production system: everything is in Git, every change goes through a pipeline, and the status is public. Click a step to see what it does.

live status → source →

Write

Posts are Markdown files and the profile data is JSON, all in one Git repo. I can edit them locally, on github.com, or in the Pages CMS web UI. Every save is a commit.

Write. Posts are Markdown files and the profile data is JSON, all in one Git repo. I can edit them locally, on github.com, or in the Pages CMS web UI. Every save is a commit.

Git repo. The single source of truth. A push to main starts the pipeline. There are no servers and no database to look after.

Build. GitHub Actions installs dependencies and runs `astro check` and `astro build`. The output is plain static HTML, CSS and a little JavaScript for the interactive parts.

Generate. A headless Chromium renders the resume page into PDF files and renders social preview cards into PNG images, so they always match the current content.

Quality gates. A separate workflow checks for broken links and runs Lighthouse for performance, accessibility and SEO. Dependabot opens pull requests for outdated dependencies.

Deploy. The build output is published to GitHub Pages, served over HTTPS from a CDN. The whole pipeline takes about a minute.

Live. The site you are on. Comments run on GitHub Discussions through giscus, and the status page reads the public GitHub API live in your browser.

stack

Framework: Astro (static output)
Hosting: GitHub Pages
CI/CD: GitHub Actions
Content: Markdown + JSON, edited with Pages CMS
Comments: giscus on GitHub Discussions
PDF and previews: Headless Chromium in CI
Quality: astro check, Lighthouse CI, link checker, Dependabot