Skill #10: Implementing Single-Source Authoring

📣 Special announcement: The Not-Boring Tech Writer team (Kate and Chad) will be at Write the Docs Portland in May. Thanks to KnowledgeOwl's sponsorship, they’ll be wearing KnowledgeOwl and The Not-Boring Tech Writer t-shirts and giving out The Not-Boring Tech Writer stickers. If you're attending WTD Portland this year, please say hi to Kate and Chad, let them know what you think of the show, and swing by the conference swag table to grab some free stickers so you can flaunt your not-boring tech writer status with the world!_____________________________________________Paul Stoecklein knows documentation: As Documentation Manager at MadCap – the industry leader in documentation software – and longtime technical writer, Paul understands what does and does not work for documentation teams.A methodology that Paul believes is essential for documentation teams is single-source authoring: to use a single-source of documentation for multiple outputs.In this episode, Paul shares how you can implement single-source authoring in your organization, including:how single-source authoring can add value to your organization.why all documentation teams should consider single-source authoring.what tools and processes can help you succeed.Show Notes: MadCap SoftwareMadCap FlareDoc-To-HelpMadCap CaptureMadCap MimicFlare’s Online Help