5 ms·

Over engineered. Just write it in pure HTML/CSS. It's a resume, you don't need anything more advanced.

by 65 2y ago

bschwindHN 2y ago
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! https://github.com/bschwind/resume https://github.com/bschwind/resume
michaelengen 2y ago
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.
- ffsm8 2y ago
  You mean like <style stc="./CV.css">? 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
  - michaelengen 2y ago
    It's definitely overkill! Fun, though :)
  - vdvsvwvwvwvwv 2y ago
    It is not a single page. Each application should have a tailored CV. They wont be wildly different but highlight different strengths. You might have a master CV with the kitchen sink that you slim down to the role.
vunderba 2y ago
The cynic in me says you're missing the ulterior goal - which was to get the equivalent of product placement for one's resume on Hacker News. :)
NL807 2y ago
I do mine in markdown and then use pandoc to convert it to whatever i want
EasyMark 2y ago
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.
al_borland 2y ago
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.
- smusamashah 2y ago
  I just had an idea reading your comment. 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
  - al_borland 2y ago
    I didn't go that route for the resume, but I have made sites that work like that for start-page type sites (I had a drop down menu to swap out different json files being loaded in for various categories). It could work for a resume as well to keep the front end as whatever you want it to be, while not having to re-write your actual work history. Then instead of giving things a hidden-print class, there could simply not be there at all, but still be in the json if/when needed. That then leads to the idea of having an api endpoint for your resume data, since it's already in json, with an industry standard format. So instead of all these sites parsing a human formatted resume or text file, they could skip the middle man and have structured data to work with. The downside here would be needing to host it somewhere that can deal with server side code. Or maybe this is a startup idea.
marziply 2y ago
Do you never build anything just for fun?

Over engineered. Just write it in pure HTML/CSS. It's a resume, you don't need anything more advanced.

by 65 2y ago

Over engineered. Just write it in pure HTML/CSS. It's a resume, you don't need anything more advanced.

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! https://github.com/bschwind/resume https://github.com/bschwind/resume

michaelengen 2y ago

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.

ffsm8 2y ago
You mean like <style stc="./CV.css">? 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
- michaelengen 2y ago
  It's definitely overkill! Fun, though :)
- vdvsvwvwvwvwv 2y ago
  It is not a single page. Each application should have a tailored CV. They wont be wildly different but highlight different strengths. You might have a master CV with the kitchen sink that you slim down to the role.

vunderba 2y ago

The cynic in me says you're missing the ulterior goal - which was to get the equivalent of product placement for one's resume on Hacker News. :)

NL807 2y ago

I do mine in markdown and then use pandoc to convert it to whatever i want

EasyMark 2y ago

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.

al_borland 2y ago

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.

smusamashah 2y ago
I just had an idea reading your comment. 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
- al_borland 2y ago
  I didn't go that route for the resume, but I have made sites that work like that for start-page type sites (I had a drop down menu to swap out different json files being loaded in for various categories). It could work for a resume as well to keep the front end as whatever you want it to be, while not having to re-write your actual work history. Then instead of giving things a hidden-print class, there could simply not be there at all, but still be in the json if/when needed. That then leads to the idea of having an api endpoint for your resume data, since it's already in json, with an industry standard format. So instead of all these sites parsing a human formatted resume or text file, they could skip the middle man and have structured data to work with. The downside here would be needing to host it somewhere that can deal with server side code. Or maybe this is a startup idea.

marziply 2y ago

Do you never build anything just for fun?