This session will help participants understand how to write and submit a manuscript for publication in Technical Communication. It covers the types of articles the journal publishes, its audience, and suggestions for choosing topics, doing research, and preparing a manuscript.
The Books by Users program, SAS Institute’s acquisitions program, serves a twofold purpose: helping SAS software users with book ideas turn their ideas into high-quality books about the SAS System; Providing Users with books about SAS Software to supplement primary documentation produced by in-house writers. This paper gives an overview of the Books by Users program and examines its operations and growth over the past three years. It offers tips both for companies building acquisitions programs and for authors hoping to interest publishers in their book ideas.
This paper represents an international study of IBM customers in the U. S., England, and Germany to see what effect the layout of a technical document has on usability for an audience of Americans and Europeans. The results indicate that while Americans and Europeans want most of the same usability features, they do not agree on all features. Communicating effectively with readers from different countries requires that writers work closely with international readers who represent the readers of their document; interview people who represent their audience; work with a document designer before starting the first draft; and test the draft document on representative users.
Drawing on experience in bringing the material of many clients to the Internet and CD-ROM, this paper describes how to develop an intelligent online document repository. The paper describes how to plan scalable solutions, how to manage production, what to watch out for, and how to maintain your collections into the future.
When you hear about XML publishing, you mostly hear about databases, workflow tools, and content management systems. These are typically costly systems aimed towards the information management needs of larger enterprises, where the sheer volume of information pumped through these systems provides a fairly rapid return on investment. This fosters the perception that you need one of these complex, expensive, enterprise solutions to use take advantage of the modularity and flexibility of authoring in XML. That is simply not true. You can realize the benefits of publishing from modularized XML, without the expense of an enterprise publishing system, by implementing the authoring environment on top of nothing more than your operating system's file system. Although this environment is not adequate for enterprise publishing needs, it is more than adequate for the needs small writing teams, businesses with a limited number of related products, proof-of-concept demonstrations, and even home users. The AIC documentation group at Cisco Systems has implemented such an authoring environment. We have been able to reuse and re-purpose modular, XML-based information without implementing a database back end. By examining how the AIC team implemented XML in a flat-file environment, you will see: * the decisions you need to make before implementing a flat-file XML system * the trade-offs, drawbacks, and pitfalls of implementing a flat-file environment (as compared to a database publishing environment) * the benefits of XML that are still available, even without the database * a migration path to a more traditional publishing environment
Success in the marketplace depends on delivering the right messages to the target market. A regular, consistent “drumbeat” can be an extremely effective way to deliver messages. At the IBM® Network Computing Software Lab, I have developed a traditional newsletter and an email bulletin for delivering our marketing messages regularly and consistently. Though they share the same objective, these two instruments are very different in content and format – reflecting the fact that they are designed to maximize the opportunities and overcome the limitations of their respective media.
Moving to Electronic Delivery of Documentation” includes information about the fundamentals of electronic documentation, case studies, what to expect, how to research, identify, and implement a process for moving from an exclusively hard copy documentation development and delivery process to electronic documentation development and delivery.
Discusses some critical methodologies we may wish to use in order to make sense of the changes which have occurred in mass media post-1976. It is rather important to understand this history -- the reasons we think the current Internet is confusing is precisely because of the reorganization it represents in the balance of power between ruling interests in our society. In the end, I argue, the Internet is another step in the increasing influence of media and publishing interests, and it is important to read news in online space as part of that history.
After centuries of focusing on the bookstore as the “customer,” success in the digital age will require publishers to focus on the ultimate consumer. Given the enormous flexibility and “mass customization” that digital technology makes possible, the future business model for book publishing can best be understood as providing a service rather than a commodity. And “value” is a co-creation—the publisher responds to the specific content needs as defined by the customer for each transaction.
The production of books that suit a publisher’s guidelines and find their appropriate market requires a perfect match of publisher and author. This panel discussion will explore the dynamics of authors and publishing professionals working to achieve that match. Acqui-sitions professionals and a technical book writer and editor will pro-vide information about what publishers expect from manuscripts and how they work with authors, suggest how writers can find the right publishers for their books, and describe how one successful techni-cal book acquisitions program was built. The discussion should be of interest to technical writers and editors hoping to publish and to publishing professionals in the trade or college book market.
Without detouring into software and platform studies, I will simply state that it is beyond time that digital archives of texts begin to adhere to the methodologies learned from Web 2.0 activities and applications (for we are now in a post-2.0, a Web n.0, time) and embrace the concepts of layering shared data and user-generated or user-customized content onto the core curated data within the archive.
Illustrations were and are integral to the "Alice in Wonderland" series of books. John Tenniel (the illustrator of the definitive editions) changed how people read the "Alice" books.
Technical communicators and photographers achieve successful communications results through open, honest working relationships. To establish and maintain a good working relationship, each party must openly communicate with each other, understand the project requirements, focus on the project objectives, and work together as a team before, during, and after the shoot. Benefits to both the technical communicator and photographer include customer satisfaction, mutual referrals and partnership opportunities, and professional achievement.