I am trying to evangelize the 10/20/30 Rule of PowerPoint. It’s quite simple: a PowerPoint presentation should have ten slides, last no more than twenty minutes, and contain no font smaller than thirty points. While I’m in the venture capital business, this rule is applicable for any presentation to reach agreement: for example, raising capital, making a sale, forming a partnership, etc.
Learn from Dr. JoAnn Hackos, President of Comtech Services, Inc. and Director of the Center for Information-Development Management (CIDM), how to evaluate your legacy content and assess how close you are to the DITA standard. Understand the decision-making process you need to follow to prepare for the conversion process. Consider if your team should first restructure your content in your current tool environment or wait to restructure and rewrite following conversion.
XML topic-based documentation enables consistency, reuse, conditional publishing, separation of content and styling, and more. A good XML solution makes it easier for the authoring teams to move to XML authoring, providing structured templates, embedded editors, maintaining links and metadata, and adding collaboration features such as workflows.
The ability to build interactions that support, enable, and improve communication is a valuable skill for help developers, Web-site designers, multimedia content developers, information-rich user interface designers-anyone who designs and develops information to be used online. This paper presents the basics of interaction design for information products and describes some basic underlying human factors and user-interface design principles.
This presentation is for beginning to intermediate users of DITA. It's based on my experience with projects on which I'm project manager, information architect, and writer.
Systems engineering is moving away from specially-designed and built systems to integration of commercial off-the-shelf (COTS) hardware and software. COTS brings new challenges to technical communicators. In the past, we found all our information in-house, now it comes from many sources. We must change our process from pure development to information integration, and we must be part of the COTS selection process.
Personalization is coming to technical communication, and the results may not be pretty. n offering the individual an opportunity to pick and choose among XML content objects, we risk causing confusion when the organization of the site appears to shift, and familiar landmarks disappear. Critical content may become invisible to the user. The very process of creating preferences, custom options, or an entire personal profile adds a complex distraction that many users may resent, because it takes them away from their original task for so long that they forget what they were doing. Even advanced search mechanisms, which promise to pinpoint the exact information object the user wants, risk baffling users with their own complexity.
Before coding any part of a hypermedia computer-based training (CBT) system, designers need to decide how much control their users should have over their individual paths through the system. Designers can choose from three different levels of control within a hypermedia CBT system: complete computer control, complete user control, and adaptive computer control. Each level of control is suited to different types of audiences and system goals. Current research provides some guidelines for designers—showing which types of audiences and system goals are suited to which methods of control.
Cisco Systems IOS ITD Documentation group had a requirement to move to the dynamic delivery of documentation to their customers. This meant that the documentation had to be redesigned using a component architecture, moved to XML, and delivered through a personalization engine. This session discusses this process and the results.
“Single source” has come to mean many things to many different people. The basic distinctions are two: (1) distributing the same content in multiple formats and (2) distributing complementary content in the most appropriate medium. The two concepts are not mutually exclusive, i.e., you may have an information strategy that encompasses both ideas. Each methodology has its own advantages, suitability, and requirements. Distributing complementary content in the most appropriate medium requires research and planning, and often results in more effective documentation.
DITA maps provide a mechanism for ordering topics and creating a topic hierarchy. Because DITA maps consist of lists of references to topics, you can reorganize the content in a deliverable simply by changing the order of the topic references. You can create different maps referencing the same source topics to create two deliverables to meet different users' needs.
This talk will explain how to use ecological design, which is an expansion of ethnography, to leverage both the rich local information from case studies, and a wider sociological perspective to take account of global realities.
This webcast is for those publishers who have made the decision to pursue digital channels for their content. What tools are out there? What do all those acronyms mean? How can publishers implement new strategies without disrupting current workflows? Here we explore the alphabet soup of digital publishing, sort out the tools that are most useful, and help publishers find some solid ground.
The XML format was developed in the 1990s in a hope to develop a universal format for documents, replacing proprietary binary formats that couldn’t integrate with one another. And we’re beginning to see the results. In this talk, Dr. Geoffrey Sauer will present an introduction to XML, with an overview that will explain to people who’re not familiar with it why this is a good thing, and how we can begin to use XML formats to our advantage as technical communicators.
This paper explains what e-commerce is and the two different types of e-commerce. The advantages of e-commerce are covered along with the steps needed to setup e-commerce. The different forms of advertising over the internet is covered next. How internet security works is covered in detail including the use of digital certificates and SSL (secure sockets layer). The processing of payments over the internet is the last subject covered including the different ways to pay and how credit card transactions are processed.
In the evolving and demanding world of telecommunications, Tellabs supports telecom service providers with the design, development, and deployment of wireline, wireless , and cable solutions worldwide. But with each unique solution deployment requires knowledge transfer from engineers to field service staff to ensure a smooth system upgrade. Learn how Tellabs' New Product Introduction group used DITA to transition to customer-centric writing. *What are the key things the organization as a whole should keep in mind regarding processes?"
This article revisits three past articles about the implications of hypermedia in the 21st century. Each August, the ACM Journal of Computer Documentation reprints a classic article, book chapter, or report along with several analytical commen- taries and a response by the author of the classic document. In this context, a 'classic' document means one that was published at least five years ago but is no longer in print. It also means one that raises issues of lasting importance to the profession.
“SGML is too complex and too costly to implement widely. ” This criticism has often been leveled at the Standard Generalized Markup Language. Mainstream SGML, a new open architecture, challenges that view. Traditionally, implementation has required companies to invest heavily in training. Authors had to learn how to create documents using complex SGML syntax. This method was time-consuming and yielded a slow return on investment. The Mainstream approach to implementing SGML uses resources that already exist in a company. Mainstream SGML provides an alternative to costly, complex native SGML document management systems. This workshop shows you how you can use mainstream SGML to successfully implement SGML in your mainstream business and publishing processes.
The information architect focuses on how things are structured within the user experience: looks “up” to the user interface – how the navigation and page layout convey the structure; looks “down” to the content management to make sure it can enable to right user experience.