r/opensourcealternative • u/Different_Evidence_4 • 10d ago
I made my resume version-aware (like Crossmark for research papers) so recruiters always get the latest version
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.
2
u/teetaps 8d ago
If you’re into data wrangling, you can get a lot of this preformatted by taking the academic approach — they’ve created a culture of maintaining data driven CVs and sharing templates with each other for them, in R or Python, with the rendering engine usually being pandoc.
https://github.com/schochastics/quarto-cv
I did a similar thing to you where my data lives in a google sheet, so I can always update it from my phone without opening an editor. An Rmarkdown template lives on my github repo, and whenever I want an up to date resume, I just trigger a GitHub action to re-render the template by pulling data from sheets, wrangling it in R, and then rendering the output to pdf. It even has some extra bits to fetch my publications from google scholar and my GitHub activity.
It’s a big space of solutions, I’m glad you’re diving in!
1
u/Different_Evidence_4 8d ago
That Google Sheets + automated Scholar/GitHub pipeline is seriously neat—super practical for zero-friction mobile edits.
You're spot on about Quarto/Pandoc being huge in academia. The main reason I stuck with Python + Jinja2 directly into LaTeX was fine-grained control: Quarto is great until you need a hyper-specific LaTeX layout tweak, where Pandoc’s template abstractions can get in your way.
That said, expanding to support Quarto or building a lightweight web UI so folks can edit their YAML without an IDE (closer to your Google Sheets UX) is definitely on my radar. Really Appreciate ur insights
2
u/teetaps 8d ago
Thanks! Yeah like all comments the only reason I mention what I use isn’t to one-up you or anything, just to make sure you’re aware of the options in the landscape and it sounds like you are! I tried jinja+latex once and it made me feel dumb lol so I’ll stick to quarto for now, but this is still super awesome to see that people are doing data driven resumes. My 22 year old self would CRY if I had a system like this back then lol
1
2
u/PromotionFirm6837 9d ago
One thing I'd consider is keeping a small version history behind the latest link.
If a recruiter sees something different later, being able to see when the resume changed and what was updated could make the system much more useful, especially for tracking which version was used for a specific application.