<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Boynton, J.R</title>	<link>http://tc.eserver.org/authors/Boynton,_J.R</link>
	<description>A bibliography of works by Boynton, J.R 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>Boynton, J.R</title>
		<link>http://tc.eserver.org/dir/Boynton,_J.R</link>
	</image>
	<item>
		<title>Content Management Systems</title>
		<link>http://tc.eserver.org/25755.html</link>
		<guid>http://tc.eserver.org/25755.html</guid>
		<description>Content management systems are key to running an efficient website. Keep the development group out of the loop on updating content, and you will move ever so much faster. &apos;Content&apos; doesn’t need the same kind of source control that scripts and templates need. Specific design suggestions follow.</description>
	</item>
	<item>
		<title>The New Publishing</title>
		<link>http://tc.eserver.org/25756.html</link>
		<guid>http://tc.eserver.org/25756.html</guid>
		<description>We know we can do better than lowest-common-denominator HTML. &apos;Better&apos; means that it is easier to use, more compelling, &apos;sexier&apos;, and more fun for us to design and produce. But it&apos;s very expensive to do bleeding edge for lots of content, and too expensive to do bleeding edge and a version that works in old browsers on slow modems on slow computers with small monitors.</description>
	</item>
	<item>
		<title>On Development Methodology</title>
		<link>http://tc.eserver.org/25757.html</link>
		<guid>http://tc.eserver.org/25757.html</guid>
		<description>Give me the smallest, smartest team possible, with the right tools and infrastructure. Work like fiends for two or three months to get infrastructure and applications started right, then grow slowly to maintain and build additional applications on the core technology.</description>
	</item>
	<item>
		<title>Server-Side Scripting and Templating</title>
		<link>http://tc.eserver.org/25758.html</link>
		<guid>http://tc.eserver.org/25758.html</guid>
		<description>The web publishing/applications industry (generally) has learned to separate content from user interface, to our great benefit. The next step, separating templates from scripts requires an equally large mental leap, but should yield an even greater reward. Here&apos;s how to make our lives easer.</description>
	</item>
	<item>
		<title>Usability for Websites</title>
		<link>http://tc.eserver.org/25759.html</link>
		<guid>http://tc.eserver.org/25759.html</guid>
		<description>Web usability covers the organization of the content (structure) of the site and its individual pages, navigation through the site, the text used to label the structure and navigation, user interaction through forms, and the structure, layout, and wording of text content. In most cases, recognizing the structure of the content and minimizing the effort to find and use content are enough to make for good &apos;usability.&apos;</description>
	</item>
	<item>
		<title>Web Typography</title>
		<link>http://tc.eserver.org/25760.html</link>
		<guid>http://tc.eserver.org/25760.html</guid>
		<description>What stays the same, and what&apos;s different when you go from books and magazines to websites? Allow me one digression, and then I&apos;ll get to specific implications of the switch to onscreen reading.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Boynton,_J.R.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>