HackMyResume is a dev-friendly, local-only Swiss Army knife for resumes and CVs
github.com
github.com
[0] https://github.com/hacksalot/HackMyResume/blob/master/assets...
Even back then there were plenty of Resume generators. What still haunts these tools is a too complex environment setup and unappealing template designs.
How often do you update your CV that you need an automated tool to do it? And why would you need it in 10 different formats?
I update mine once every 2-4 months or so, whenever I complete a project, earn a certification, take a course or work (professionally) with a new technology.
Having 10 different formats does sound a bit like overkill, but I don't think that is a reason that the OP would want to ignore or exclude any that users would find useful. Personally, I keep about 3-4 (linkedin, .doc, .pdf, .htm).
Web design is fundamentally different to print design, and your CV should show that you understand that. So you should be able to make a Word version save that to PDF, then re-write and redesign the content for the web page.
Further, this (really the underlying JSON resume schema) could be a great starting point for a fancier web-resume generator working from the same content.
I highly interactive web-based resume for a lawyer or accountant might seem silly in that community (and some of my lawyer/account friends agree).
It's certainly a step up from a docx but just not that great of a template based on the criteria I named.
It seems to me the template itself is the most important differentiating characteristic of a product like the OP. I understand it accepts custom templates, but that one above is the only sample I found.
Here's my own old-school resume with the DeCorte template: http://static.coshx.com/kopley_resume.pdf
BTW, do you have the base style for that uploaded somewhere?
Here's one: https://github.com/elizabrock/LaTeX-Resume
In unrelated uncreepy news, we are practically neighbors! One block over on Steiner.
Exporting to various formats is high on my list of todos. I'll definitely be looking closely at how it's implemented here.
You'll need early adoption by large employers such as big tech companies to governments for it to have potential to reach critical mass and make you become an acquisition target by Applicant Tracking System vendors.
The problem - poorly solved by Burning Glass, Daxtra, TextKernel, Sovren et al is converting documents applicants pass in to those formats.
I've used that for years. No problems, though the odd jobsite's commented on formatting, giving me an opportunity to explain the generator ;-)