Left Quotation MarkRight Quotation Mark
Bullet-Tripple
Photo of Jayna Locke

Jayna Locke

Content Strategist, Digi International

@jaynalockewww.linkedin.com/in/jaynalocke

Jayna Locke is a content strategist with a background in technical communications and digital marketing. Her experience includes content strategy, SEO work, user experience analysis, project management, web development, copy writing, technical writing, team building and technical publications team management. Her team began testing MadCap Flare for some content in 2013, and moved to full adoption in 2015.

MadWorld 2017 Sessions Presented by Jayna Locke:

Monday, April 3

2:35-3:30 PM

Choosing MadCap Flare Over DITA, But Getting the Best of Both Worlds

Track 3 DITA • MadCap Flare • Case Study

In this presentation, learn how our harrowing 11th hour selection of MadCap Flare over the Darwin Information Typing Architecture (DITA) saved our company well over $100,000 a year. But even better, it helped us to ramp up very quickly and get the entire team using a consistent methodology that improved our content, our agility as a team, and our customer experience. Using MadCap Flare paired with source control enabled us to establish a mock content management system that provided most of what we would get by paying for a DITA CMS, but with fewer limitations and more room for creativity. Learn about the benefits we’ve experienced, as well as how we integrated the best aspects of DITA into our content development methodology.

Tuesday, April 4

9:30-10:25 AM

Working with MadCap Flare and Confluence in a Dispersed Team

Track 4 MadCap Flare • Confluence • Single Sourcing • Case Study

In this presentation, we will talk about the options and tools we evaluated for how to work most effectively with a dispersed project team in an agile environment. Through trial and error, we developed a collaborative paradigm that allowed us to complete the documentation development alongside the product development, whether the team is local or international. The secret was working in both Confluence and MadCap Flare. While Confluence and Flare do not natively integrate with each other, our global team needed to find a way to collaborate and rapidly develop content using both tools. We wanted to produce our initial content using the real time conversational Confluence environment, but we also wanted the robust, single sourcing Flare environment, as well as its professional, tech-comm centered tools, excellent single sourcing model, and responsive output. We will describe the hybrid solution, the ways in which this methodology supports fast-paced development, and how we made it work.