Last week we launched three YouTube channels with more than 30 videos on Arbortext and XML publishing.
So you’ve just been told to create a mobile version of your product’s help system… Can we revise content written for a large screen to fit on an iPhone screen? Can we cut it? Is there a point at which the two options are effectively the same? In either case, how do we decide what to give up? Can that “lost” material be made available somewhere? In this presentation, we’ll discuss these issues and look at a real example, a very early multimedia presentation about US history in which the presenter boiled 70 pages of content down to a few dozen paragraphs and decide whether it worked.
In this session, we’re going to talk about the Side-By-Side panel in Styler. We’ll talk about what it means, how best to use it, and how to make it work for you. We’ll show you how to make it look like you’ve got a graphic embedded in a paragraph, with text spilling around it, through the simple side-by-side mechanism. This is but one application of the side-by-side technology, but it’s a good one to get your feet wet with.
This session will explore data visualization and literacy, focusing on various techniques to conceptualize narratives and create visualizations. Along with gaining a more comprehensive understanding of data visualization, participants will be introduced to new ways of managing, analyzing, and visualizing data sets, as well as textually expressing underlying relational content.
One of the hardest things for technical communicators moving into an XML authoring environment is that you’re learning two things at once: A new UI and a new technology. In this session, we’re going to take a step back and walk through the Editor UI. There are a lot of features right at your fingertips that make it easy to get started. We’ll show them to you and give you a chance to see Arbortext Editor in a neutral context.
To DITA or Not To DITA. DITA isn’t the right answer for every situation. In this session we’ll discuss the differences between the two doctypes to give you a foundation to decide between them.