[vinceguidry]

YAML's a weird choice for this kind of application. I once explored different markup languages for maintaining my resume, ultimately just went back to using LibreOffice.

There's a temptation to use a structured, machine-readable formatting language for anything that has structure, because you might one day want to use machines to work on it.

But for an application like this, those times are the exceptions, most of the time, it's humans that are going to read and modify the text. It makes way more sense to use a human-oriented format and simply use a convention so that it's easy to use a tool to convert it when you need to. I see no reason why Markdown can't be used.

[Grishnakh]

I use LibreOffice for my resume too. However, I'm the only person who maintains my resume, so it works for me. For something that's going to be touched by a lot of different people, a text-based language is far better because you can diff the changes easily. Such tools exist for office documents within those programs, but they're clumsy and don't integrate with source control systems.

But otherwise, Markdown does seem like it'd be a better choice. Everyone's using it these days, it's simple, whereas YAML is obscure.