\\documentclass[11pt]{article}

\\usepackage{palatino}
\\usepackage[utf8]{inputenc}
\\usepackage[margin=2.54cm]{geometry}
\\usepackage{setspace}
\\usepackage{datetime}

\\title{On manuscript workflows and \\LaTeX}
\\author{Chester Balingit (\\texttt{[email protected]})}
\\date{\\today, \\currenttime}

\\begin{document}
\\maketitle
\\onehalfspacing

\\section*{Introduction}
We need to stop using \\LaTeX for text editing but rather have it as a typesetting tool: we put in text we've already written, and out goes a beautifully-typeset document for our enjoyment.

Considering that a lot of researchers in my field would get angry at me with this statement, I'd instead suggest a workflow that aligns with this belief:

\\begin{itemize}
	\\item Writing/Drafting Phase: create a Google Docs or Microsoft Word online document, then share that link with your coauthors. \\textit{Do not} use a specific document template or formatting other than what's necessary. You can change the layout/fonts according to taste but remember that the focus is on readability. 

Imagine writing an outline and few blocks of text. Then you send it over to your coauthors and discuss manuscript content while live-editing the document. Make sure that when anyone starts adding or altering text in the document, everything remains consistent.

	\\item Proofreading Phase: this should still be done in the online document, but now you start turning on those nice reviewing tools and change tracking.
\\end{itemize}

\\section*{Frequently-Asked Questions (aka Complaints)}
Here's some snarky questions that you might  have come up with as you read through my suggested approach:

Q: \\textit{I'm already deep into the latex workflow! Why should I change it now?}

A: This is not about making writing easy for you, but making it easy for your coauthors. 

Q: \\textit{Writing symbols and equations with those word processors are hard! With latex I can just copy-paste everything, and my fancy Greek variables that represent totally relevant parameters shows up nicely in the document.}

A: 

Q: \\textit{Why not Markdown?}

A: Anything that demands further learning from any of the authors with regards to writing is just a waste of time. You might be writing a paper were everyone is as tech-savvy as you are but building a workflow around Markdown/latex means not only you have to teach everyone the workflow (just for this particular document!) but also justify why using this workflow is worth it.

Q: \\textit{But not only neither Google Docs nor Microsoft Word are free, I also don't want to rely on these big corporations with my work!}

A: 

\\section*{\\textit{Author Remarks}}
I don't know in what form you'll be able to read this text, but I assure you that I wrote the draft in latex first using the iPad app \\textit{Texpad}. Ironically, I also wrote this while mulling over touching my working manuscripts in Overleaf: I'm procrastinating by writing about an approach which minimizes procrastination from ``workflow friction".

\\end{document}