4 ms·
I have an elaborate set of scripts cobbled together to feed and operate resume-cli What I glued together let's me do this: - Write independent versions of eac
by 97-109-107 5y ago
I have an elaborate set of scripts cobbled together to feed and operate resume-cli
What I glued together let's me do this:
- Write independent versions of each partial of the resume (introduction, experience, skills, etc.) in discrete files. These are JSON files, with seperate versions tailored for different profiles, ie. "introduction (consulting).json", "introduction (ex-founder).json", ...
- Assemble selected json files to dynamically generate a merged version under a specif codename (usually company name or profile type)
- Live preview the assembled version
- Archive a specific merged version using that codename as a complete and static json
- Export as pdf, rename, upload html version and open a preview
Motivation
In essence - parts of my resume progress in a straight line infrequently, while other need to be re-written for different positions and are single-purpose. I had a hard time writing and rewriting different versions of the resume and keeping track of versions, so I decided to divide the content into partials.
I'm skipping the presentation layer, as the PDF export and theming is a seperate topic, particularly problematic on the intersection of HTML and PDF rendering.
- DamianEscobedo 5y agoOh, wow, that's cool, do you have this in a public repository?
- 97-109-107 5y agoI don't, but if you really think you'd need it, I can wrap it up and share. Caveats - it relies on resume-cli to actually generate the resume and it badly glued together. If you think you still could use it, let me know