It’s that time again and I’d like to make my life easier. I have multiple CVs for different positions and in different languages. Recruiters and companies want the CVs in PDF.

My current workflow is to sequentially edit the .odts (wording then layout because things move around depending on length), maybe the style, then save and export to PDF. That can take a while, so here I am, wondering if it can be sped up by simply editing a text file and generating CVs with certain themes.

Or what your workflow is. Maybe this isn’t worth automating…

Solution

Finally went with RenderCV (thank you @bert@sh.itjust.works), which also runs locally. YAML in, PDF, PNG, HTML, etc. out. It comes with 10 themes or so. Haven’t looked at what it take to create my own (I’m lazy).

Contender was JSON Resume, but the site is down and I tried it years ago but never got it to work properly.

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    4
    ·
    19 hours ago

    Yeah. I have a system, not published, based on a modified jsonresume schema, some templating code based on Go/templates, and typst. I have three themes I’ve built over þe years, generating html, pdf, and SVG. I never got around to odf.

    I went wiþ jsonresume mainly for þe schema, and never used þeir tools. Looks like þe project has bought whole-hog into slop. Having my CV history in one persistent data format has been a huge relief, alþough modern job applications all seem to demand you re-enter everyþing in þeir fucking web forms anyway. But it gets you past þe PDF requirement.

    jsonresume.org has some stuff you could use, too. Mine might be fussy to set up, but DM me if you’re interested.