<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Lombardi, Victor</title>	<link>http://tc.eserver.org/authors/Lombardi,_Victor</link>
	<description>A bibliography of works by Lombardi, Victor 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>Lombardi, Victor</title>
		<link>http://tc.eserver.org/dir/Lombardi,_Victor</link>
	</image>
	<item>
		<title>Managing the Complexity of Content Management</title>
		<link>http://tc.eserver.org/33284.html</link>
		<guid>http://tc.eserver.org/33284.html</guid>
		<description>Content management systems suck. Or so you would think from the strife heard from analysts and practitioners alike. And yet, many websites regularly publish vast amounts of information with superior control and ease compared to manually editing pages. So where’s the disconnect between what’s possible and the too-often failure of CMS?</description>
	</item>
	<item>
		<title>Metadata Glossary</title>
		<link>http://tc.eserver.org/33040.html</link>
		<guid>http://tc.eserver.org/33040.html</guid>
		<description>In an attempt to summarize the relationship among various metadata formats and how they relate to building Internet systems I wrote a glossary. I then ordered and tied the terms together with a bit of narrative to explain the relationships among the terms.</description>
	</item>
	<item>
		<title>Concept Design Tools</title>
		<link>http://tc.eserver.org/32634.html</link>
		<guid>http://tc.eserver.org/32634.html</guid>
		<description>Designers of digital products and services like ourselves can dramatically improve our work by generating more concepts early in our projects. In this article, I’ll try to make concept design easier to learn by illustrating three simple tools for generating concepts.</description>
	</item>
	<item>
		<title>Defining the Damn Thing</title>
		<link>http://tc.eserver.org/23871.html</link>
		<guid>http://tc.eserver.org/23871.html</guid>
		<description>Defining information architecture is a reccuring theme in all IA forums, and frequently leads to re-naming efforts as well, from information therapist to experience designer. This page is dedicated to that ongoing struggle.</description>
	</item>
	<item>
		<title>Designing for Web Services</title>
		<link>http://tc.eserver.org/23818.html</link>
		<guid>http://tc.eserver.org/23818.html</guid>
		<description>Many technology companies, consultants, and academics are hyping the future of Web services. But how will this background transfer of data between applications affect the user experience?</description>
	</item>
	<item>
		<title>Incorporating Navigation Research into a Design Method</title>
		<link>http://tc.eserver.org/23816.html</link>
		<guid>http://tc.eserver.org/23816.html</guid>
		<description>A presentation about whether an underlying spatial metaphor aids information design usability.</description>
	</item>
	<item>
		<title>Pattern Languages For Interaction Design</title>
		<link>http://tc.eserver.org/23819.html</link>
		<guid>http://tc.eserver.org/23819.html</guid>
		<description>Discusses Christopher Alexander&apos;s theories about a group of related design patterns, referred to as a &apos;pattern language.&apos;</description>
	</item>
	<item>
		<title>The (Unfulfilled) Promise of Content Management Systems</title>
		<link>http://tc.eserver.org/23817.html</link>
		<guid>http://tc.eserver.org/23817.html</guid>
		<description>Be realistic about your needs. Use the right system for your needs. Err on the side of a smaller system. Accept the consistency/flexibility tradeoff. Devote extra time to information architecture. Build a modular design with reusable content. Standardize process and design elements as much as possible.&#xD;Don&apos;t neglect the content in favor of (sexier?) IA and technology.</description>
	</item>
	<item>
		<title>Managing the Complexity of Content Management</title>
		<link>http://tc.eserver.org/21748.html</link>
		<guid>http://tc.eserver.org/21748.html</guid>
		<description>Content management systems suck. Or so you would think from the strife heard from analysts and practitioners alike. And yet, many websites regularly publish vast amounts of information with superior control and ease compared to manually editing pages.</description>
	</item>
	<item>
		<title>The Evolving Homepage: The Growth of Three Booksellers</title>
		<link>http://tc.eserver.org/21275.html</link>
		<guid>http://tc.eserver.org/21275.html</guid>
		<description>What lessons have we learned about how design improves the interface between customers and companies? Perhaps we can start by asking how websites have actually changed over time, and from that we can learn how websites should change in the future.</description>
	</item>
	<item>
		<title>Smarter Content Publishing: Building A Semantic Website to Increase the Efficiency and Usability of Publishing Systems</title>
		<link>http://tc.eserver.org/13660.html</link>
		<guid>http://tc.eserver.org/13660.html</guid>
		<description>The web is not print. The need to create hypertext within pages requires more control over documents. Another is that web pages can also be applications, so access to the &apos;guts&apos; of the page is needed to insert programming code. And ideally, we would like to separate presentation from content, enabling us to format the content in different ways for different purposes. How can we achieve all this with the efficiency and usability we&apos;ve come to expect of other publishing tools?</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Lombardi,_Victor.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>