Left Quotation MarkRight Quotation Mark
Bullet-Tripplesymbol-play
Photo of Swapnil Ogale

Swapnil Ogale

Technical Writer

iCreateDocs

@swapnilogalewww.linkedin.com/in/swapnilogale/

Swapnil is a Technical Writer with over 11 years of experience across a range of industries in Australia. He also moonlights (literally, working some US hours) on remote writing projects (using MadCap Flare), providing expertise on technical documentation for startups and niche organizations. Swapnil has been running an Australia-wide Flare User Group since 2014 and initiated the Write the Docs community meetups in Australia in 2016. He presents at technical meetups and conferences on various topics he has experienced as a technical writer.

Sessions Presented by Swapnil Ogale:

Monday, June 4

11:30 AM-12:25 PM

Estimate, Analyze, and Visualize: How We Turned Customers into Users (or Believers)

Track 4 MadCap Flare Case Study

In this real-world example, explore how Planifi, a software company building products for Architecture and Engineering (A/E) firms, worked with a technical writer remotely to migrate existing content from Adobe® RoboHelp® to MadCap Flare and then document their suite of project management tools targeted particularly at project managers and architects. Swapnil Ogale will look at how the documentation went from being field/screen level to task-based and how other content (hover image, videos, etc.) replaced and complemented text based on customer feedback. In addition, learn how this content was streamlined to be used for multiple purposes, such as product help, training, and customer support.

Tuesday, June 5

2:50-3:50 PM

What’s the Deal with Release Notes?

Track 1 Release Notes

Product managers swear by them, development managers are keen on producing them and quite so often your developers or engineers will help (grudgingly) craft them. Customers (or users), on the other hand, love to get a sneak peek of what has been fixed, improved or added in the newer version. Release notes are everywhere, be it a product or a process. They are quite often your first point of communication with customers eager to know what’s new or fixed in your product or process. In some instances, they also become the most frequently or commonly accessed content on your documentation site. In this presentation, we look at what makes for good release notes, how they help customers/users understand product or process changes, and how technical writers can help bring clarity and structure to release notes.