While people are interested in hearing about successes, we can actually learn more from failure. Not only do we discover what not to do, but also how to avoid the circumstances that led to it. Presenter Keith Schengili-Roberts has seen a lot of good and bad things happen to DITA implementations over the years, and part of his job at IXIASOFT is to investigate what works, what doesn’t, and why. Listen to his stories on the best (worst) DITA practices!
A brief discussion of reuse challenges in DITA and various responses to those challenges. Focuses on the challenges inherent in reusing topics that contain embedded cross references.
Optimizing Content Reuse with DITA - slides from FREE webinar presented by LavaCon, with Keith Schengili-Roberts, IXIASOFT DITA Specialist
DITA was designed around the idea of content reuse. Maps, topics, conrefs and keys all provide the means for sharing and reusing content effectively within a documentation team using the standard. But what are the optimal ways of doing this, and what are the common mistakes first-time DITA users make when it comes to content reuse? Did you know that DITA 1.3 offers up additional means for reusing content by using such things as scoped keys? And what good is content reuse if you can’t find the content you are looking for?
In this presentation IXIASOFT’s DITA Specialist Keith Schengili-Roberts will examine content reuse best practices, and look at how the idea of content reuse has evolved, changed and been refined since DITA first debuted over ten years ago. This webinar will be conducted through GoToWebinar, and the link will be sent the day before the event.
Webinar sponsored by IXIASOFT, presented by LavaCon.
Optimizing Content Reuse with DITA - LavaCon Webinar with Keith Schengili-Rob...IXIASOFT
Join Keith Schengili-Roberts, IXIASOFT DITA Specialist, and the LavaCon crew, for a free webinar on Thursday, September 8, 2016 to learn more about optimizing content reuse with DITA. Just click on the gotowebinar link above to register - it's free!
Optimizing Content Reuse with DITA
DITA was designed around the idea of content reuse. Maps, topics, conrefs and keys all provide the means for sharing and reusing content effectively within a documentation team using the standard. But what are the optimal ways of doing this, and what are the common mistakes first-time DITA users make when it comes to content reuse? Did you know that DITA 1.3 offers up additional means for reusing content via using such things as scoped keys? And what good is content reuse if you can’t find the content you are looking for?
In this presentation IXIASOFT’s DITA Specialist Keith Schengili-Roberts will examine content reuse best practices, and look at how the idea of content reuse has evolved, changed and been refined since DITA first debuted over ten years ago.
Webinar hosted by LavaCon, Sponsored by IXIASOFT.
Click here to listen to the webcast - http://bit.ly/MdAzXd
DITA Tasks are often the most valuable content we create – especially when we present them in Support portals. But if end-users can’t find them they have no value – avoiding that requires classifying them with metadata and labels from a standard taxonomy.
Taxonomy and metadata can seem like scary or complex turf to the uninitiated – but they don’t have to be. In this 40-minute webinar, Paul Wlodarczyk will walk you through a simple process to begin to assemble a basic taxonomy of controlled vocabularies for tagging your DITA Tasks.
You will learn:
The most critical metadata for classifying tasks – regardless of your industry
How to use tools that you already own to build your taxonomy
Simple rules for keeping your terms consistent
Using existing lists of terms so you don’t have to build a taxonomy from scratch
A brief discussion of reuse challenges in DITA and various responses to those challenges. Focuses on the challenges inherent in reusing topics that contain embedded cross references.
Optimizing Content Reuse with DITA - slides from FREE webinar presented by LavaCon, with Keith Schengili-Roberts, IXIASOFT DITA Specialist
DITA was designed around the idea of content reuse. Maps, topics, conrefs and keys all provide the means for sharing and reusing content effectively within a documentation team using the standard. But what are the optimal ways of doing this, and what are the common mistakes first-time DITA users make when it comes to content reuse? Did you know that DITA 1.3 offers up additional means for reusing content by using such things as scoped keys? And what good is content reuse if you can’t find the content you are looking for?
In this presentation IXIASOFT’s DITA Specialist Keith Schengili-Roberts will examine content reuse best practices, and look at how the idea of content reuse has evolved, changed and been refined since DITA first debuted over ten years ago. This webinar will be conducted through GoToWebinar, and the link will be sent the day before the event.
Webinar sponsored by IXIASOFT, presented by LavaCon.
Optimizing Content Reuse with DITA - LavaCon Webinar with Keith Schengili-Rob...IXIASOFT
Join Keith Schengili-Roberts, IXIASOFT DITA Specialist, and the LavaCon crew, for a free webinar on Thursday, September 8, 2016 to learn more about optimizing content reuse with DITA. Just click on the gotowebinar link above to register - it's free!
Optimizing Content Reuse with DITA
DITA was designed around the idea of content reuse. Maps, topics, conrefs and keys all provide the means for sharing and reusing content effectively within a documentation team using the standard. But what are the optimal ways of doing this, and what are the common mistakes first-time DITA users make when it comes to content reuse? Did you know that DITA 1.3 offers up additional means for reusing content via using such things as scoped keys? And what good is content reuse if you can’t find the content you are looking for?
In this presentation IXIASOFT’s DITA Specialist Keith Schengili-Roberts will examine content reuse best practices, and look at how the idea of content reuse has evolved, changed and been refined since DITA first debuted over ten years ago.
Webinar hosted by LavaCon, Sponsored by IXIASOFT.
Click here to listen to the webcast - http://bit.ly/MdAzXd
DITA Tasks are often the most valuable content we create – especially when we present them in Support portals. But if end-users can’t find them they have no value – avoiding that requires classifying them with metadata and labels from a standard taxonomy.
Taxonomy and metadata can seem like scary or complex turf to the uninitiated – but they don’t have to be. In this 40-minute webinar, Paul Wlodarczyk will walk you through a simple process to begin to assemble a basic taxonomy of controlled vocabularies for tagging your DITA Tasks.
You will learn:
The most critical metadata for classifying tasks – regardless of your industry
How to use tools that you already own to build your taxonomy
Simple rules for keeping your terms consistent
Using existing lists of terms so you don’t have to build a taxonomy from scratch
Session at tcworld 2016. Organized by Kristen James Eberlein (Eberlein Consulting LLC); other participants were Joe Gollner (Gnostyx), George Bina (SyncroSoft), Jean-François Ameye (IXIASOFT), and Eliot Kimber (Contrext).
DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A M...Paul Wlodarczyk
DITA was conceived as a model for improving reuse through topic-oriented modularization of content. Instead of creating new content or copying and pasting information which may or may not be current and authoritative, organizations manage a repository of content assets – or DITA topics – that can be centrally managed, maintained and reused across the enterprise. This helps to accelerate the creation and maintenance of documents and other deliverables and to ensure the quality and consistency of the content organizations publish. But the next frontier of DITA adoption is leveraging semantic technologies—taxonomies, ontologies and text analytics—to automate the delivery of targeted content. For example, a service incident from a customer is automatically matched with the appropriate response, which is authored and managed as a DITA topic. Learn how organizations can leverage DITA, semantics, content management, dynamic documents, and linked data to fully utilize the value of their information.
Shows how to use XSLT with FrameMaker 2017. Provides an overview of XSLT basics and demonstrates how to integrate simple XSLT transforms with FrameMaker structured applications.
Introduction to XML and Structured Authoring • Overview of DITA • Topics: The Basic Information Types • Maps: Assembling Topics into Deliverables • Common elements and attributes • Metadata • Examples and exercises
This presentation was made to the Boston DITA Users Group in December 2019. It looks at how the DITA standard is developed, some of the new "features" to expect in DITA 2.0, a brief look at Lightweight DITA, and the possible futures of DITA and structured content in general.
Presented by Leigh W. White, IXIASOFT DITA Specialist at CMS/DITA North America 2015 in Chicago.
A hot topic among DITA users, DITA 1.3 is the next version of the DITA standard and introduces key scope, which potentially allows multiple definitions of a key within a single output scope. Her presentation explains what key scope is, how it works, and offers several examples of how key scope can be used in both simple and complex scenarios. http://www.ixiasoft.com/en/news-and-events/news/2015/ixiasoft-sponsors-presents-cmsdita-north-america-2015/#sthash.lf3HQ5aV.dpuf
DITA Quick Start: System Architecture of a Basic DITA ToolsetSuite Solutions
Presenter: Joe Gelb, President, Suite Solutions
Abstract: In this webinar, you will learn about the software, integration and customization which enable you to effectively author, manage, localize, publish and share your DITA XML content. We will review how each tool fits into the content lifecycle and discuss options for an incremental DITA XML implementation using a basic toolset as the starting point.
Gone through articles and presentations on the web and got a half-baked understanding of the Darwin Information Typing Architecture (DITA)?
Refer to my DITA Quick Start presentation for the 2007 STC India Conference to learn to evaluate, plan and start implementing DITA.
In this presentation, you will learn about the following:
o Structured authoring and XML
o Key DITA concepts: topics, maps, specialization
o DITA architecture and content model
o Authoring in topics
o Organizing content using DITA maps
o Creating relationship tables
o Conditional text and reuse in DITA
o Metadata support in DITA
o DITA tools, standards and processes
o Publishing with the DITA Open Toolkit
10 Mistakes When Moving to Topic-Based Authoringdclsocialmedia
But moving to topic-based authoring can be one of the most expensive things you've ever done. In this talk, Sharon Burton will show you the top 10 mistakes made by companies and how you can avoid them. These mistakes can include missing deadlines, delivering poor quality content, or not integrating this content development strategy into the rest of the product development strategy.
Session at tcworld 2016. Organized by Kristen James Eberlein (Eberlein Consulting LLC); other participants were Joe Gollner (Gnostyx), George Bina (SyncroSoft), Jean-François Ameye (IXIASOFT), and Eliot Kimber (Contrext).
DITA, Semantics, Content Management, Dynamic Documents, and Linked Data – A M...Paul Wlodarczyk
DITA was conceived as a model for improving reuse through topic-oriented modularization of content. Instead of creating new content or copying and pasting information which may or may not be current and authoritative, organizations manage a repository of content assets – or DITA topics – that can be centrally managed, maintained and reused across the enterprise. This helps to accelerate the creation and maintenance of documents and other deliverables and to ensure the quality and consistency of the content organizations publish. But the next frontier of DITA adoption is leveraging semantic technologies—taxonomies, ontologies and text analytics—to automate the delivery of targeted content. For example, a service incident from a customer is automatically matched with the appropriate response, which is authored and managed as a DITA topic. Learn how organizations can leverage DITA, semantics, content management, dynamic documents, and linked data to fully utilize the value of their information.
Shows how to use XSLT with FrameMaker 2017. Provides an overview of XSLT basics and demonstrates how to integrate simple XSLT transforms with FrameMaker structured applications.
Introduction to XML and Structured Authoring • Overview of DITA • Topics: The Basic Information Types • Maps: Assembling Topics into Deliverables • Common elements and attributes • Metadata • Examples and exercises
This presentation was made to the Boston DITA Users Group in December 2019. It looks at how the DITA standard is developed, some of the new "features" to expect in DITA 2.0, a brief look at Lightweight DITA, and the possible futures of DITA and structured content in general.
Presented by Leigh W. White, IXIASOFT DITA Specialist at CMS/DITA North America 2015 in Chicago.
A hot topic among DITA users, DITA 1.3 is the next version of the DITA standard and introduces key scope, which potentially allows multiple definitions of a key within a single output scope. Her presentation explains what key scope is, how it works, and offers several examples of how key scope can be used in both simple and complex scenarios. http://www.ixiasoft.com/en/news-and-events/news/2015/ixiasoft-sponsors-presents-cmsdita-north-america-2015/#sthash.lf3HQ5aV.dpuf
DITA Quick Start: System Architecture of a Basic DITA ToolsetSuite Solutions
Presenter: Joe Gelb, President, Suite Solutions
Abstract: In this webinar, you will learn about the software, integration and customization which enable you to effectively author, manage, localize, publish and share your DITA XML content. We will review how each tool fits into the content lifecycle and discuss options for an incremental DITA XML implementation using a basic toolset as the starting point.
Gone through articles and presentations on the web and got a half-baked understanding of the Darwin Information Typing Architecture (DITA)?
Refer to my DITA Quick Start presentation for the 2007 STC India Conference to learn to evaluate, plan and start implementing DITA.
In this presentation, you will learn about the following:
o Structured authoring and XML
o Key DITA concepts: topics, maps, specialization
o DITA architecture and content model
o Authoring in topics
o Organizing content using DITA maps
o Creating relationship tables
o Conditional text and reuse in DITA
o Metadata support in DITA
o DITA tools, standards and processes
o Publishing with the DITA Open Toolkit
10 Mistakes When Moving to Topic-Based Authoringdclsocialmedia
But moving to topic-based authoring can be one of the most expensive things you've ever done. In this talk, Sharon Burton will show you the top 10 mistakes made by companies and how you can avoid them. These mistakes can include missing deadlines, delivering poor quality content, or not integrating this content development strategy into the rest of the product development strategy.
10 mistakes when you move to topic-based authoringSharon Burton
Topic-based authoring is the most cost-effective way to develop content in the "Do more with less" world we live in. It can help reduce localization costs, reduce project schedules, and help you better meet the needs of your users. It's a potential win/win for your company and your users. Makes you want to jump right in, doesn't it?
But moving to topic-based authoring can be one of the most expensive things you've ever done. In this talk, Sharon Burton will show you the top 10 mistakes made by companies and how you can avoid them. These mistakes can include missing deadlines, delivering poor quality content, or not integrating this content development strategy into the rest of the product development strategy.
If you're thinking about making this move, you'll learn what not to do; if you made the move and you're struggling, find out how to solve your problems. Either way, you really can't afford to miss this vendor-neutral discussion!
InnerSource - Using open source best practices to help your companyEric Caron
Once a company has more than 1 department developing code, a problem inevitably arises: How do you share source code that's mutually used? There are many different thoughts on the matter, but one that's starting to gain a significant amount of attention is "InnerSource". PayPal defines InnerSource as:
"InnerSource takes the lessons learned from developing open source software and applies them to the way companies develop software internally. As developers have become accustomed to working on world class open source software, there is a strong desire to bring those practices back inside the firewall and apply them to software that companies may be reluctant to release. For companies building mostly closed source software, InnerSource can be a great tool to help break down silos, encourage internal collaboration, accelerate new engineer on-boarding, and identify opportunities to contribute software back to the open source world."
In this talk I cover how to get from where you are ("Hey, we've got some source code that multiple people find useful!"), where you're going ("Look, we're more popular than ReactJS"), and some hurdles along the way ("Oh shoot, it looks like there is already a library to convert FLAC to MP3s..."). I give real-world examples of doing it right, and leave with some takeaways that people can immediately implement at their own companies.
Slides from the Structured Authoring Workshop at TC Camp 2014 by Tracy Baker, Amy Bowman, and Wendy Shaffer.
The road from traditional book-based authoring to DITA and topic-based authoring is full of potholes.
How do you chop up a book into self-contained topics and put it back together into something that makes sense?
How do you handle reuse and linking?
And how do you wrap your mind around new tools and workflows while still getting your job done?
Three people who have made the trip share their experiences and lessons-learned to help you get to DITA/TBA without taking too many wrong turns.
LavaCon 2017 - Snakes and Ladders: Content Collaboration with Subject Matter ...Jack Molisani
This workshop equips participants with planning tactics for laying out your next content change initiative. Participants will leverage a planning framework and participate in an interactive process of identifying key project opportunities and risks as well as exploring their own project roadmap. In this workshop, the project scenario focuses on how a content management system can be leveraged to facilitate content collaboration with subject matter experts. The topic will be approached using the familiar board game of Snakes and Ladders.
Sure, you could do a lot of guesswork at the beginning of a website design project. Let’s build a template and throw in some placeholders, and see what becomes of it! Only to discover when the text and media come rolling in from your content creators that half the template needs to be rebuilt, and the menu structure you had in mind was way off-base.
This happens a lot, costing everyone involved valuable time and energy — especially you. Learn how to put content first in the sequence of design steps.
This talk will cover:
- Defining your audience and goals
- How to convince your client to provide content in a timely fashion
- Understanding, organizing, and prioritizing content
- Brainstorming ideas for optimal site and page structure
Connecting Intelligent Content with Micropublishing and BeyondDon Day
This presentation will describe and demonstrate a grand unified vision for pulling together different kinds of single-page products for the Web, for print, and more. Lessons from this model can give you an edge in market-leading adoption of the next great thing after micropublishing, the current trend.
DITA and Agile are Made for Each Other by Keith Schengili-Roberts, IXIASOFT DITA Specialist. Presented at CMS/DITA North America 2016 in Reston, Virginia.
Agile software development makes specific demands on documentation teams, whose content creators now need to be more nimble, describe features in a piece-meal fashion, and report on their progress in an effective way. The topic-based structure of DITA is ideally suited to these needs. Keith Schengili-Roberts (also known as “DITAWriter”) focuses on how DITA-based content is the optimal way of working in an Agile environment, enabling content creators to effectively meet the demands of short sprint cycles, measure content output for Scrum meetings, and how to become a pig rather than staying a chicken (yes, seriously). Keith also looks at several case studies of DITA-using documentation groups working within an Agile environment. If you are wondering about what the impacts are of working with Agile or are simply looking to optimize your DITA-based documentation processes, come to this presentation!
What can the audience expect to learn?
Keith expands upon the material that was touched upon during the Best Practices conference on the same subject, including information based on subsequent interviews with clients and other content creators who are using DITA in an Agile environment. He provides information on how others are using DITA in this scenario and emerging best practices within it. Keith has found that many content creators using DITA are looking to move to an Agile environment—particularly if they work for a software firm. The ideas presented here serve as an introduction on what to expect. Even those who do not fit this scenario may find some of the ways and processes used by DITA-using doc groups in an Agile team to be beneficial.
Test & Learn: How to Leverage Design to Learn & Deliver Results Quickly Optimizely
The role of design is often overlooked on growth teams that are moving fast and running experiments at scale. When applied correctly, design can be your growth team's secret weapon. Join Angel Steger, growth design lead at Dropbox, to learn how to leverage design thinking and design craft to super-charge your growth team's velocity while driving high-quality output. We’ll walk through tools and case studies to give you ideas you can put into motion right away.
Attendees will:
Learn how to leverage the Design role within a Growth team
Learn how design quality works in the context of a fast-moving team
Learn how to use design thinking to differentiate between haste and velocity as a cross-functional team
Walk away with tools to learn quickly while making meaningful progress against large unknowns
Cheaper, Faster, Better DITA Implementations, Part 1Lasselle-Ramsay
Tom Voltz from Lasselle-Ramsay presents some of the most important but frequently overlooked architectural aspects of DITA that you can leverage to improve and simplify your DITA adoption process. The right DITA approach will
* dramatically decrease training costs
* increase consistency and accuracy of your content
* simplify your stylesheet customization
Proper implementation sets you up for success. Learn how in this first of a two-part series.
Do the words 'open source' scare you (or your boss)? Do you want to contibute but don't know how? Did an angry person reply to your email scolding you for top-posting? This talk is for you! It will cover various real world relevant aspects of open source communites and projects, as well as put to rest various bits of FUD (fear, uncertainty, and doubt) that vendors may throw around. It'll cover best practices for interaction and contributing to open source projects and their communities (specific to archival, and also a more general foundation) on issue trackers, mailing lists, etc., with confidence, so that everyone can benefit.
LavaCon 2017 - Developing Your Edge: Getting a Seat at the Customer’s TableJack Molisani
In many businesses, Sales account teams closely guard and regulate contact with customers. I have heard of, and have experienced situations where technical communications staff are refused access to customers unless there is a major issue. Customer engagement is the linchpin to understanding requirements and delivering value. It is the critical factor between celebrating success and wasting cycles. My session explores the idea of getting communications professionals to overcome the trust and perception deficits we often face.
A large part of the problem is the perception of how we communicate and a fear of what we’ll say. This mentality impedes and undermines our value proposition. I’ll share ideas and anecdotes about what can we do to:
LavaCon 2017 - How Modern Analytics Will Turn Your Technical Content Into a R...Jack Molisani
Understanding how product documentation is consumed can fuel your company with data that has the potential to transform operations and impact decisions. To gain this insight, you need to change the way you track and mine the behavior of users when they search, read and interact with your technical content. By combining the latest delivery, text-mining and analytics technologies, you will transform tech content into a sensor and its delivery into a data generator.
After reviewing the flaws of the “old” approaches to content analytics, we will study how to properly capture the interactions of users with content. We will also explore the different levels of value that we can derive from modern delivery, text-mining and analytics. We will see how those new technologies can multiply the value of tech content. And we will learn how tech content can be impactful for many different activities and constituencies of the company, gathering more support and becoming more strategic.
LavaCon 2017 - Agile Localization: Building Bridges Between Translation Quali...Jack Molisani
Staying in sync with the rapid cycles of Agile software development can be a challenge for any technical communicator, and even more so when localization is involved. Localization includes both the technical and linguistic aspects of translating software and documentation into other languages. You can be a hero in your organization by creating a smooth process to build a bridge between the seemingly incompatible processes of agile development and localization.
Content moves around. It passes back and forth between authoring, editing, reviewing, and publishing before ever reaching its intended audience. Each touch point creates change, but often that change is elusive or unknown. In regulated industries such as healthcare, aerospace, and pharmaceuticals, proving that you have control over content change is a vital capability. How can you gain and demonstrate that control and how do you present an audit trail of change to the relevant audiences in an appropriate format?
LavaCon 2017 - Much Ado About Templates: Reduce the Learning Curve and Increa...Jack Molisani
How did our team of five information specialists and 100 SMEs, who provide content for a worldwide audience of 3,500 service technicians in a regulated industry, move from Word to XML? We adapted – and used templates! Since we were used to Word templates, it made sense to mimic that for simplicity in training and transition. Templates provide a built-in structure and allow customization of the user experience. Please join us as we expose our experiences with templates in XML.
LavaCon 2017 - Building an Enterprisewide Content Platform—and Why DITA will ...Jack Molisani
Breaking down content silos requires an enterprise-wide strategy that serves a number of distinct departments, creators, reviewers, and consumers. However, an enterprise-wide strategy that requires an enterprise-wide deployment of DITA will very likely fail. DITA simply is not made for ALL the content types and workflows within an organization, which usually span support, marketing, product documentation, legal, and more. In this session, we’ll focus on why an enterprise-wide content strategy is important, alternatives to DITA, and how to get started.
LavaCon 2017 - Take the Risk, Embrace the Change!Jack Molisani
Hoa Aldous has made many difficult choices throughout her life. From escaping Vietnam to opting out of an arranged marriage, she’s had to risk it all on more than one occasion.
In this keynote, Hoa will share her life experiences, how she assessed the risks she’s faced, and that embracing the resulting changes can often lead to the experience you were looking for all along.
LavaCon 2017 - Structured Content Authoring For All!Jack Molisani
Many say “Structured Content Authoring is too complex.” But organizations have no choice: to keep content consistent, findable and manageable, we simply must write and store in a structured format. Semantic tagging, re-use, targeting, conditions, references, all are essential and valuable features that form the essence of Structured Content schemas. If we simply ‘strip complexity’ –for ‘lightweight authoring’- chances are fair that we lose much of this value. The question is: how to make Structured Content Authoring a mainstream activity?
LavaCon 2017 - Building Catwalks Between Silos: Using Taxonomy to Drive Engag...Jack Molisani
While content marketing can improve brand preference, it’s hard to link it to product information directly while maintaining an authentic voice. Conversely, product documentation is perceived as authentic and trustworthy — a potentially powerful marketing asset itself — but can be hard to find and hard work to read. This live use case shows how content marketing can link customers to docs in a relevant, contextual, and scalable way by combining taxonomy and minimalist structured content.
LavaCon 2017 - Getting Dragged Along? Start Charting Your Team’s Course with ...Jack Molisani
To meet the demand for content, do you take a “peanut butter” approach and spread your resources evenly – but thinly – across the whole product? Or do you grease the squeakiest wheel, which means you neglect a wheel that’s more vital to the business? Either way, outside forces dictate how you’ll use your resources. Soon you’ll have a lot of mediocre content that doesn’t represent your team’s value. And that makes it hard to get headcount and funding.
LavaCon 2017 - DITA: Start Small, Grow Big Using Open Source ToolsJack Molisani
You’re considering using DITA and would like to try it out without incurring significant upfront costs, but also keeping your options open longer-term. Where do you start? How will you approach the challenges of content creation, content management, and publishing your content? There are in fact plenty of options. The good news is that XML and DITA are open standards. This has led to a healthy ecosystem with quality commercial and inter-operable open source tools, that do away with vendor lock-in and keep operating costs down. We will discuss the three challenges, show an example of how end-to-end solutions can be built based upon Git and other open source tools. In fact, the result may be better than you’d expect.
LavaCon 2017 - Feed the Goldfish in 19 Minutes and 52 SecondsJack Molisani
Content consumption patterns have dramatically changed over the last decade. The maximum selective sustained attention span of a human being is about 20 minutes. The length of this talk. Latest research shows that the transient attention span of human beings has even gone down from 12 to 8 seconds over the last decade – even a goldfish has a longer attention span.
To communicate technical content in the future successfully, we need to move from drops to drips, deliver smaller content chunks, improve findability and searchability and tailor content to the content consumer’s role and context automatically.
LavaCon 2017 - How UX and Content Can (and Should) Work TogetherJack Molisani
The Farmer and the Cowhand Should Be Friends, or, How UX and Content Can (and Should) Work Together.
Let’s be frank: If UX designers had their way, the only words you’d ever see on the web are lorem ipsum. And yet, words — from interfaces to microcopy to long narratives — are integral to the usability and delight of any web product. Based on his years of UX experience and love of good content, Dylan will talk about ways to bring the two sides together to make better things on the web.
LavaCon 2017 - Implementing a Customer-driven Transition to DITA Content: A S...Jack Molisani
When customer expectations uproot your documentation processes and PDF content offering, how do you mobilize a team that has used the same tools and processes to create book-based, unstructured content for over two decades? When new demands drive the change for structured content to support a myriad of users and multi-channel publishing, the logical choice is a DITA workflow.
Join Ciena, The Content Era and Adobe Tech Comm at LavaCon 2017 Portland for an immersive workshop that highlights how a DITA workflow is possible with familiar tools, a modest budget, and creative handling of the content.
LavaCon 2017 - Evolving the New Content OrderJack Molisani
We are at a critical moment in history, with knowledge bursting at the seams of our organizations. Many of us still struggle to manage numerous modes of omnichannel content engagement: published, interactive, and automated. The solution requires vision to move towards a new order of content intelligence encompassing our organization’s entire knowledge graph. It requires spanning silos, especially between marcomm and techcomm. Join Cruce Saunders as he explores the new content stack, and how to future proof content assets to meet the demands of ever-evolving customer experiences.
LavaCon 2017 - Managing Stakeholders Across the Content Ecosystem: The Key to...Jack Molisani
Trying to implement an content strategy that supports your customers across their entire journey–or even just sell the idea to decision makers? Having problems getting it to fly? More than any other single aspect, stakeholder management is critical to getting support for and implementing a unified content strategy (or ANY project, for that matter). You need to understand THEIR needs and ensure that you’re communicating continually to quiet objections and move your project forward. And it’s not always easy–especially when you’re leading initiatives across silos and teams with no direct authority. Influencing those stakeholders is key!
In this session, Andrea will discuss the success factors to aim for, and the behaviors that can trip you up, when managing stakeholders to successfully support your clients, solve business problems, and drive revenue and customer loyalty!
LavaCon 2017 - Future-proof Your Content: Beyond Traditional Publishing for S...Jack Molisani
This session delineates why the most common publishing methods in today’s technical space cannot survive into the middle of the next decade. Tools and methodologies are required that are scalable for vast increases of “atomic” content and to dozens of more language targets. Discover what the minimum ingredients are for survival in terms of tools, workflows and content strategies.
LavaCon 2017 - Silos. (And other concepts that make us average)Jack Molisani
Content crosses silos, giving content developers a unique perspective of the good, the bad, and the ugly. Years of experience leads to insight, but can also paralyze innovative ideas.
Has your experience given you tribal knowledge and wisdom, or preconceived notions that are no longer true or helpful?
In this keynote, Megan Gilhooly discusses new ways of thinking that challenge common business trends. She will provide examples highlighting how your ability to think critically and your passion for forging new trends can help you throughout your content career.
LavaCon 2017 - Management Workshop Part 1: Leadership and Management in Techn...Jack Molisani
Some of the unique challenges that Tech Comms managers face are offshoring, outsourcing, vendor management, managing across countries, justification of resources etc. In this workshop we will work with real life scenarios and learn from solutions that have been implemented in organizations to manage and lead effective content management teams. You will be exposed to ideas and and handy tools that we to build your team with a varied set of skills for scalability and longevity.
LavaCon 2017 - Stop, Listen, and Collaborate: Creating an Experience-first Co...Jack Molisani
Everyone in your organization wants to keep the user happy—they just have different ideas of how to go about it. Focusing on what information a user needs and when they need it along their journey can act as the bridge between product development, experience design, marketing and sales. Get tips on how to bring each group into the process and how to leverage content as a way to keep the user front of mind.
In this session, attendees will learn a mix of “soft” and “hard” skills to help put together an experience-first content strategy.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
3. Keith Schengili-
Roberts
Who’s This Guy?
What I do:
• DITA Evangelist & Market Researcher at
IXIASOFT
• Chair of OASIS DITA Adoption Committee
• Member of OASIS DITA Technical
Committee and LwDITA Sub-committee
• Lecturer on Information Architecture at
the University of Toronto
• 12+ years of experience with DITA XML
4. 2017
Am Also “DITAWriter”
• Industry blog started 6+ years ago
• Over 275,000 hits(!)
• Regularly updated info on DITA
conferences, DITA books, companies
using DITA, DITA CMSes, DITA editors,
other DITA tools, and DITA consulting
firms
• News and views on DITA use
• Also features interviews with those
making a difference in the world of
DITA
6. 2017
How This Presentation Came About
• Last year I went to the “Best
Practices” conference, and I got to
thinking…
• How often do best practices
emerge after trying out what
ended up being a “worst
practice”?
• I also think we learn things more
readily when they are framed as a
story of “things gone wrong”
7. 2017
This Presentation is Crowd-sourced
• While I have some good stories of my
own of DITA mishaps and adventures, I
decided to reach out to my colleagues
and peers in the industry to get their
take on the subject
• My thanks to everyone who responded!
• In some cases the contributor of the
anecdote does not wish to be identified
• In all cases, no company names are
mentioned
8. 2017
A Pattern Emerges…
Two main types of issues appeared:
1. DITA-specific issues (aka, “poor information
architecture decisions were made”)
2. Problems with processes (aka, “how not to work
effectively with people”)
•Boundaries between categories can be fuzzy; ultimately
it comes back to the people behind the issues
9. 2017
What The Fudge?
• While these two categories
capture the essence of the
types of problems from an
objective, dispassionate
perspective, there’s often a
third, more intangible “What
The Fudge” factor that turns up
• This is what typically propels
what otherwise would have
been a bad experience into a
memorable “worst experience”
10. 2017
A Beginning, a Middle and an End/Lesson Learned
Each of my stories uses this
tried-and-true three part
process of a good story:
1. The good
intention/beginning
2. How things went horribly
wrong
3. What can be learned
11. 2017
Ideas on DITA Best Practices are More Widely Known
• Before I get started, I just want to point
out that many of the examples here are
from the early days of DITA
• While many of these problems keep
coming up, greater dissemination of DITA
best practices from people who have
experience using DITA and better tools
means that there is a growing “core” of
people with good experience out there
• But we can still learn from “Worst
Practices”
A really good
book, from 2011
13. 2017
#1. Content Reuse is Always a Good Thing, Right?
Yes, but it also depends on how you do it.
Consider this example:
• A tech docs group finds that they want use
the conref mechanism for reuse purposes,
such as:
• Creating a standard way of referencing
standardized phrases, such as “Click OK”
• “Let’s use the new trademark term used
in this topic and use that everywhere”
• One writer likes a paragraph another
writer has created in a topic
In all/most cases, the first version encountered
is conrefed, which is in turn re-conrefed, and so
on, and so on…
14. 2017
Welcome to “Spaghetti Conrefs”
How the pain emerges:
• Someone conrefs a phrase containing
a conref, which may contain another
conref, and so on, and so on…
• Nobody knows the origin of the
original conref and it needs to be
changed…
• Somebody changes the targeted
conref-ed word/phrase/block
unknowingly, affecting all
publications that link to it
15. 2017
The Horror… The Horror…
“I have seen 20K references to a
single topic, in a folder
containing 40K objects. I saw
this when a small amount of
content needed to be extracted
and handed off and 10K topics
having to be included for a 20-
topic map, because you can
never get to the bottom of the
broken links to files which link to
other files which link to…”
16. 2017
Solutions to Spaghetti Conrefs
1. Just don’t do that. For phrases that are
commonly used, create a conref
warehouse: a single file or set of files
that cover off most commonly-used
blocks of content
• When people want to add new
items, discuss with the group, then
add accepted additions to this
warehouse topic
2. For trademark terms / product /
company names, consider using keys,
and storing their values in a key
warehouse topic
Nolwenn Kerzreho
Technical Account Manager Europe,
IXIASOFT
17. 2017
#2. Never Specialize Your Content
• Specialization is core to DITA,
allowing people to create new topic
types, elements and attributes
• The general recommendation has
been: “do not specialize if you don’t
have to”; specialization is not easy,
and it can limit content reuse,
especially if you intend to share your
content to other organizations
• But “never” is a strong word…
18. 2017
A Worst Practice from a Supposed Best Practice
An example that shows the pain this can cause:
• Client was (incorrectly) told not to specialize
• Implementation had to be done on a tight timeline (uh oh…)
• As a result, there were outputclasses in places that didn’t make a lot of
sense, including:
• Individual table cells (instead of to the table or row)
• various types of images for explicit scaling purposes
• bibliographic references (which also included convoluted, doubly-
referenced conrefs)
• These were all poorly designed, ultimately making more work for the
writers
19. 2017
Pairman’s Outputclass Rule
• Result: a frustrating mess for all involved
• Better, more judicious use of the
available DITA elements, such as
wrapping a fig element around image
for better block-level formatting
• Pairman’s Outputclass Rule: “if an
organization uses the outputclass
attribute for more than two or three
different features, think instead at
better leveraging the standard, including
the possibility of creating a
specialization.”
Lead Consultant, Mekon
20. 2017
#3. If a DITA Tag Exists, We Should Use It
• Sharon Figueira’s
story: “during the first
migration I did, my
team and I were so
enchanted with DITA
and its every last detail
that we implemented
as many tags as
possible. We had the
approach of:
‘if it’s there we
should use it’.
Basic + Technical DITA 1.3 Elements
433 Elements
21. 2017
The Problem, The Pain
Luigi Russolo, The Revolt (1911)
• It was a self-made problem:
“The ridiculous thing was that
we weren’t using these tags
before DITA, so why we
thought we suddenly had a
need for filepath etc. I
have no idea.”
• The pain: “the writers soon
revolted and refused to put in
multiple inline tags per
paragraph.”
22. 2017
Figueria’s DITA Complexity Formulation
• There are many tag and element
choice options in DITA, and you
are not obliged to use them all
• While you might want to add new
semantically-descriptive
tags/elements to your existing
content when migrating,
• Figueria’s DITA Complexity
Formulation: “Build out
complexity slowly and in response
to a well-understood need.”
Sharon Figueira
Pre-Sales Engineer, IXIASOFT
23. 2017
#4: All DITA is Good DITA, Right?
• The scenario: firm is moving to
DITA, decides to contract with an
outside firm to migrate their
legacy content over to DITA
• Client is new to DITA; assumes
content migration firm knows
what it is doing and so the client
provides little or no direction on
how to do the conversion
24. 2017
Problems with Unoptimized DITA Converted Content
• Conversion firm does its best, but without
guidance it can’t optimize the content for the
needs of the client; creates DITA content
using minimal DITA tagging, done in most
generic manner possible
• Final result initially looks good, but problems
emerge:
• Works poorly with newly-created DITA content
• Need to convert from generic to specific topic
types
• Provides no guidance to writers working with
content
• Problematic when it comes to content reuse
• Keys for product names not present
25. 2017
Pringle’s Directions for DITA Conversion Success
1. Learn enough DITA to know what you
need to specify in any converted legacy
content.
2. Create new, sample content covering
what you think you will need. When it
works the way you intend, show it to
the conversion firm. If they are good at
what they do, they will provide
suggestions based on your model to
improve it.
3. Only then begin the legacy conversion!
Alan Pringle
Chief Operating Officer,
Scriptorium Publishing
26. 2017
#5: A DITA Test Output Document? What’s That?
• A DITA output related tale: a DITA
test document is a map + topics
designed specifically to test output
conditions
• As new XSL transforms are added,
add content to the test document
to see how they work
• Can be used to test fonts, image
sizing, widow/orphan control, how
errors appear; basically to test the
“look and feel” of everything
27. 2017
“It was Working Before”
• Example: shortly after a software
upgrade, images no longer rendered
properly for a new document; blame
was put on software
• Separate test installation showed that
new software was working fine
• A recent change in how images were
inserted into DITA code was the real
culprit; in the end a single line of XSL
code had to be tweaked
• Discovering the root cause without
having a test document took 8 hours…
28. 2017
Proulx’s DITA Test Document Dictum
• Create a separate test document designed to
test all aspects of your DITA output conditions
• It can serve as a companion to your style
guide, showing expected output under all
circumstances
• Every time something is changed (new DITA
feature, software, rendering engine, etc.),
check output using test document and
compare to previous version
• Should not be an existing document, as it can
always be changed (as the last example
shows)
Martin Proulx
Senior IT Specialist &
Integration, IXIASOFT
30. 2017
#6: “Just Let IT Choose a CCMS for You”
• This past summer I worked
on an internal project,
studying the factors behind
“successful” RFIs/RFQs from
vendor perspective
• Over a third of the RFIs/RFQs
I reviewed had zero or
minimal references to
“DITA” in them
• In most of these cases it was
clear that IT was choosing a
CCMS based on their
technical requirements, with
little to no input from the
technical writers
31. 2017
Some Not Unexpected Results When this Happens
• Technical writing team is given a
CCMS that they had no part in
selecting; not surprisingly, this
often leads to general
unhappiness
• Project may lead to outright
failure; DITA / CCMS initiative may
be dropped
• Or, at significant expense, a
second, more appropriate CCMS
is selected, this time with input
from technical writing staff
32. 2017
Schengili-Roberts’ RFI Recommendation
• When your company is choosing a
CCMS, make sure that the
technical writing staff plays an
active part in the selection
• Should cover not only what you
need in terms of DITA
requirements, but in terms of
processes and expected
workflows, report capabilities,
metrics gathering, expected
content contributions from SMEs,
localization requirements, etc!
Keith Schengili-
Roberts
33. 2017
#7: “Workflow Captures / Enforces All Possibilities”
• Introduction of a DITA CCMS into a
company provided the opportunity
to hone the workflow in which
content is reviewed, managed and
produced
• Consultant is brought it, and maps
out a very detailed workflow that
captures every possibility:
• initial state, editor review, second
review steps (including SME review),
third step (including separate
reviewer/editor), and so on…
34. 2017
Let The Technical Writers Eat Cake?
• This was all for a team of three
technical writers
• Not all steps were necessary, but
they were all implemented within
the CCMS
• This meant that even the smallest of
changes (such as typos) had to go
through this process
• Not surprisingly, the technical writing
staff soon revolted against this strict
and overly-convoluted workflow
35. 2017
Anonymous’ Recognizing Workflow Reality
• This story is relayed by a subsequent
consultant who came in to try and fix
the resulting mess
• In the end DITA usage was dropped
within this firm, even though DITA
itself had nothing to do with the
problem
• Solution: start with a basic workflow,
and then build up as required; build
flexibility into the system to allow for
minor changes or overrides as
required
Anonymous
36. 2017
#8: The Person with Too Many Hats
• The change from unstructured
to structured content does not
just mean a change in how to
write content, but also in the
associated roles for a technical
communications team
• Situation: a “DITA Lead” person
is designated, and they are
given all of the tasks with
making the DITA
implementation a success
37. 2017
DITA Overload Ensues!
• That one designated person must
adopt multiple roles at once,
which may include:
• Conversion Specialist
• Information Architect
• Trainer
• Project Manager
• CCMS Administrator
• XSL Developer
38. 2017
Houser’s “A Head for Each Hat” Homily
• This is a sure way for a structured
content initiative to fail
• Understand the new roles that are
required; see: Roles and
Responsibilities of a DITA Adoption
(from: www.oasis-
open.org/committees/download.php
/50770/DITA_Roles_Responsibilities_
final.pdf (or goo.gl/s3x44g)
• Effective change management is
required, ideally have one person per
“hat”
Alan Houser
Technical Publishing Consultant,
Group Wellesley
39. 2017
#9: “They Can Learn DITA as They Use It”
• An all-too-common
assumption that
technical writers are
able to cope with
writing content while
also learning the
intricacies of DITA
elements and
attributes
40. 2017
Juggling Too Many Balls
• Learning DITA while trying to
implement it is a sure way to
lengthen the time of
productivity dip when moving
to a new system / process /
CCMS
41. 2017
O’Keefe’s DITA Training Lesson
• Where possible, bring in someone
with DITA experience to help train
the rest of the technical writing
staff
• Can be external consultant or
someone internal who already
knows DITA
• Another alternative: online courses,
such as those offered by CIDM or
LearningDITA.com
• Proven to shorten productivity gap
Sarah O’Keefe
CEO, Scriptorium Publishing
42. 2017
#10: “We Already Have Sufficient Executive Buy-in”
• European software firm contracts
with consultant for most of a year
to understand and rationalize
their information architecture and
overall content strategy
• I am brought in to help train
Directors on basics of DITA for
several days
• A full plan is ultimately delivered
to company’s board
43. 2017
•One executive ends up
saying: “if we can’t do
this using [insert exec’s
favourite technology
here] we aren’t going to
do it”
•All that work and
preparation goes down
the tubes…
Um, We Forgot About the Pointy-Haired Boss…
44. 2017
Anonymous’ “Always Get Full Buy-in First”
•Not anticipating this “requirement”
was a serious oversight by those
leading the project
•While this example is extreme,
lower-level buy-in from SMEs,
Directors, Managers and of course
from your technical writing staff
counts as well
•It’s all about effective
communication
Anonymous
45. 2017
Son of DITA Worst Practices?
This is only the beginning of the stories I have been told; there’s easily enough for
another presentation. Other ideas:
• Feeling compelled to move to DITA without really understanding what business issues
need to be addressed
• Going through a tool selection process without performing even basic information
architecture
• Over 1K DITA “variables” (keys) created to cover every product name, trademark,
interface control, file paths, etc.
• Repeated chunking at or below the sentence level
• Writers using semantic tagging just to change how something appears at output
• Constraining out short descriptions, then finding resulting SEO is poor as users can’t
find content
46. 2017
A Review of DITA Worst Practices
1. Content Reuse is Always a
Good Thing, Right?
2. Never Specialize Your
Content
3. If a DITA Tag Exists, We
Should Use It
4. All DITA is Good DITA, Right?
5. A DITA Test Output
Document? What’s That?
6. “Just Let IT Choose a CCMS
for You”
7. “Workflow Captures /
Enforces All Possibilities”
8. The Person with Too Many
Hats
9. “They Can Learn DITA as They
Use It”
10. “We Already Have Sufficient
Executive Buy-in”
47. 2017
Documentation Does Not
Happen by Magic
• Must remember that all
documentation is made by
and for people
• DITA may be a driver towards
creating better
documentation, but it is part
of a larger process that
involves people and tools
• Need to think about
documentation in a new way
48. 2017
QA
• Blog on www.ixiasoft.com
• Twitter: @IXIASOFT and @KeithIXIASOFT
• IXIASOFT DITA CMS Users LinkedIn group
• OASIS DITA Adoption Committee articles
• Member of OASIS DITA Technical
Committee