MWmwhite·Feb 3, 2016
Obligatory link to my Markdown resume which converts to PDF (via LaTeX) and HTML using Pandoc:
https://github.com/mwhite/resume
In Show HN: Simple and elegant Markdown-based resumesmwhite
resume
HISTORICAL RECORD2011–2016
mwhite / resume · Not publicly available
resume
Discover this repository through its Hacker News conversations.
2Distinct people
4Mentions
0Explicit recommenders
What to know before exploring
What it is
A public description has not been verified.
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year4 dated mentions
Observed mentions: 2011-11-03 00:48:43 UTC to 2016-02-03 22:34:49 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2011 | 2011-01-01 00:00:00 UTC | 2012-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2012 | 2012-01-01 00:00:00 UTC | 2013-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2013 | 2013-01-01 00:00:00 UTC | 2014-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesCoincidentally I was experimenting with LaTeX for writing my resume today, so this caught my eye.
In the screenshots, I see the same problem that I was facing with an [offline tool][1]:
There are too many hyphens all over the place! For example in this screenshot:
https://www.cvsintellect.com/img/home/sample-resumes/Classic...
... you can see "Devel-oped" "function-ality" "con-version" "expo-sure" "communi-cations"
Most other word processors can justify text without too much hyphenation. The TeX system seems to work differently (at least by default).
[1] https://github.com/mwhite/resume
In Free online resume creator based on LaTeXI prefer Markdown. It allows you to separate content and form, and you can easily output to basically any format using pandoc.
https://github.com/mwhite/resume
In Writing a CV in LaTeXNot bad, a nice simple hosted resume solution. I'm not a designer but it seems to me that the visual distinction achieved by the indentation on the left side of resume items could be improved a bit. It all seems kind of mashed together and somehow hard on the eyes.
As mentioned in another comment, http://re.vu is a totally different approach that attempts to enable slick display of a ton of information.
I still prefer what I currently use: Markdown + pandoc + github + bit.ly. That gives me the following:
1. Version control, backup and hosting from Github.
2. Plain text for posting in the occasional web form or whenever else I might need a plain text resume.
3. One-command conversion to PDF using pandoc with a very simple LaTeX header (which I could automate with git hooks if I was lazy enough).
4. One-command conversion to HTML using p
Read the rest
andoc, with a CSS file. I can jazz up the CSS and then print to PDF from my browser if I ever want something prettier.
5. Readable URLs using bit.ly that point to the latest version, for which I can easily view analytics by appending +, including country and referrer: http://bit.ly/mwhiteresume and http://bit.ly/mwhiteresumepdf
6. The awesomeness that is Github's Markdown style.
http://github.com/mwhite/resume