WEBINAR AuthorBridge v3: web-based DITA editing for SMEs - raising the bar ... again

Broadcast: Tuesday, January 29

View recording (registration required) >>

Web-based authoring tools are improving all the time, but with the upcoming release of AuthorBridge v3, Stilo is setting new standards for ease-of-use and performance for SMEs in DITA authoring environments.

Since its inception, AuthorBridge has provide SMEs with a truly unique guided and fluid authoring experience. Specifically designed for users with no knowledge of DITA or XML, it has helped organizations rapidly roll out DITA authoring to non-ID professionals in marketing, engineering, training and support.

To do this well requires sophisticated DITA content processing ‘under the hood’ and this is where AuthorBridge excels.

AuthorBridge v3 provides

  • a guidance panel to help SMEs understand where they are in the structure
  • change tracking; text and structural, authors can accept or reject
  • DITA map support; topics resolved and editable, can be inserted, removed, moved around
  • advanced copy & paste support; ensuring appropriate mark-up is applied and valid
  • superior table handling; support for <CALS table> for complex table formats
  • optimized performance for large documents

Want to see all this in action?

Join Stilo’s VP of Development, Patrick Baker, for this demonstration of AuthorBridge and see first hand why AuthorBridge v3 is the most full-feature, user-friendly DITA authoring tool on the market.

View recording (registration required) >>

WEBINAR | Automating the conversion of content to DITA and optimizing for reuse

Broadcast: Thursday, November 29, 2018

Converting legacy content to DITA and optimizing reuse potential to ensure content quality and consistency across the enterprise is high on most organizations’ to-do list when implementing DITA.

So what tools are available to help ID professionals and where do you start?

In this DITA Knowledge Series webinar, Stilo’s Conversion Services Manager, Helen St. Denis, provides a demonstration of Stilo’s Migrate cloud XML content conversion service and OptimizeR, a new DITA content optimization service. Discover just how easy it is to automate the conversion of content to DITA and following analysis automatically deduplicate any replicated content.

Migrate is a unique cloud service that enables technical authoring teams to automate the conversion of content to DITA and custom XML from source formats including Word, FrameMaker, Robohelp and XML/SGML/HTML. Migrate provides greater control over conversion quality, immediate turnaround times and operates on a pay-as-you-use basis.

Free conversion offer

OptimizeR is a new content optimization service that analyzes your DITA content collections for exact and near-exact matches and identifies reuse opportunities at topic and element level. Following review, it automatically deduplicates content, updates the associated conref libraries and ditamaps and provides a report of all changes that have been implemented.

Free optimization offer

WEBINAR | DITA OptimizeR—maximizing content reuse, September 27

Broadcast: Thursday, September 27, 2018

Presented by
Les Burnham, CEO
Helen St. Denis, Conversion Services Manager

Content reuse is a fundamental benefit of DITA adoption, providing huge efficiency gains to authoring teams and helping to ensure the consistency of published information across an enterprise. However, identifying potential reuse opportunities and implementing reuse strategies can be a painstaking and laborious process. As an increasing volume of content is authored in DITA across authoring teams, then invariably more content is replicated over a period of time.

In this Stilo DITA Knowledge Series webinar we introduce DITA OptimizeR, Stilo's new content optimization service. See just how easy it is to automatically identify reuse potential across your DITA content, deduplicate topics and update your maps and conref files.

Learn how, with the DITA OptimizeR service, you can

• significantly reduce the amount of content that needs to be maintained on an ongoing basis

• generate more focussed and rapid search engine results for customer queries

• publish more accurate and normalized content

VIEW RECORDING (Registration required)

WEBINAR | Sharing content across the enterprise

Broadcast June 20, 2018

Presented by Amber Swope, DITA Strategies, Inc.
Introduced by Les Burnham, Stilo International

Can you easily find content created by other teams?
Is content consistently structured across the enterprise?
Do you have a common content lifecycle management strategy?

If you answered “no” to any of these questions, then join us for this Stilo DITA Knowledge Series webinar featuring guest presenter, Amber Swope, president of DITA Strategies, Inc., for a discussion on using content collections to share content.

Content collections are libraries of organized, labeled, source content units that are accessible by the appropriate people. Let’s talk about strategies to create and share the right content in your organization. 

What can you expect to learn?

In this presentation, Amber will explain how to:

  • Identify the requirements for the collection
  • Determine the collection scope
  • Collaborate with other stakeholders to build and manage the collection

VIEW RECORDING (registration required)

This is the third in a new programme of Stilo DITA Knowledge Series webinars for 2018. Check our website for updates - new topics and dates are being added all the time! You can also find more Stilo DITA Knowledge Series resources at stilo.com/knowdita

Meet the presenter

Amber is an internationally-recognized expert on the Darwin Information Typing Architecture (DITA), creator of the Information Architecture Blueprint™, and president of DITA Strategies, Inc. With over 20 years of experience in the information development field and 12 years of DITA expertise, Amber helps teams design, develop, and optimize their information architecture (IA) and implement DITA to improve efficiency and reduce costs. Amber has authored numerous papers and articles on information design, development, and architecture, and has presented at leading industry conferences as a DITA expert. She holds a master’s degree in technical and professional writing and a certificate in computer technical writing, both from Northeastern University.

WEBINAR | How to keep the reuse you have when you move to DITA

Broadcast | Tuesday, March 27, 2018

Presented by Helen St. Denis, Conversion Services Manager
Introduced by Les Burnham, CEO
Stilo International

You are moving to DITA, but you’ve already got reuse happening in your legacy format. Reuse mechanisms don’t usually match DITA’s. How can you keep the added value of content reuse when you move the content to the new format?

You may have your reused content in text insets, common files, or snippets. Text insets and snippets can be big or small, contain any amount or type of content, from a single word or phrase to one or more entire topics, and anywhere in between.

Reuse in DITA, though, happens at the element level, whether by conref or topicref. So we've got to get your content into a form that is readily reusable as we republish the legacy information, as well as available for reuse in new publications.

Thankfully, there's a quick and easy way to do this, and we'll show you how. Join Stilo's Conversion Services Manager, Helen St. Denis, for this Stilo DITA Knowledge Series webinar to learn how to keep the reuse you already have when you move to DITA.

View recording (registration required)

This is the second in a new programme of Stilo DITA Knowledge Series webinars for 2018. Check our website for updates - new topics and dates being added soon! You can also find more Stilo DITA Knowledge Series resources at stilo.com/knowdita

WEBINAR | How to prepare content for conversion to DITA

Broadcast: Thursday, March 1, 2018

Presented by Helen St. Denis, Conversion Services Manager
Introduced by Les Burnham, CEO
Stilo International

So, the decision is made to implement DITA and you now need to convert your existing content from Word, FrameMaker or other unstructured formats. The content audit has been done and you need to figure out what you REALLY need to do to your content before you start the conversion process. It’s maybe not as much as you might think!

Join Stilo’s Conversion Services Manager, Helen St. Denis, for this recorded Stilo DITA Knowledge Series webinar, to learn:

  • What is the most useful thing to do pre-conversion?
  • What kind of things influence what else you might want to do pre-conversion?
  • What are the common trouble areas in the different source formats?
  • What is best left for post-conversion?

View recording

This was the first in a new programme of Stilo DITA Knowledge Series webinars for 2018. Check our website for updates - new topics and dates being added soon! You can also find more Stilo DITA Knowledge Series resources at stilo.com/knowdita

Migration to DITA – The Atmel / Microchip Story

Morten Haaker, Staff Business System Analyst | Microchip Technology
Introduced by Les Burnham, CEO | Stilo International
Broadcast Tuesday, September 26, 2017

Are you thinking about moving to DITA? In addition to learning DITA, tool and vendor selection, creation of stylesheets, change management and other challenges, you may be faced with having to convert thousands of pages of detailed technical information from an unstructured format to DITA.

This was the task Atmel’s Morten Haaker was faced with back in 2013 when the company embarked upon their DITA migration project. Morten and his team successfully converted hundreds of Atmel’s complex technical documentation (semiconductor-specific information and datasheets of more than 2000 pages) from unstructured FrameMaker to the DITA standard using Stilo’s Migrate cloud XML content conversion service.

But the conversion project didn’t end there. In April 2016, Atmel was acquired by Microchip Technology, a leading provider of microcontroller, mixed-signal, analog and flash-IP solutions, and Morten was further tasked with migrating Microchip’s FrameMaker documents to DITA.

Join us, and Morten, for this Stilo DITA Knowledge Series webinar to learn how they approached the issue of content conversion as an integral part of their DITA implementation and how they managed the conversion of Microchip’s technical documentation following the acquisition.

» View recording (registration required)


Presenter bio | Morten is a Staff Business System Analyst at Microchip Technology responsible for the technical documentation project. Located in Norway, Morten has been with Atmel/Microchip for more than 15 years. He holds a Master of Computer Science from the Norwegian University of Science and Technology and heads up the Nordic SDL Knowledge Center User Group.

Migrate cloud XML content conversion service DEMO

Broadcast July 12, 2017

Join Stilo’s Conversion Services Manager, Helen St. Denis, for a demo of the Migrate cloud XML content conversion service. Migrate is a unique cloud service that enables technical authoring teams to automate the conversion of content from various source formats including XML/SGML/HTML, FrameMaker, Word, Author-it, InDesign, RoboHelp and DocBook to DITA and custom XML. It provides greater control over conversion quality, immediate turnaround times and operates on a low-cost, pay-as-you-use basis.

See why Migrate is the conversion service of choice for organizations including Altera, Cisco, Dell, EMC, Extreme Networks, IBM, Qualcomm, Teradata, Varian Medical Systems, Webtrends and many more.

Find out more about the Migrate XML cloud content conversion service

Convert sample document to DITA for free

View recording (registration required)

DITA and minimalism

Minimalism from a technical writing and training perspective was first investigated and proposed in the late 1970s by John Carroll and colleagues at the IBM Watson Research Center. It has since evolved and been extended by a variety of stakeholders.
The link between DITA and minimalism (the IBM connection notwithstanding) is not exactly carved in stone but the two complement each other like macaroni and cheese. The macaroni (DITA) provides the infrastructure and model that you need to support the cheese sauce (the minimalist content).

JoAnn Hackos’ Four Principles of Minimalism are helpful and useful. They are:

  • Principle One: Focus on an action-oriented approach
  • Principle Two: Ensure you understand the users’ world
  • Principle Three: Recognize the importance of troubleshooting information
  • Principle Four: Ensure that users can find the information they need

However, I would change things up a bit and stress some different points. Minimalism, when applied to technical writing, should result in content that is:

  • Based on knowledge of the users
  • Usable
  • Minimal
  • Appropriate
  • Findable
Based on Knowledge of the Users

Understanding your users is the underlying requisite for applying all other facets of minimalism. Without knowing how they are using the product, how they are accessing the content, and what their daily goals are with your product (and a thousand other factors), you aren’t going to be able to correctly apply the other facets of minimalism.


Write task-oriented topics that are focused on business goals rather than product functionality.

This means you need to understand your users well enough to understand those goals, including what backgrounds they have, what other tools they have at their disposal, their educational background, and a host of other information. User personas can be a powerful tool here.

The action-oriented approach is important but more specifically, you should be writing procedural information (tasks). One absolutely vital piece of any task is a detailed, goal-based context for the task. Done well, this context is an essential component of the learning process. The context the “why” that helps users situate themselves—so it must be written for and about their goals when using your product. They use that context to take their understanding of your product to the next level. The task’s focus should always be on the user. This focus is often neglected, although usually through either ignorance or time constraints, but the steps of a particular task are almost immaterial when compared to the context.


Powerful, usable content is clear and simple. In this sense, minimalism means removing words that add no value; words or phrases that are long, ambiguous, convoluted; and content that is simply not required.

Short simple sentences are easier to read and provide a basis for better translation. Topics that have only essential information are more easily parsed and will be read with more attention. If you limit yourself to essential words, then every word will be valuable to end users.

This facet of minimalism can often be done as part of an editing pass, either by you, a peer reviewer, or an editor—or better yet, all three. Remember that fewer, clearer words is more work, not less.


The careful selection and placement of every word you write should always be on your mind, from the planning stages through to the editing stages of your content. For content to be appropriate, it has to be the right information in the right place, support error recovery, and be formatted correctly.

  • Provide the right information in the right place to support users in their goals.

A pre-requisite to a task that is placed between steps four and five is a good example of content being in an inappropriate location. Always move a pre-requisite up before the context (in its valid DITA location) for consistency and because no one wants to get part-way through a task only to realize that should have done something important before even beginning. Similarly, if you need to prevent a common error from occurring between one step and another, then put it right there instead of in a separate location or topic. Best practices, mentioned in the right place, can save your users the hassle of having to troubleshoot later on.

  • Write detailed error recovery using DITA 1.3’s new troubleshooting topic and elements.

Many users will turn to the documentation only when they have run into a problem and need to look for a solution, so you are most definitely trying to write exactly what they are looking for. Troubleshooting, if it is concise and can’t be separated out from the context of its related task, should be kept inline using any of the three new troubleshooting-related elements (task troubleshooting, step troubleshooting, or the troubleshooting note type). When there’s too much information or the troubleshooting topic really should stand on its own (and be searched for as a discrete object) it should be written using the new troubleshooting topic. For any troubleshooting information (whether it’s a topic or inline), your goal is to provide error recovery by identifying a condition, a cause, and a remedy. The new troubleshooting topic also allows you to provide multiple cause and remedy pairs for a single condition to cover more complex cases.

  • Provide supporting information in the right format.

Although much of your minimalistic content will be in task topics (and thus formatted as ordered lists), your supporting information should use unordered lists, graphics, and tables depending on the type of information being conveyed. When users will need to scan and look up specific details quickly, you’ll use a table. Graphics will be most helpful when trying to convey an underlying or specific structure or flow. Unordered lists are important for listing parallel items that need to be noted


All of this targeted, minimalist, formatted, supportive content is going to be completely wasted if it’s not also all easily findable.

There are two levels to findability. At the detailed level, it means using short, targeted topics that are the appropriate type (task, concept, reference, troubleshooting, and glossary).

At the macroscopic level, findability means robust search mechanisms including faceted search, role-based content, and filtering. Whether your content strategy calls for building something custom, leveraging something in house, or buying a tool (that can take DITA source content and publish responsive Web-based content with these findability features built right in) is up to your requirements, budget, and timelines.


One of the most valuable changes you can make to your DITA content is applying minimalism to that content, both before and after your DITA conversion. Take the opportunity when learning DITA to learn how to apply minimalism to your content. It will not only improve your content and make your users far happier (leading to customer satisfaction improvements that will positively affect the entire company), it will also allow you to further define and refine your entire content strategy.

Further reading

JoAnn Hackos: Minimalism Updated 2012

OASIS DITA Adoption Feature Article on Troubleshooting in DITA 1.3: DITA 1.3 Feature Article: Using DITA 1.3 Troubleshooting

Overcoming writer resistance to DITA adoption

I could easily have titled this article “Why your writers are suddenly freaking out,” because that is exactly what happens on teams that adopt DITA—there is always some degree of writer resistance. Even the best writers experience a moment of doubt when contemplating such a complete overhaul of their writing tools and standards. The trick, as someone implementing DITA, is to manage those fears wisely, even preempting them when possible, so that writer resistance becomes writer acceptance.

Successful DITA adoption relies on three pillars of strength: a solid content strategy, a detailed and realistic project plan, and a useful change management plan. That last pillar, the change management plan, is most often forgotten or left out and that’s where you’ll plan your strategy for overcoming inevitable writer resistance.

Why writers resist

Although many writers understand and embrace the changes that DITA introduces into their day-to-day writing, when they’re actually faced with adopting DITA, it can be a scary prospect. There are some key reasons for resistance.

Lack understanding of DITA best practices

Even if authors understand the basics of DITA, it’s not always clear how to do things the best way. This murky beginning can daunt even the most seasoned writers. In fact, the more senior the writer, the more likely they are to be bothered by this gap in their skillset.

Job loss

Many authors fear that their team will be downsized because DITA promises to be a more efficient way of creating and managing content. Although companies rarely downsize after adopting DITA, it is still a fear that needs to be managed because it can drive a very stubborn resistance; people feel like they are fighting for their livelihoods.

New tools

You are asking writers who have been using FrameMaker, Word, InDesign, and, in some cases, text editors to adopt a completely new writing tool, one that doesn’t necessarily reflect the look and feel of the end product they are creating—which is very confusing at first.  Piled on top of that, you are also asking them to learn a few hundred elements, attributes, and probably a CCMS as well. There’s no doubt about it, there is a lot to learn all at once.

New way of writing

The move from chapter-based or narrative writing to topic-based writing is a huge change for most writers. This is actually the change that writers struggle with most in the first 6 months.

Many authors have been doing things the same way for so many years that they’re uncertain if they’ll be able to adapt to a new way of writing, one that focusses more on modular writing and user goals. Often, this change in the way they write exposes a gap in their understanding of the end users and how they’re using the product. Although this gap is usually not their fault, it certainly hinders creating quality DITA content and reflects poorly on the writer.

Forms of resistance

There are generally two kinds of resistance you’ll run into: active and passive. You might see some authors using both forms while others will choose one over the other. The key to a smooth writer transition is to anticipate both forms and deal with them separately.

There’s no shame in being either one of these types of resisters. DITA is a big change and it’s up to management to ensure that the writers have all the knowledge (whether it’s tools, training, or communication) to ensure that change is as easy as possible.

Active resistance

Active resistance includes being vocal about doubting the adoption process, personnel, tools, or management handling of the adoption. Often, these writers will derail meetings or training with side issues—and you’ll suddenly find yourself mired in meetings that never accomplish what you need them to. Everyone’s work starts suffering and tempers run hot.

They might also take their disgruntlement to fellow team members and try to gang up on a manager, raising doubts and concerns that although real to them, are usually unfounded. If you get a group of writers entering your office one day to “talk to you about this DITA thing,” then you know you’ve neglected to address the concerns of your active resisters.

Passive resistance

Passive resistance includes not using the tools, performing tag abuse (using the wrong tags to get a specific result), not chunking content into topics, and generally not implementing the content strategy that is laid out for them. In some cases, you’ll find that an author has simply never made the transition from the old tools—they are sneakily still using them.

Passive resisters aren’t trying to rock the boat, but they definitely need help to make the change successfully.


A change management strategy is your plan for deciding how you’ll introduce the changes that DITA requires. Part of your change management plan should be specifically targeted towards identifying likely resistance from your team and how you’ll address each issue.

  • Active resisters: These are actually the easiest resisters to deal with because they are so easily identified. The best way to work with active resisters is to get them involved with the planning and content strategy. Active resistance also usually means that your writer lacks training or doesn’t understand that training will eventually cover all their concerns. Getting your active resister to create or review the training plan (what kind of information do we need at which point in the adoption) often circumvents their fears.
  • Passive resisters: Although passive resistance is harder to identify, you can plan for ways to either prevent it or catch it immediately. Feedback combined with adequate and timely training will solve this problem.

Don’t forget to proactively address your writers’ reasons for resistance in your plan. When you manage change, use the following tools to help address their underlying fears and keep your authors moving forward.

Communications plan

This plan should include how and when you’ll communicate the goals and progress of your DITA adoption. Use this plan to specifically address the issue of downsizing or job loss. Most companies don’t even think about downsizing because they are about to invest time and money into upgrading the skills of those same resources. However, authors still need to hear that their jobs are as secure as they have ever been from management.

The message you want to convey (at key points and on a regular basis) is that you are training them to be more valuable tech writers with two major goals: easier content lifecycles (happier writers and reviewers with more time to write usable, focused content) and more usable content (happier end users).

Don’t forget that DITA adoption also means new roles will be available, like content strategist, tools maintenance, and publishing expert, to name just a few. DITA adoption opens doors to all sorts of opportunities. And even if the company is downsizing, your writers will leave after being trained in DITA, making their options for a prospective job that much better.

This is also the time to let them know that their yearly performance reviews will include DITA adoption goals. For example, you can include each document converted to DITA or each new documents written in DITA as point on their performance review. You can even gamify this process and have writers compete for the most DITA-related points, which will convert to real dollars at the end of the year. If you give writers a target to shoot for with their DITA adoption, you’ll be pleased with the results.

Training plan

The right training for the right people at the right time in the adoption can prevent problems for both types of resisters. Authors need several kinds of training to get up to speed quickly but smoothly. Very early on, start with DITA fundamentals and then closely follow by topic-based writing, minimalism, tools training, process training, and DITA best practices.

Your content strategist and your publishing specialist will need training in DITA content strategy, metadata, and XSLT/DITA Open Toolkit (or equivalent, depending on your choices) very early on.

It’s a good idea to plan for ongoing training for the first four years in addition to formal training during the initial adoption phase. This ongoing training can be more informal and internal where authors and content strategists can share tips, tricks, and best practices among team members. You should also plan for key people to attend DITA-related conferences so they can get exposure to a wider world of what is possible with DITA.

Some companies have hired a consultant to bring an internal resource up to speed for the role of content strategist as a sort of ongoing, as-needed training from an expert.

Whatever your decisions for promoting, shifting, or even hiring your resources, an effective training plan will preempt a lot of resistance.

Feedback conduits

Authors need a way to have someone check their tagging and writing for the first 4-6 months to give them essential feedback on how to do things better or which pitfalls to avoid. This is where you’ll catch most of your passive resisters, but to do so, it’s essential that someone track who is and who is not getting their content checked.

Also provide a way for authors to ask questions from someone who knows the right answers. If you can do this in a way where they don’t need to risk looking or feeling dumb to their manager or peers, then it will be more of a success. A wiki page is a good idea or an anonymous Q&A drop box works well too, with the answers coming from someone with DITA experience (usually a content strategist, either full time or consulting).


Overall, writer resistance is a normal part of a DITA adoption project and can (and should) be planned for just like every other aspect of the project. Identify the root causes for your team and plan for how and when you’ll address those concerns for both active and passive resisters.