Search Resources

Content Type

Company

Author

This is a presentation that provides an intersection between content and design. It is a high-level practical guide to analyzing your content, deciding what you want to do with it, developing style naming conventions, and developing editorial style guides, design style guides, and style templates.

A look at the treasures of telecommute during times when you least expect it.

Post conversion cleanup efforts fall into three levels. Learn details on how resolving issues in each phase will continue to improve your content quality.

In this session, we’ll see both traditional and headless delivery strategies that will inspire you to think about content in new and exciting ways.

This presentation will define the new exponential organizations, companies that grow often at 10 times faster than comparable companies, and are guided by a massive transformational purpose to deliver Information Enablement through innovations such as “ Content as A Service” – CAAS.

Rob Hanna explores how information-enablement across the enterprise is key to this type of performance and why we need to rethink how we create content to become Exponential Organizations.

GitHub has many uses but there are limitations - this webinar will introduce some work arounds and help you identify when it might be time to consider a fully functioning CCMS (Component Management System).

One of the many things I’ve learned from VMware is how essential it is to incorporate Enterprise-Grade documentation reviews in each release cycle, regardless of company size or geographic differences. Working at a start-up is exciting, it’s thrilling, and there’s constant action, with the opportunity to build something from the ground up. The high agility allows engineering to release new features, updates, and fixes at the flip of a coin. As a Technical Writer, my biggest struggle was trying to figure out how to keep the documentation accurate and helpful to our customers, while still flowing with the agility of the start-up environment; I believe VMware Workspace ONE UEM has found a solution.

In this session, Ayush Gupta, Product Manager at Adobe, will discuss how organizations can transform their mundane, time consuming and cyclic review process into a more meaningful, error-free and productive collaboration experience for Content Creators and Subject Matter Experts (SMEs).

A summary and analysis of the 2020 survey "Following the Trends, Is Your Content Ready?"

Join Lawrence Orin, Product Evangelist and Customer Implementation Expert at Zoomin, as he takes an intriguing look at content strategy, and reveals a down-to-earth, practical approach that will ensure your writing is making a visible impact on your company.

There is a lot of confusion about how difficult writing in DITA can be. This article is part 2 of 3 on learning how to author in DITA, which focuses on writing for accessibility.

A brief look at what we'd do differently in our DITA migration and why I came to that conclusion.

Self-service support portals help organizations realize their content strategy in three ways: enabling content to be more findable, providing user feedback mechanisms, and facilitating the breakdown of content silos by unifying disparate content types across an organization.

In this webinar, we will showcase: how to leverage metadata to make your content searchable, what is the difference between good and bad taxonomies, and a live example of taxonomy development using Adobe Experience Manager.

During the webinar we walk through the results of the 2020 Trends Survey, a study we have been conducting since 2012. We trace the changes in how we think about developing and delivering content.

It seems like a lifetime ago that distractions were the bane of people working at home. Casual calls, chores, well-meaning friends, and family could break your momentum. Avoiding distractions was vital to success. COVID-19 has changed how we view so things today, even distractions.

When developers and technical writers work well together, they both take advantage of their relationship and bring out the best in each other. This article highlights the value of an efficient collaboration which can improve the quality of the documentation.

With the increasing clarion call to attune technical content to be customer-oriented, we're constantly identifying ways to understand our consumers better. While we look for external resources, such as direct feedback, let's also look at a rich repository of data within the company to be used in this pursuit.

In this presentation, Stefan Gentz will give insights from the Adobe Technical Communication Worldwide Survey 2019/2020. TechComm professionals from 60 countries participated in the survey. He will discuss the driving factors for enterprises around the world when it comes to technical communication.

Implementing DITA with a small team of technical writers does not have to be expensive or difficult to set up.

When UX and information development partner together, the result is a stronger, richer product experience because content is an important part of that experience.

You’ve probably heard about Acrolinx and Schematron for evaluating content for style and grammar. These tools work well for structured content, but what about API documentation that is outside of your control? Can you still provide feedback to engineers and developers to ensure that they follow corporate writing guidelines? You can apply your same style and grammar rules using the Vale linter, which works on API documentation formats, such as Markdown.

At VMware, we needed to know whether our content met user needs, what was missing, and what we should change. We ran simple to complex usability tests, which enabled us to gather data, recommend best practices, iterate, and create educational materials that support our writers to do it too. We discovered that we can improve the user experience! Discover what your users think by testing your content! To learn more, this article is for you!

There is a lot of confusion about how difficult writing in DITA can be and this article’s goal is to clarify the challenges for information developers and technical writers alike. It is part 1 of 3 on learning how to author in DITA which focuses on Learning reinforcing best practices and highlighting unconscious practices and knowledge the authors are already familiar with.

Dawn's director's column compares travel experiences to user experiences with technical content and their customer journeys.

Before you proceed, think about how the conversion could help you derive the benefits of DITA that you expect.

In this presentation, we will explore a few collaboration scenarios that show how to implement continuous improvement loops for published documentation, how to integrate documentation as part of the product development workflow, and how immediate collaboration can take place.

Three things which will increase the value of your content strategy--articulating how your vision will accomplish your specific goals and ultimately save money for your company, creating a set of compelling slides tailored to your stakeholder audiences, especially upper management, and using the terminology of your organization's mission statements to frame the discussion.

Jim will begin with an overview of the localization process, of how content flows across systems and organizations. In this context, we will discuss techniques and also wins and pitfalls in automating and streamlining the localization process.

A recap of the BOTI 2019 Conference including comments from the attendees and highlights of the presentations.

We will analyze a working Docs as Code setup that will be freely available on GitHub afterward so attendees will be able to fork it, work with it, gain a deeper understanding and apply these concepts into their own documentation projects.

A step by step guide to getting started with Schematron and Schematron Quick Fixes.

In this webinar, Sabine Ocker discusses some top hidden costs and provide insights on how to identify, plan for, and mitigate the impact of common examples such as changes to project scope, lack of appropriate standards, and content conversions.

How people learn and consume information is swiftly changing and we, as technical communicators, must adapt. This article explores changes over the past decade in how people live and think, how these changes impact our role as technical communicators, and how UX and a modernized approach to content can help us thrive in this new world.

Digital Natives have fundamentally different content requirements and preferences than digital immigrants. In order to be able to meet those needs, Technical Communications organizations must gain deeper understanding of user preferences such as visual learning, user generated text, and mobile device access via multiple first hand feedback mechanisms.