Notes from 54th International STC Conference
Minneapolis, Minnesota, May 13-16, 2007

Web 2.0 101:
Understanding Web 2.0 and Its Impact on Technical Communication

Scott Abel

The presenter's variegated background includes experience as a nightclub DJ, investigative reporter, technical writer, trouble-maker, entrepreneur, and "evangelist" (a.k.a., an advocate for change).

Session Description: The Semantic Web is coming and it's bringing major changes to the ways that people create, manage, deliver, consume, and share technical information. This session introduced Web 2.0 and its tools and technologies, and examined how they are changing the landscape of technical communication. It showed how Web 2.0 methods make it possible for technical communicators to deliver "content as a service" and to personalize technical content in useful and exciting new ways.

• User expectations are driving rapid change in the technical communication field.
• Content is everywhere, and managing it is getting out of hand.
• To share content, you have to give it some predictability (that's where structure comes into the picture)
• Web 1.0 is publishing to the web: users surf and "read stuff" (if they can find it). Content is published to websites: writers create content to fill these web places. The medium is the message.
• Web 2.0 is oriented toward bringing service to the web: it helps users to "do stuff" rather than read stuff.
• Web 2.0 syndication allows users to remix content: structure content makes it possible.
• Really simple syndication (RSS): an XML standard; provides structure and semantic value to content.
• Without style, RSS feeds provide a less-than-desirable user experience.
• With style, RSS feeds provide a valuable user service.
• Publish/subscribe model: extends the reach of content; users reuse content in unlimited ways.
   
• Publish: write it once and let go of control; content is both human and machine readable.
• Subscription services provide relevant information, delivered how, when, and where users want it.


• Proprietary code wrapped around content keeps it from being widely disseminated. New business model may call for more open distribution of information.
• Syndicated content from STC RSS feeds can enable other communities to present a much more comprehensive web site than would ordinarily be possible with the limitations of volunteer "bandwidth." This keeps the satellite sites fresh with auto-generated content, via the RSS feed.
• http://www.indeed.com, specifying geographic location and profession, is an excellent job posting site.
• Write it once, publish it many times.
• Blogs: two new blogs are created every second of every day. (Term comes from "web log," and articles are called "posts.")
   
• Blogs for documentation? Blogs provide a low-cost entry point; blogs that support DITA are being developed now.
• Structured blogging allows us to create structured XML content; uses microformats (granular structured content).
• http://www.upcoming.com tracks events.
• http://www.incredibooks.com makes structured blogging so easy that even kids are doing it (and earning money for their efforts).


• How can you use structured content internally on an intranet to increase productivity?
• Wikis: web-based collaboration tools that support user-generated content; users can consume, create, correct, corrupt, and cut content.
   
• There are even DITA-based wikis that impose underlying structure via templates—and might therefore be appropriate for documentation.
• Wikipedia, by and large, contains legitimate content despite the open access and constant change. There have been cases of manipulation which have gotten media attention.


• Podcasts: Anyone can make bad audio faster than ever!
   
• Top-quality podcasts can be a very useful tool. Technical writers struggle to find legitimate uses; users benefit from the usability. To use audio for documentation requires "chunking" by sub-topic, keeping individual podcasts small. Otherwise, it is virtually useless because you can't search and zero in on a specific topic. Podcasts have obvious accessibility value for blind and visually impaired users.


• User-generated content: users are creating their own documentation whether you want them to or not.
• Video documentation: user expectations are changing rapidly.
• Documentation: users helping users; software forums with content provided by customers.
• Social networks: users share with one another in uncensored online communities (e.g., LinkedIn). LinkedIn is great for job search.
• Online resources
   
• http://www.thecontentwrangler.com contains Scott's visuals from this presentation.
• http://www.slideshare.net is another great site.
• http://www.confabb.com tracks conference presenters and their performance.


• In soliciting user feedback, it's important to give them something.
• The Semantic Web, or Web 2.0, seeks to leverage the internet to deliver service.
• http://pipes.yahoo.com/pipes/ is designed to search for almost anything under user-defined parameters.
• To conduct advanced searches, you must think non-linearly (like a programmer), not linearly (like a tech writer!)
• Old information, new view: looking at content from all angles helps us make meaning of content; new technologies make content accessible in meaningful ways.
• Timeline organized chronologically.
• Pandora customizes music recommendations through streaming internet radio.