I used Pandoc at a previous job when I got frustrated with writing documentation for our customer in OpenOffice. Instead, I started writing markdown and wrote

I used Pandoc at a previous job when I got frustrated with writing documentation for our customer in OpenOffice. Instead, I started writing markdown and wrote a script that used Pandoc to convert it to LaTeX, insert headers/footers and company logo etc, and finally used latexmk to output PDFs. This looked far more professional than the word documents we shipped previously. It also successfully separated content (markdown text files) from presentation (handled by script), making sure all PDFs had a consistent look. With documentation being just another buffer in emacs it was more often written/sketched when implementing, instead of being a task to do last when you had already run out of time. It is also much easier for developers to follow changes to the documentation in the version control system, and merges are a breeze instead of a time-sink.