The Pros and Cons of Adopting Markdown for Technical Documentation (Part 3)

Join us for part three of our discussion about the pros and cons of tech docs 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. And, we'll explore the time writers spend on tooling versus content creation to maintain the publishing pipeline. Panelists: Peggy Sanchez, Senior Technical Publications Manager at Cray, transforms content management, drives efficiency, productivity, and team growth through process improvement. Peggy has achieved a 60% production increase, a 25% reduction in carbon footprint, and consistent on-time deliverables. She excels in building supportive, high-functioning teams and implementing component content management systems, engaging stakeholders, and addressing pain points to foster collaboration and success. Manny Silva, Head of Documentation at Skyflow, excels in technical writing, engineering, and developer experience. He leads Docs and UXW, created the Docs as Tests strategy, and maintains the Doc Detective framework. Passionate about intuitive and scalable solutions, Manny also explores AI development and experimentation. Mark Wentowski is an API Documentation Specialist with over 12 years of experience producing global, web-based, developer-to-developer documentation for web services, libraries, and other software products. 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.