<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Quality Web Content</title>	<link>http://tc.eserver.org/publisher/Quality_Web_Content</link>
	<description>A listing of works published by Quality Web Content in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Quality Web Content</title>
		<link>http://tc.eserver.org/dir/Quality_Web_Content</link>
	</image>
	<item>
		<title>The Paper Mountain Goes Online</title>
		<link>http://tc.eserver.org/26158.html</link>
		<guid>http://tc.eserver.org/26158.html</guid>
		<description>Ample research has proved that companies can save many thousands of dollars by rewriting key documents in plain English. Poor communication on the Web and intranet are squandering the time and money of many an organisation.</description>
	</item>
	<item>
		<title>Why this Word &apos;Content&apos;?</title>
		<link>http://tc.eserver.org/26157.html</link>
		<guid>http://tc.eserver.org/26157.html</guid>
		<description>Since the world went online we see this word &apos;content&apos;, meaning the stuff that is published on a website or intranet. Why do we need this word? It&apos;s all to do with the dominance of technology.</description>
	</item>
	<item>
		<title>Accessible Graphs and Charts Online</title>
		<link>http://tc.eserver.org/26154.html</link>
		<guid>http://tc.eserver.org/26154.html</guid>
		<description>Most government web writers are knowledgeable about alt-text by now... or at least semi-knowledgeable. But sometimes, alt-text is not enough.</description>
	</item>
	<item>
		<title>Content for Tourism and Hospitality Sites</title>
		<link>http://tc.eserver.org/26146.html</link>
		<guid>http://tc.eserver.org/26146.html</guid>
		<description>My worst experiences with hospitality sites have been to do with vague location, online timetables, poor follow-up communication, and out of date information. I have wasted days as a result, which I hate.</description>
	</item>
	<item>
		<title>Dodge the Grammar Traps</title>
		<link>http://tc.eserver.org/26151.html</link>
		<guid>http://tc.eserver.org/26151.html</guid>
		<description>You don&apos;t have to swallow a grammar book to write correctly. If you can just avoid ten serious and very common traps, your chances of making a grammar mistake drop dramatically.</description>
	</item>
	<item>
		<title>Estimating the Cost of Writing and Editing</title>
		<link>http://tc.eserver.org/26153.html</link>
		<guid>http://tc.eserver.org/26153.html</guid>
		<description>The cost depends on how long and complex the document is, and how much editing is required. Most editors have a fixed hourly rate, and will quote for a job after they have studied the document. Skilled wordsmiths usually charge more per hour, because they do the job faster. When you find a fine wordsmith, handle with care. They are not exactly thick on the ground.</description>
	</item>
	<item>
		<title>It&apos;s Only Words</title>
		<link>http://tc.eserver.org/26149.html</link>
		<guid>http://tc.eserver.org/26149.html</guid>
		<description>Today, at least in this country, most government and corporate organisations are well aware that words online matter. A lot. Even when the technology is perfect, words can make or break the success of a web site or intranet. So sure, words now get due respect in many quarters.</description>
	</item>
	<item>
		<title>Keep Spelling Consistent With a Style Sheet</title>
		<link>http://tc.eserver.org/26152.html</link>
		<guid>http://tc.eserver.org/26152.html</guid>
		<description>Consistent spelling and punctuation increases your website&apos;s credibility. Often it&apos;s your decision: &apos;inhouse&apos; or &apos;in-house&apos;, for instance? Either one is correct, but you must use the same punctuation throughout.</description>
	</item>
	<item>
		<title>Link Location That Works</title>
		<link>http://tc.eserver.org/26141.html</link>
		<guid>http://tc.eserver.org/26141.html</guid>
		<description>Where to put links on a web page? That&apos;s a standard dilemma for content writers. Best to establish a policy and make sure all writers on your site follow it. That has an added advantage of standardising the &apos;look&apos; of your pages.</description>
	</item>
	<item>
		<title>National Policies for Government Web Writers</title>
		<link>http://tc.eserver.org/26144.html</link>
		<guid>http://tc.eserver.org/26144.html</guid>
		<description>Every country has its own requirements for public sector web sites. Legislation and policies vary greatly, and express an attitude. I base my Quality Web Content workshops for government web content writers on the policy of the country concerned. Some countries consider that an accessible site requires accessible writing. Others don&apos;t.</description>
	</item>
	<item>
		<title>A Problem of Category</title>
		<link>http://tc.eserver.org/26143.html</link>
		<guid>http://tc.eserver.org/26143.html</guid>
		<description>What is this thing called web content? I fear most people still believe that it&apos;s something as trivial as a whitebait in a bucket. Fresh whitebait is transparent. If you don&apos;t look hard, you can only see the container, and not the thing contained.</description>
	</item>
	<item>
		<title>Seven Tests for Quality Web Content</title>
		<link>http://tc.eserver.org/26148.html</link>
		<guid>http://tc.eserver.org/26148.html</guid>
		<description>Do these quick tests on every web page you write or edit. Use the tests for quality control of web content.</description>
	</item>
	<item>
		<title>Those Pesky Index Pages</title>
		<link>http://tc.eserver.org/26155.html</link>
		<guid>http://tc.eserver.org/26155.html</guid>
		<description>Every directory on the site must have an index page. The index.htm or index.html page is a standard requirement for every directory on every site.</description>
	</item>
	<item>
		<title>Top of the Top of the Top of Search Results</title>
		<link>http://tc.eserver.org/26150.html</link>
		<guid>http://tc.eserver.org/26150.html</guid>
		<description>Virtually every search engine and directory is now associated with some kind of paid solution, and it is tempting to see them as an easy way to get top ranking for your web site.</description>
	</item>
	<item>
		<title>Web Writing Guidelines Backed by Research</title>
		<link>http://tc.eserver.org/26145.html</link>
		<guid>http://tc.eserver.org/26145.html</guid>
		<description>In the past, I have been bothered by the lack of a coherent summary of research on web writing. In November 2003 the problem was solved by the (US) National Cancer Institute, for the time being, at least.</description>
	</item>
	<item>
		<title>What Shall We Do With the Publications?</title>
		<link>http://tc.eserver.org/26142.html</link>
		<guid>http://tc.eserver.org/26142.html</guid>
		<description>Publications pages are often among the most popular pages on web sites, particularly government sites. But this handy convention has turned into a problem.</description>
	</item>
	<item>
		<title>Woes of the Intranet Writer</title>
		<link>http://tc.eserver.org/26147.html</link>
		<guid>http://tc.eserver.org/26147.html</guid>
		<description>Some main points submitted by readers about writing for intranets, in quotation marks or paraphrased.</description>
	</item>
	<item>
		<title>Combining Paper and Electronic Communication</title>
		<link>http://tc.eserver.org/26137.html</link>
		<guid>http://tc.eserver.org/26137.html</guid>
		<description>A few ideas for ad hoc workforce communication that must be conveyed on paper as well as electronically.</description>
	</item>
	<item>
		<title>Corporate Pages 2002-2004 (Part 1)</title>
		<link>http://tc.eserver.org/26139.html</link>
		<guid>http://tc.eserver.org/26139.html</guid>
		<description>In 2002 I saved nine sample web pages from corporate web sites, for teaching purposes. On 1 June 2004 I took another look at those pages or their current equivalent. No way is this a systematic study or even a random sample. But the results are interesting and do reflect trends in corporate web sites.</description>
	</item>
	<item>
		<title>Corporate Pages 2002-2004 (Part 2)</title>
		<link>http://tc.eserver.org/26138.html</link>
		<guid>http://tc.eserver.org/26138.html</guid>
		<description>When training web authors, I prefer to use good examples of their kind, so these must have been either typical or among the best I could find at the time. However, they certainly did not contain content to skite about.</description>
	</item>
	<item>
		<title>Draft 2 of Web Content Accessibility Guidelines</title>
		<link>http://tc.eserver.org/26131.html</link>
		<guid>http://tc.eserver.org/26131.html</guid>
		<description>It&apos;s time to take a look at the working draft of WCAG 2.0. You&apos;ll see a fresh approach to a formidable challenge.</description>
	</item>
	<item>
		<title>How to Write a Summary, and Why</title>
		<link>http://tc.eserver.org/26130.html</link>
		<guid>http://tc.eserver.org/26130.html</guid>
		<description>The first text in most web and intranet pages should be a summary of 1-2 sentences. That&apos;s a good rule of thumb. The starter-summary has several important functions.</description>
	</item>
	<item>
		<title>Say When and Where</title>
		<link>http://tc.eserver.org/26140.html</link>
		<guid>http://tc.eserver.org/26140.html</guid>
		<description>Certain expressions in web content get users all discombobulated. Relative expressions of time and place need an anchor, a key, right there in the text. Some common confusers follow. They would not be a problem in other circumstances. But on the Web or intranet, every page must make sense in isolation.</description>
	</item>
	<item>
		<title>Stanford&apos;s Web Credibility Study</title>
		<link>http://tc.eserver.org/26134.html</link>
		<guid>http://tc.eserver.org/26134.html</guid>
		<description>In this study, 2,684 people evaluated the credibility of two live web sites randomly assigned from one of 10 content categories. A total of 100 sites were assessed. The Stanford credibility team analysed the comments to discover how consumers evaluated credibility online.</description>
	</item>
	<item>
		<title>Stop Creating ROT (Redundant, Outdated and Trivial Content)</title>
		<link>http://tc.eserver.org/26133.html</link>
		<guid>http://tc.eserver.org/26133.html</guid>
		<description>Redundant, outdated and trivial content (ROT): you&apos;re soaking in it. First and second generation web sites and intranets are full of ROT. It&apos;s almost inevitable when you have a web site but no system for reviewing content regularly.</description>
	</item>
	<item>
		<title>Two Kinds of Keywords</title>
		<link>http://tc.eserver.org/26136.html</link>
		<guid>http://tc.eserver.org/26136.html</guid>
		<description>I have long wondered why government web sites all over the world tend to use metadata of several different types jumbled together and overlapping. For example, pages with two description metatags or two or three title tags are common. I suspect that most of the replication and confusion has developed for historical reasons.</description>
	</item>
	<item>
		<title>When is a Long Document Not a Long Document?</title>
		<link>http://tc.eserver.org/26135.html</link>
		<guid>http://tc.eserver.org/26135.html</guid>
		<description>Change is upon us, whether we like it or not. HTML is the default technology for accessible documents online according to the W3C and most government standards. That means goodbye to the easy solution of flinging scores of long documents on to a web site as Word or PDF files.</description>
	</item>
	<item>
		<title>Eyes Top Left: Lessons from Eyetrack III</title>
		<link>http://tc.eserver.org/26129.html</link>
		<guid>http://tc.eserver.org/26129.html</guid>
		<description>Where do your eyes go when you read articles on the Web? What do you notice, and what do you miss? The upper left quarter of the screen gets the most attention, according to the Eyetrack III research of The Poynter Institute, the Estlow Center for Journalism &amp; New Media, and Eyetools.</description>
	</item>
	<item>
		<title>Standards for Online Content Authors</title>
		<link>http://tc.eserver.org/26128.html</link>
		<guid>http://tc.eserver.org/26128.html</guid>
		<description>The standards on this page include non-technical standards relevant to all web authors and technical standards relevant to some web authors.</description>
	</item>
	<item>
		<title>Standards for Online Graphs</title>
		<link>http://tc.eserver.org/26127.html</link>
		<guid>http://tc.eserver.org/26127.html</guid>
		<description>A government organisation in New Zealand wants to create standards for graphs, especially online graphs. Until now, we haven&apos;t been able to find any existing standards, so we will have to start from scratch.</description>
	</item>
	<item>
		<title>From Plain English to Global English</title>
		<link>http://tc.eserver.org/23941.html</link>
		<guid>http://tc.eserver.org/23941.html</guid>
		<description>Make your documents easy for EFL users to read and understand, and communicate successfully with people all over the world.&#xD;&#xD;About one billion people use English as a foreign language (EFL). You can avoid most pitfalls of cross-cultural communication by using global English.</description>
	</item>
	<atom:link href="http://tc.eserver.org/publisher/Quality_Web_Content.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>