Technical Writing Book

Writing Book

Are you looking for good books on technical writing, style guides, technical communication and DITA? The pages in this category are part of the Professional and Technical Writing book. Business & Technical Writing books. This is a collection of books on technical writing and technical writing careers. Writing is education through the written word.

Which are the best technical writing resources?

Classical and general literature about good and simple writing (like "The Elements of Style" by Strunk and White or "How to World Well" by William Zinsser) is of course great. But if you are writing a technical documentation such as a users handbook or an installer handbook, these ledgers will not help you.

Specifically designed Microsoft Manual of Styles and Handbooks with a Handbook of Technical Writing by Alred et al. for each important approach would help a little, but since they present information in a somewhat incomplete way, or they speak to the kind of formating rule that may not be applicable to your projects at all, they are probably not what you need.

One can' t literally literate these ledgers (which weren't conceived and wrote in such a way that they can be literally literate at once anyway) and then, for example, just take a seat and start writing a great user's guide. They need to study textbooks that address the issue of writing technical documentation with many in-depth samples, information about the compilation of the various elements of a paper and some procedures for writing.

Therefore I suggest the following extra ledgers, which I have had in my bookshelf for years and consult frequently: {\a6} "Why Not Say It Clearly" by Lester S. King, M.D. Although out of stock, try to get a copy of this book in any case. He is a medicinal novelist, a speciality within the general theme of technical writing, and as his last name implies, he really is a king of technical writing!

Though slender as a book, you will certainly be a much better author once you finish this book and think about the samples it provides. How to Watch a Manual" by Elizabeth Slatkin. Planning, designing, writing, reviewing and creating a handbook. There is even a section on page layouts technologies (and you would be surprised how much page layouts you will make as a technical editor).

What's with this book? Technical Writing is increasingly writing for an increasingly global public. The majority of technical documentation is localised into different tongues. To know how to work for an global public is a must for all technical authors theseadays. This is the best resource to help you get started with the web with thousands of samples.

It breaches the presumption that a technical file is a paper "book". Today there are as many technical papers on the web as there are in print format. If you ever want to be a technical editor and want to publish on the web, please have a look at this landmark book. The Agile Documentary by Andreas Ruping.

It is a fairly sophisticated book for those who work in an agile (software production) milieu. Although the peloton is moving too fast and changes to be correctly covered by a book from 2003, it still offers a great bird's perspective on the whole area.

A great entry into a very technical (and well-paid) sub-discipline of technical documentary. This is Barry J. Rosenberg's "Technical Writing for Engineers and Scientists". Instructions for writing a great handbook with sections about the public, documentary maps (which you won't find in many other books), how to spell phrases, sections, lists, laboratory papers, PCT presentation and much more.

{\a6} (7) "How to Watch User Documentation" von Edmond H. Weiss. It is an old book that is outdated in its cover of many topics such as page and book sizing. However, some of the chapters, such as creating a storyboard or writing a section or section heading, are still excellent.

It is also invaluable how to create and organise "modules" of a technical documentation. You' re going to reject half of this book because advanced technologies have made this section completely inapplicable. Principal Investigator (8) "Technical Communication" by Mike Markel. It' the bestselling technical writing classics for a good cause - it's as good as it should be!

Full of great how-to-do samples on all imaginable topics of technical writing, this is a book that I have gladly advised over the years. This is a must for your technical writing libraries. {\a6} (9) ªEditing Technical Writingº by Donald C. Samson, Jr. Write is one thing, edit is another. Any good technical author is not a good technical journalist, believe me.

It is one of the few and valuable works that go into the technical editorial detail (text and images) with samples. There' s an answer code for the practice question and even a section on how much you have to pay for your writing (also obsolete, of course). Twenty years ago, Peter Kent's "Making money in technical writing" was one of those few publications dedicated to the technical writing world.

We give gold hints and techniques in his book on how to start up your free-lance technical writing shop, how to commercialize your utilities, how much to boot (refurbished in) and how much you can expect to making (also refurbished). {\a6}(11) "Create Technical Manual" by Gerald Cohen. Like the sub-title says: "A step-by-step guide to write user-friendly statements.

" It is good to recall from times to times that technical writing is about writing statements. It is one of my primary resources for writing clear step-by-step explanations, even though some of the graphical samples are out of date (as most is quickly obsolete in this mad era of uninterrupted advancement and innovation).

Process-and-product technical writing by Sharon J. Gerson and Steven M. Gerson. It is a book in the same genre as Mike Markel's classical work. It is well-formed, well-written, and covered a great deal of ground by concentrating on single technology lecturing product such as CVs, flyers, leaflets, newsletter, reports, suggestions and even orals.

Writing and Speech for Technical Professionals" by Martin S. Roden and Teresa E. Murphy. It is an outstanding book that shows how to talk, not necessarily how to create technical documentation. Only after page 200 do the writers get to writing a technical paper.

AIan S. Pringle and Sarah S. O'Keefe, Technical Writing 101. This is another book you need to have on your bookshelf, and it is by two well-known technical authors. It is a "guide for the design and creation of technical documentation", as the sub-title says, and it keeps its promises.

In the second issue, there are also chapters on the latest technology in the field of structured authorization andML. Last but not least, if you are looking for a complete on-line tutorial in the handicraft of technical writing, technical writing and editorial, I would like to suggest my own bestseller course: https://www.udemy. com/technical-.....

Mehr zum Thema