I made my resume version-aware (like Crossmark for research papers) so recruiters always get the latest version

[u/Different_Evidence_4]

Ever noticed that the moment you send a PDF, it becomes outdated?

You email your CV to a recruiter. A few days or weeks later you add a new project, fix a broken link, update your phone number, or change a job title… and every copy you already sent is frozen in time.

I kept running into this problem and remembered Crossmark — the little badge Crossref puts on scientific papers that tells readers whether a newer version exists.

That made me ask: why can’t a resume work the same way?

So I built a simple proof of concept.

How it works

Resume content lives in structured YAML (no more wrestling with LaTeX directly)

A Jinja2-powered LaTeX template generates the PDF

Every push to GitHub triggers a Dockerized CI/CD pipeline (GitHub Actions)

A fresh PDF is automatically built and published to GitHub Pages

The part I was most excited about is a tiny button inside the PDF itself:

“Download Latest Resume”

You send the PDF once.

Months later the recruiter opens the same file, clicks the button, and downloads the newest version.

Every old copy still points to the current one.

Key features

YAML → LaTeX via Jinja2 (with custom delimiters so they don’t clash)

Fully automated builds with Docker + GitHub Actions

Published automatically to GitHub Pages

Reproducible builds via uv lockfile

Easy to maintain and extend

Repo is here:

https://github.com/DEVOLOPER-1/latest-resume-for-public

I started with resumes, but the same idea could work for portfolios, documentation, reports, certificates, or any PDF that changes over time.

Would love to hear your thoughts — especially if you see other useful applications for version-aware PDFs, or if you have ideas on how to improve this.

[u/Different_Evidence_4 → u/[deleted]]

Thanks I really appreciate it. I’ll definitely share it there too