Four Strategies to Integrate Markdown into a Word-Centric Workplace

Introduction How do you handle documentation at work? If you're a Qiita user, you might frequently use Markdown. At my workplace, the norm was to write documents in Word. Recently, we've switched to using Markdown, and I'd like to share what steps we took in this process. Note: This article does not intend to criticize Microsoft Word or claim Markdown is superior. The workplace described is a software engineering department dealing with technical documents. Please read with this context in mind. Strategy 1: Taking Meeting Minutes in Markdown Initially, our workplace didn't have a habit of recording meeting minutes. I started taking notes on my own and distributing them post-meeting, which was well-received, leading me to continue as the meeting scribe. I initially used plain text files but later switched to Markdown. When distributing these notes, I included: The file extension is .md, but it’s just a text file. You can view it with your preferred text editor. However, if you use a Mar