~/projects / resume-pipeline

Resume Pipeline

2026

• GitHub Actions
• YAML
• CI/CD
• Cloudflare Pages

overview

My resume is data, not a document. I edit one YAML file, push to GitHub, and a workflow builds the PDF and publishes it. This site and the PDF link always serve the latest version.

how it works

resume.yaml  ->  git push  ->  GitHub Actions builds PDF
                                      |
                       commit jimmy.wong.resume.pdf
                                      |
                  Cloudflare Pages deploys the site
                                      |
        jwong.org  +  resume.jwong.org (always the newest PDF)

why

• One source of truth: no copy-and-paste between a web page and a PDF.
• Every change is versioned in Git, so I can see exactly what changed and when.
• Publishing is hands-off: edit, push, done.

details

• [PDF tool used: e.g. headless Chrome, LaTeX, WeasyPrint.]
• [Anything tricky: fonts, page breaks, keeping the PDF text searchable for recruiters' ATS tools.]

Source code: github.com/jwong545/resume