Indeed, it's evolved over time as I've needed more from it but the UX has wound up pretty awful. Adding a personal statement for example involves finding and pressing the oh-so-very-intuitive "add block" button at the bottom of the edit page.
For reference you can drag and drop any of the sections to reorder them, and most of the fields will happily accept Markdown.
Any feedback appreciated for next time I have a weekend spare :)
Pretty cool. Just a suggestion, why not display a few more rows for the stack options instead of a single row. It would be pretty neat if I can just click through the stacks that I knew instead of figuring what I probably left out.
Very cool project! The Latex version is based on the awesome modern cv template. If you prefer not to install the massive TeX package on your computer you can use the online apps like ShareLatex[0] and WriteLatex[1] both of which have templates that you can use to get a CV ready in no time.
As someone who has read hundreds of resumes filling positions, I've got to admit this is not a great template, IMHO. I don't (and shouldn't) care about a candidate's picture/logo and the horizontal rules just burn more space. This strikes me as a template for someone that is trying to take up space.
Frankly, the hackerb.io template is something I'd prefer to read.
While this seems like a nice exercise, I wonder how much things would break when the JSON is slightly "off" in terms of the schema, which seems to be very ad-hoc.
And with so many standards for resume schemas going around, I fear this will end up in a http://xkcd.com/927/ situation.
Perhaps this exercise could've been more interesting if it were some nifty XSLT that took HR-XML and made HTML (preferably with tags that followed the hResume format) and LaTeX? The "XML Résumé library" http://xmlresume.sourceforge.net/ seems to be abandoned, but it is still worth to take a look.
I kind of thought JSON is [essentially] HR-XML. lol. But then again, I have not heard of Human Readable XML, and sort of chuckled at the thought of “HR” meaning human readable (until I googled it — __face–palm__).
This is particularly amusing because 6 or so months ago I had to write a résumé as part of a "career unit" in my Engish class. I was fed up with the whole thing -- what we had been taught seemed totally obvious to me and I was pretty much only doing busy work -- so I decided to write mine in JSON, and its schema happened to look pretty similar to this one's! The best part of the story, however, is that my awesome English teacher (only doing the unit because of the district), understanding of my interest in tech, loved it and thought it was clever and so gave me full points on it.
Was in a similar situation with a less happy ending. I had already generated a LaTeX résumé starting from around 2010. However, this year in an English course, I had to rewrite one in Microsoft Word, which was the only method accepted.
Hmmm, should be using en-dashes (--) not hyphens (-) for date-ranges, uses mathematical superscripting $22^nd$ and so gets incorrect fonts and spacing of the superscript, .... It's a CV, write it (carefully) in LaTeX!
Mine only does Latex, has a slightly similar layout... To be honest I don't think that a HTML version of a 2-page, non-interactive resume is needed. And since I know Latex I prefer to have the full toolset of Latex at my fingertips in order to make it stand out (babel+hyphen, vspacing, href links, content flow control).
Here the link, I hooks you up to a rendered version, and pointers for a zero-install-get-started-now-for-free route of getting your own print-perfect PDF using the awesome ShareLatex web app.
This is a great idea! I did something similar which stripped the text out of my tex resume, but I like the idea of writing it in the intermediate format and then converting to whatever you want.
While on my most recent job search, I found that a lot of places want a copy/pasted version of your resume in a plain text box. It would be nice if this printed out a pretty plaintext version of your resume too for boxes like this.
I find it interesting how techies rather make a complex generator than just open up an editor, write their resume and be done with the whole thing. Personally I find the JSON structure much harder to read than just use MD in Sublime or even something as trivial as using Word. By saying this, I don't try to bash on the creator, just acknowledge the phenomenon. Cool idea.
I'm not sure why you'd want to start with json or yaml. Seems like you'd want to start with a document, not a datastore. A datastore would tend to being opinionated and inflexible. What happens when my resume doesn't match a prescribed format? Or what about other documents beyond resumes? And whats with the star bullets? Why mix style with data? What if I want hearts instead of stars?
I only mention this cause I'm working on something similar for my resume. I start with markdown and output pdf, html, etc.
What happens when the code you wrote to parse markdown is unable to understand your new fangled resume material? Then markdown is just as much a datastore as json. The problem is not in json or markdown. It is in the code: your code must be able to understand all reasonable resume material.
Whenever need to write docs, such as resume, posts, wiki, and many others, I prefer markdown. I make a chrome extension to read and write markdown file inside browser, and it is easy to convert to pdf. It is available here:
https://chrome.google.com/webstore/detail/markview/iaddkimmo...
This is very subjective, but I think your resume would look better if you made the background white and set the line-height to about 1.5em on the whole body. You might even play with removing the list bullets and padding (list-style:none, padding-left:0px). If you try this, I would be interested to hear if you think it looks better or worse.
That would be really cool. But that requires an understanding of what u have to offer and what they REALLY need.... I mean humans have issues with this problem, its gonna be tougher to write a program that does it
http://hackerb.io/cantlin.pdf
In MD:
http://hackerb.io/cantlin.md
In JSON:
http://hackerb.io/cantlin.json
You can generate a decent chunk of the content from LinkedIn/GitHub too :)
http://hackerb.io/