The Pros and Cons of Using Markdown for Technical Documentation (Part 2)

Join us for part two of our discussion about the pros and cons of technical documentation shops using Markdown, a lightweight markup language with plain-text formatting syntax that is designed to be converted to HTML and other formats using markup conventions. We'll discuss Markdown's pros, cons, strengths, and limitations in creating tech docs. We'll also address misconceptions about its adoption, its value, and its drawbacks. Additionally, we'll explore the time writers spend on tooling versus content creation to maintain the publishing pipeline. Our panelists will share their views, personal experiences, and anecdotes. Come prepared to ask questions. Panelists: — Knut Melvær, Head of Development Community and Education at Sanity. Knut manages Sanity.io’s developer community and works to build developer relations and support teams. — Peter Conrad is an author, content designer, and artist with a knack for the technical. He's published several books, including 'Markdown Dreams,' 'Git Doesn't Have to Be Hard.' . — Cris Perez is a technical writer, content strategist, and developer. With over 25 years of corporate experience in high tech, Cris combines his background in technical communication, computer science, and translation to create content solutions that empower customers to make the best use of technology. Can’t make it? Register, and we’ll send you a link you can use to watch a recording when it’s convenient for you. Coffee and Content is brought to you by The Content Wrangler and is sponsored by Heretto, a powerful component content management system (CCMS) platform to deploy help and API documentation in a single portal designed to delight your customers.