Enlarge / In goes the sensible characters, out goes a document for which you almost always have to adjust the sharing permissions. (credit: Aurich Lawson | Getty Images)
The best time to truly implement the Markdown markup language into Google Docs was in the early 2010s, but yesterday was a pretty good time, too.
Google Docs was born from the conjoined features of a series of software company acquisitions (Writely, DocVerse, and QuickOffice), plus the remains of Google Wave, smooshed together into Drive by 2012. By that point, Markdown, a project of web writer John Gruber with input from data activist Aaron Swartz, had been solidified and gathering steam for about eight years. Then, for another decade or so, writing in Markdown and writing in Google Docs were two different things, joined together only through browser extensions or onerous import/export tools. An uncountable number of cloud-syncing, collaboration-friendly but Markdown-focused writing tools flourished in that chasm.
In early 2022, the first connecting plank was placed: Docs could “Automatically detect Markdown,” if you enabled it. This expanded the cursory support for numbered and unordered lists and checkboxes to the big items, like headlines, italics, bold, strikethrough, and links. You could write in Markdown in Docs, but you could not paste, nor could you import or export between Docs and Markdown styling.
Read 4 remaining paragraphs | Comments
