Alternatively, tack `/export?format=pdf` to the end of a google doc. It generates and displays the PDF version on the fly. i.e. <a href="https://docs.google.com/document/d/______/export?format=pdf" rel="nofollow">https://docs.google.com/document/d/______/export?format=pdf</a>
Built my <a href="https://soft-wa.re/resume" rel="nofollow">https://soft-wa.re/resume</a> with <a href="https://jsonresume.org" rel="nofollow">https://jsonresume.org</a><p>I'm pretty happy with it. It needs some more work, and I would like to do some preprocessing to tailor it based on the job. So maybe if you go to <a href="https://soft-wa.re/resume?tech=python" rel="nofollow">https://soft-wa.re/resume?tech=python</a> you get my resume filtered for any python work.<p>I've also been thinking I could host for people. So maybe I host Alices.soft-wa.re/resume or Bobs.soft-wa.re/resume. Any interest in this?
My website's print version is a CV, so you can just print it to a PDF: <a href="https://notpushk.in/" rel="nofollow">https://notpushk.in/</a><p>I've also had Netlify generate a PDF of each build using wkhtmltopdf, but there was some issue with fonts which I didn't figure out at the time (it doesn't load them: <a href="https://notpushk.in/cv.pdf" rel="nofollow">https://notpushk.in/cv.pdf</a>) and can't had a chance to come back and solve it once and for all.
I have a similar system that solely uses a github actions workflow to build a jsonresume file into a latex pdf. I can make different branches for different roles and have a link that always directs people to the most up to date version of the resume. Plus, anybody can fork it and use it with their own resume without need for extra configuration or services. <a href="https://github.com/lukew3/resume">https://github.com/lukew3/resume</a>
I generate my website <a href="https://thomasahle.com" rel="nofollow">https://thomasahle.com</a> with a static Jinja template. Whenever I update it, it also generates a new resume and uploads that. Very convenient.
I have built something similar for myself, which I'll hopefully publish some day. The stack is YAML, Sveltekit, Puppeteer. Overall YAML makes adding content very easy and I can adapt the schema to suit my needs if I need to.