16 comments

[ 3.7 ms ] story [ 19.5 ms ] thread
(comment deleted)
My website's print version is a CV, so you can just print it to a PDF: https://notpushk.in/

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: https://notpushk.in/cv.pdf) and can't had a chance to come back and solve it once and for all.

You can use chrome with '--headless --print-to-pdf' instead of wkhtmltopdf, it worked better when I last looked into this around 2017-2018. Needed to generate a consistent pdf and couldn't rely on the users browser because they might render slightly differently depending on the browser.

Instead I ran a "microservice" that just took html and generated PDF's using chrome, it worked pretty well.

Mine too, very convenient. I use hidden elements to present summaries so the whole thing fits in a page. https://kroltan.me
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. https://github.com/lukew3/resume
(comment deleted)
(comment deleted)
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.
Are these resumes ATS compliant? A problem I have right now is my current resume generating technique does not produce very good ATS compliant resume.
I generate my website https://thomasahle.com with a static Jinja template. Whenever I update it, it also generates a new resume and uploads that. Very convenient.