f523fa986c4b14c97796640c70f92e16e5c68cb8
My Gatsby Deployment pipeline / build-and-deploy (push) Successful in 3m42s
Make the portrait smaller (200px) and tighten the hero columns. Remove the "Open to new work" status and neutralise the contact copy so nothing reads as job-seeking; show a plain location in the top bar instead. Deploy/tooling: drop the unneeded `--force` from the install (verified a clean --legacy-peer-deps install + gatsby build both pass). Replace gatsby-plugin-offline with gatsby-plugin-remove-serviceworker to retire the service worker (fixes stale-cache-after-deploy and removes the workbox deprecation). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
thiessen.io
Personal site of Dennis Thiessen — Staff Data, Analytics & AI Engineer (Bern, Switzerland).
Built with Gatsby 5 and React 18. Single-page, Swiss-minimal design; styles are plain CSS in src/assets/style.css (no preprocessor).
Develop
npm install --legacy-peer-deps
npx gatsby develop # http://localhost:8000
Build
npx gatsby build # output in ./public
Use Node 20 (see .nvmrc).
Deploy
Pushing to master triggers the Gitea Actions workflow in
.gitea/workflows/workflow.yaml, which builds the site and rsyncs public/
to the web server over SSH. It relies on these repository secrets:
SSH_PRIVATE_KEY, SSH_KNOWN_HOSTS, DEPLOY_USER, DEPLOY_HOST, DEPLOY_PATH.
Languages
JavaScript
53.5%
CSS
46.5%