If I’m hiring a web developer and you give me a `resume.html` you’d best believe I’m viewing source on that.
This is a high-risk high-reward game, because if it’s clean you’ll get bonus points, but if there’s unnecessary cruft (as defined by me) you’ll loose points.
For example, while this is pretty clean code, I’m currently on my phone and getting horizontal scroll bars. For a text based site like this resume that shouldn’t happen, and perhaps unfairly, that’s going to weigh heavily against the other good work OP has done.
`grid-template-columns: max-content 1fr;` is preventing the text from wrapping in `header` elements. Should be a simple fix, but it'd definitely loose some points from me.
Yep. I revisited mine I made in 2015 and it still renders just fine. Haven't touched it in years. No build steps, no external tooling aside from a text editor and a browser.
Print to PDF if you need to via the browser, and you're good to go!
Author here—This is fair criticism, but _for me_, the overhead of a simple static site generator is worth all the benefits I get from being able to e.g., separate my data from my styles and so on.
I mean I personally would use a static site generator too, but objectively speaking: for a single page (no navigation, not printed page)... It really is overkill
This is how my resume was (maybe still is, I haven’t looked I years).
One thing I did that I like was after the most recent jobs, the older and less relevant ones were faded a bit. A hover would make them dark and easier to read. When printing a PDF, only the darker more recent ones would print. This let me keep a full record in a single file (mostly for my own benefit), while still being able to quickly and easily print out a single page version.
You could have structured data as json etc within that html, and some Javascript that renders that onto final html. Than add a button (or a URL argument, or print action) that returns final html (including all your Javascript). That way you only ever need to update your structured data while never needing to edit the html itself. You could theoretically even add some interface to update the resume. I am thinking tiddlywiki but for the CV.
May be that's what you are saying in your comment already.
It will be self
that's what I did, but pandoc massacred my boy on the first pass, several passes later it was a bit better with just the right args. I got better results just using brave and adjusting the margins by hand for printing to pdf. I started with markdown but it was simply too limiting for anything that involved alignment (left, right, center) without html, and figure if I have to do that, just use html.
I've been using LaTeX for mine for years and never looked back. I have it setup in such a way that I just comment or uncomment a few lins at the start and can easily include or exclude, or adjust, types of skills, work experience, length, etc.
Always produces a nice, easy to clean minimal pdf that has some protections against recruiters trying to copy and paste and change things.
Mine is also in LaTeX. Every 3-5 years I get a nice reminder of the nightmare that is cobbling together a fully functional LaTeX dev environment to work on it again.
I agree, but it can be useful to produce html and plain text versions of your resume and cover letter too. Per-job customization, and adding custom metadata for cover letters, is also useful.
What worked for me was I creating a simple python script that uses json files with custom data as input, and uses mako templates to create latex, html, and text output.
I've never needed an html version honestly. I do have it setup to produce a text version for copying and pasting into job applications that don't support file upload. Or worse, that want you to paste the same information and then upload your resume anyway.
Hi, I have a latex resume/cv too and am curious about "some protections against recruiters trying to copy and paste and change things". What does that mean?
Honestly I don't recall exactly because it's been so long since I set it up. I think I did something to make it hard to export/convert to doc/docx, and maybe even prevent or make it hard to copy test for certain blocks. It was just using some tracks for things you can do with the pdf format, but I don't have more information at the moment.
I'll try and dig in later and see what I actually did.
Unpopular opinion: every time I see anything made with LaTeX, it makes my eyes bleed. While it might be great for editing, I find it to be a pain to read. I really wish academic papers (and everything else it is used for) would be written with a tool that generate at least a bit more readable output...
TeX output was optimized for printing, so it looks better on paper than on screen. (IMHO, it looks excellent on paper). Try to zoom in, for better experience, or view generated PDF on eInk display.
I've kept mine in a single file HTML with some CSS for years too. After toying with more complicated solutions, decided to stick with the KISS principle.
It's at https://github.com/astangl/alexstangl-resume if anyone wants to take a look.
I made an Elevnty website for my partner's business. It was a great experience. It worked well and was easy to code.
After I came back to update it 3 years later by cloning the repo and running 'npm i' I got a bunch of errors. Working through the upgrade process failed. I couldn't get it running again.
I dumped the HTML from the live site, changed that directly, and just uploaded that to S3 to host it. I don't think I'd bother with Elevnty again. It's great for making a new site, but the long term maintainability isn't there. To be fair, this is on me. I should have done more to keep it running, or pinned the dependencies, or something.
Am i the only lunatic that has build his resume in troff? I mean, its simple, available in every *nix and absolutely ideal for such an simple document.
This reminds me of writing my resume using nroff[0] when I was a junior engineer years ago. Times have changed but I get why he did it, even though I doubt I would have chosen the same tooling.
Readit News
This is a high-risk high-reward game, because if it’s clean you’ll get bonus points, but if there’s unnecessary cruft (as defined by me) you’ll loose points.
For example, while this is pretty clean code, I’m currently on my phone and getting horizontal scroll bars. For a text based site like this resume that shouldn’t happen, and perhaps unfairly, that’s going to weigh heavily against the other good work OP has done.
Print to PDF if you need to via the browser, and you're good to go!
https://github.com/bschwind/resume
I mean I personally would use a static site generator too, but objectively speaking: for a single page (no navigation, not printed page)... It really is overkill
One thing I did that I like was after the most recent jobs, the older and less relevant ones were faded a bit. A hover would make them dark and easier to read. When printing a PDF, only the darker more recent ones would print. This let me keep a full record in a single file (mostly for my own benefit), while still being able to quickly and easily print out a single page version.
You could have structured data as json etc within that html, and some Javascript that renders that onto final html. Than add a button (or a URL argument, or print action) that returns final html (including all your Javascript). That way you only ever need to update your structured data while never needing to edit the html itself. You could theoretically even add some interface to update the resume. I am thinking tiddlywiki but for the CV.
May be that's what you are saying in your comment already. It will be self
Always produces a nice, easy to clean minimal pdf that has some protections against recruiters trying to copy and paste and change things.
What worked for me was I creating a simple python script that uses json files with custom data as input, and uses mako templates to create latex, html, and text output.
I'll try and dig in later and see what I actually did.
After I came back to update it 3 years later by cloning the repo and running 'npm i' I got a bunch of errors. Working through the upgrade process failed. I couldn't get it running again.
I dumped the HTML from the live site, changed that directly, and just uploaded that to S3 to host it. I don't think I'd bother with Elevnty again. It's great for making a new site, but the long term maintainability isn't there. To be fair, this is on me. I should have done more to keep it running, or pinned the dependencies, or something.
0 - https://en.wikipedia.org/wiki/Nroff