紙の本の価格: | ¥5,149 |
割引: | ¥ 1,016 (20%) |
| |
Kindle 価格: | ¥4,133 (税込) |
獲得ポイント: | 41ポイント (1%) |
無料のKindleアプリをダウンロードして、スマートフォン、タブレット、またはコンピューターで今すぐKindle本を読むことができます。Kindleデバイスは必要ありません。
ウェブ版Kindleなら、お使いのブラウザですぐにお読みいただけます。
携帯電話のカメラを使用する - 以下のコードをスキャンし、Kindleアプリをダウンロードしてください。
Every Page is Page One: Topic-Based Writing for Technical Communication and the Web (English Edition) Kindle版
The Web changes how people use content; not just content on the Web, but all content. If your content is not easy to find and immediately helpful, readers will move on almost at once. We are all children of the Web, and we come to any information system, including product documentation, looking for the search box and expecting every search to work like Google. There is no first, last, previous, next, up, or back anymore. Every Page is Page One.
In this ground-breaking book, Mark Baker looks beyond the usual advice on writing for the Web, and beyond the idea of topic-based writing merely as an aid to efficiency and reuse, to explore how readers really use information in the age of the Web and to lay out an approach to planning, creating, managing, and organizing topic-based documentation that really works for the reader.
- 言語英語
- 出版社XML Press
- 発売日2013/12/3
- ファイルサイズ6823 KB
登録情報
- ASIN : B07PPXSN8W
- 出版社 : XML Press; 第1版 (2013/12/3)
- 発売日 : 2013/12/3
- 言語 : 英語
- ファイルサイズ : 6823 KB
- Text-to-Speech(テキスト読み上げ機能) : 有効
- X-Ray : 有効にされていません
- Word Wise : 有効にされていません
- 付箋メモ : Kindle Scribeで
- 本の長さ : 372ページ
- カスタマーレビュー:
他の国からのトップレビュー
Because of my dual role as a database specialist and technical writer, I know Microsoft SQL Server documentation very well, but it was not after reading this book that I realized why this documentation is so well structured and comprehensive, and why this type of writing is a pattern to follow. The same can be said about Wikipedia, which is an example used in several chapters. This book provides a compelling argument against traditional books or book-style user guides and manuals, and explains the fundamentals to write documentation your users and customers will find -finally- useful. Isn’t this exciting enough?
The only thing I missed was more examples. If you open the book this may seem contradictory, because it has plenty of examples and metaphors that makes the explanation easy to follow (I particularly liked the “recipe” example), but I am referring here to examples using “real” technical documents. In this way, I think it would be great to have some examples about how a chapter from one “traditional” manual can be rewritten in an "EPPO way”, or how DITA and EPPO can both work together in a topic. Yes, I know after reading the book this is not as simple as it sounds! :)
Overall, this is an excellent book, well thought and well researched, and plenty of fresh ideas in a field that is particularly stagnant and, in most of the cases, lacks innovation. As part of my development into the technical writing and communication field, I have read several books about the subject, and this is by far the most revealing and helpful one.
If you are reading this and have something to do with technical writing, buy this book. This small investment may have a great impact in the way you think and work around technical writing.
Could have been much tighter. Seemed to be a lot of repetition, which would be resolved, in part, with better organization.
I wish it would have suggested some ways to measure the success of an EPPO initiative. Are there Google analytics that are useful? What else?
Even as an appendix, an example - from beginning to end - would have been worthwhile. It's one thing to show examples that already meet EPPO standards, but it could have been more meaningful to show a before and after accompanied by an explanation that anticipates the real-world issues that may come up in applying these principles.