Oh man, we are kindred spirits.

I also feel like there's no point in making a CV in HTML for my website, if I'm going to re-make it in PDF for all the old school application processes out there.

My solution was simply to keep the online CV as simple as possible, so it still looked good in PDF. But it's far from perfect.

▲

beej71 6 hours ago | parent | next [-]

I wrote two xsl stylesheets and then encoded my resume in xml.

I know what you're thinking: "Ok genxer", but hear me out. :)

The two stylesheets produce HTML and Typst code. And so I get the exact render that I want.

(It actually goes further, making a CV and a resume from the same xml source, rearranging sections and sorting appropriately.)

Xml and xsl are quite dated, but this really does seem to be a good use case for data/presentation separation.

But really my dream is for print css (or something) to finally be implemented.

	▲	mxuribe 5 hours ago \| parent [-]
		I remember leveraging xml and xslt for doing the exact thing for my resume! This was quite some time ago, when xml was king. So, as a way to both unify my generation for my resume but more importantly learn more about xml, xslt, i created what sounds like a similar pipeline to yours. It felt really cool, and i learned about xslt - which to this day i'm impressed by. But, over the years as xml, xslt seem to have waned, plus i never got to use such skills at any of my jobs, and finally employers just wanted a Word doc, not a PDF...then i just stopped using my setup. Nowadays i simply keep a local copy of an .ODT file, and export to word or PDF, or whatever format an employer or recruiter asks for...and like 99.999% of the time its a Word doc. But, back then, it certainly as fun learning that stuff!

▲

etcetcetcetceta 6 hours ago | parent | prev [-]

I think you can generate html from latex, I use latex for my CV and render it as a pdf for circulation.