<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Web Design&gt;Document Design</title>	<link>http://tc.eserver.org/dir/Articles/Web-Design/Document-Design</link>
	<description>A listing of the most recently indexed works about Articles and Web Design and Document Design 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>Articles&gt;Web Design&gt;Document Design</title>
		<link>http://tc.eserver.org/dir/Articles/Web-Design/Document-Design</link>
	</image>
	<item>
		<title>Web 2.0, and Me</title>
		<link>http://tc.eserver.org/35210.html</link>
		<guid>http://tc.eserver.org/35210.html</guid>
		<description>As help systems continue to evolve, whatever name they are called, we will increasingly have to face responsibility for their content, and bring their expertise to what we write. The new systems provide us with all the required tools that tell us the problems with their content. It is up to us to leverage that information to provide better content, and act as ambassadors for products that we write. If writers can go a step ahead, and use their help information to sell products, and reduce the burden on customer support, we would have truly arrived.</description>
	</item>
	<item>
		<title>Calling Accessible Context-Sensitive Help with Unobtrusive DOM/JavaScript: A Help Authoring Guide</title>
		<link>http://tc.eserver.org/35190.html</link>
		<guid>http://tc.eserver.org/35190.html</guid>
		<description> This Fast Track tutorial demonstrates two methods to call Context-Sensitive Help in a Web Form. We&apos;ll discover how Unobtrusive DOM/JavaScript achieves the desired result in calling Context-Sensitive help, and demonstrate how to keep the Structure, Presentation, and Behavior layers of a web page completely separate from one another ensuring good practice with current web standards and accessibility rules.</description>
	</item>
	<item>
		<title>Unwebbable</title>
		<link>http://tc.eserver.org/35174.html</link>
		<guid>http://tc.eserver.org/35174.html</guid>
		<description>It’s time we came to grips with the fact that not every “document” can be a “web page.” Some forms of writing just cannot be expressed in HTML—or they need to be bent and distorted to do so. But for once, XML might actually help.</description>
	</item>
	<item>
		<title>Tips To Create A Clean Structured About Page</title>
		<link>http://tc.eserver.org/35158.html</link>
		<guid>http://tc.eserver.org/35158.html</guid>
		<description>When it comes to an about page, think outside the box. Try to think of something new and creative that’s different form the rest of your site. Of course display images of you / your staff, and descriptions of each, but try to lay it out in a very fun way, whistle keeping it clean and readable.</description>
	</item>
	<item>
		<title>Webpage Layout: Right Hand Side Blindness</title>
		<link>http://tc.eserver.org/34464.html</link>
		<guid>http://tc.eserver.org/34464.html</guid>
		<description>In several recent websites we have user tested, the site designers have placed important task critical links and information on the right hand side (RHS) of three column page layouts. The user testing was conclusive, users ignore any information presented on the RHS. We think this is a similar effect to the well documented banner blindness. It is essential to ensure that import links or information is not positioned on the RHS as they will surely be ignored.</description>
	</item>
	<item>
		<title>Fluid Grids</title>
		<link>http://tc.eserver.org/34100.html</link>
		<guid>http://tc.eserver.org/34100.html</guid>
		<description>Fluid layouts are an undervalued commodity in web design. They put control of our designs firmly in the hands of our users and their browsing habits. They’ve also utterly failed to seize the imagination of web designers.</description>
	</item>
	<item>
		<title>Relatively Absolute</title>
		<link>http://tc.eserver.org/33964.html</link>
		<guid>http://tc.eserver.org/33964.html</guid>
		<description>Positioning is perhaps one of the most misunderstood parts of&#xD;CSS 2. Let us look a little closer at how it works.</description>
	</item>
	<item>
		<title>Bezględnie Względny</title>
		<link>http://tc.eserver.org/33965.html</link>
		<guid>http://tc.eserver.org/33965.html</guid>
		<description>Pozycjonowanie z kolei jest jednym z najczęściej mylnie interpretowanych aspektów wersji 2 CSS. Przyjrzyjmy się zatem nieco bliżej temu, jak ono działa.</description>
	</item>
	<item>
		<title>CSS Hizalama</title>
		<link>http://tc.eserver.org/33966.html</link>
		<guid>http://tc.eserver.org/33966.html</guid>
		<description>Hizalama ise CSS 2’nin belki de en yanlış anlaşılmış bölümlerinden biridir. Şimdi nasıl çalıştıklarına biraz daha yakından bakalım.</description>
	</item>
	<item>
		<title>Liquid Layouts the Easy Way</title>
		<link>http://tc.eserver.org/33967.html</link>
		<guid>http://tc.eserver.org/33967.html</guid>
		<description>This article explains one method of achieving a successful liquid layout as well as providing basic definitions of liquid, fixed-width and em-driven layouts.</description>
	</item>
	<item>
		<title>Fluid Grids</title>
		<link>http://tc.eserver.org/33941.html</link>
		<guid>http://tc.eserver.org/33941.html</guid>
		<description>Fluid layouts are an undervalued commodity in web design. They put control of our designs firmly in the hands of our users and their browsing habits. They’ve also utterly failed to seize the imagination of web designers.</description>
	</item>
	<item>
		<title>Reviewing Wiki Documentation via Crucible</title>
		<link>http://tc.eserver.org/33694.html</link>
		<guid>http://tc.eserver.org/33694.html</guid>
		<description>I have been playing around with Crucible, Atlassian’s peer code review tool. The latest version of Crucible allows you to review Confluence wiki pages. This is a new feature, so I decided to try it out. Also, I was wondering why you might want to use an independent tool to review a wiki page, when you could instead just add comments to the page or update the page directly.</description>
	</item>
	<item>
		<title>Using a “Strawman” for Page Layout Design</title>
		<link>http://tc.eserver.org/33227.html</link>
		<guid>http://tc.eserver.org/33227.html</guid>
		<description>Designing the page layouts for a new or redesigned intranet can be complex. One of the most difficult aspects is creating the first layout. Starting with an empty screen, you need to determine what will go on each page and where it will go. Using a strawman design - a design that is created with the intent of discarding it - can help to overcome many of the difficulties in the design process.</description>
	</item>
	<item>
		<title>Visible Narratives: Understanding Visual Organization</title>
		<link>http://tc.eserver.org/33228.html</link>
		<guid>http://tc.eserver.org/33228.html</guid>
		<description>Visual communication can be thought of as two intertwined parts: personality, or look and feel, and visual organization. The personality of a presentation is what provides the emotional impact —your instinctual response to what you see. Creating an appropriate personality requires the use of colors, type treatments, images, shapes, patterns, and more, to “say” the right thing to your audience. This article, however, focuses on the other side of the visual communication coin: visual organization.</description>
	</item>
	<item>
		<title>Web Site Layout</title>
		<link>http://tc.eserver.org/33233.html</link>
		<guid>http://tc.eserver.org/33233.html</guid>
		<description>It appears that about one out of five Web sites (only 20%) currently are designed using a &quot;Fluid&quot; layout. Unfortunately, the layout most preferred by users, the &quot;Fluid&quot; layout, is the one implemented least often by designers.</description>
	</item>
	<item>
		<title>Five Simple Steps to Designing Grid Systems: Grid Systems for Web Design, Part 1</title>
		<link>http://tc.eserver.org/33145.html</link>
		<guid>http://tc.eserver.org/33145.html</guid>
		<description>Designing grid systems for print is considerably more straight forward than designing grid systems for the web. First off,in print, the designer has a fixed media size - the paper size (or packaging, poster, whatever). Let&apos;s say a print designer has designed a magazine. The reader of this magazine can&apos;t suddenly increase the font size if they find it difficult to read - well they just move it closer to their eyes I guess. This is just one consideration, there are more but I&apos;m sure you get the point.</description>
	</item>
	<item>
		<title>Five Simple Steps to Designing Grid Systems: Grid Systems for Web Design, Part 2</title>
		<link>http://tc.eserver.org/33146.html</link>
		<guid>http://tc.eserver.org/33146.html</guid>
		<description>Fixed width grid design for the web. What is it, how do we do it and how do we implement it? For the purposes of this article, I&apos;m going to be focussing on the theory of creating the grid rather than the implementation. I did mention in the last series that I would cover implementation using CSS, well I&apos;m not going to. There are just so many resources and books available telling you how to create the CSS layouts you need—I&apos;ll touch on it, but I won&apos;t be going into too much detail.</description>
	</item>
	<item>
		<title>Five Simple Steps to Designing Grid Systems: Grid Systems for Web Design, Part 3</title>
		<link>http://tc.eserver.org/33147.html</link>
		<guid>http://tc.eserver.org/33147.html</guid>
		<description>Flexible vs Fixed. Which one to choose? Why choose one over the other? Well you won&apos;t find the answers to those questions here. What I&apos;m aiming to do with this article is to investigate how the theory of grid design can be applied to a flexible web page.</description>
	</item>
	<item>
		<title>How to Prevent HTML Tables from Becoming Too Wide</title>
		<link>http://tc.eserver.org/32504.html</link>
		<guid>http://tc.eserver.org/32504.html</guid>
		<description>The layout model of tables differ from that of block level elements in that they will normally expand beyond their specified width to make their contents fit. At first that may sound like a good thing – and it often is – but it makes it possible for oversized content to make text unreadable or completely break a site’s layout, especially in Internet Explorer.</description>
	</item>
	<item>
		<title>Building Up a Site Wireframe</title>
		<link>http://tc.eserver.org/32434.html</link>
		<guid>http://tc.eserver.org/32434.html</guid>
		<description>Every web designer should know and understand a Web site’s parameters before lifting a finger to start designing the site. In this article, you will learn the basics required to start designing business Web sites. While this information is useful if you want to build sites for others, it can also serve as a checklist article for sites you want to build for yourself.</description>
	</item>
	<item>
		<title>Six Ways to Style Blockquotes</title>
		<link>http://tc.eserver.org/32395.html</link>
		<guid>http://tc.eserver.org/32395.html</guid>
		<description>Blockquotes do have some styling by default. Most browsers will indent the text in a blockquote tag, which helps the user recognize that the text is different somehow. But who’s to say that we need to stop there? Here are six different ways you could style your blockquotes using CSS.</description>
	</item>
	<item>
		<title>Book-Style Chapter Introductions Using Pure CSS</title>
		<link>http://tc.eserver.org/32405.html</link>
		<guid>http://tc.eserver.org/32405.html</guid>
		<description>Today’s tutorial will show you how easy it is to create book-style chapter (article, whatever) introductions using nothing but pure CSS — no XHTML was harmed in the making of this tutorial. We’ll use two types of selectors which I haven’t talked about yet here: adjacent sibling selectors and pseudo-element selectors. I’ll explain each type briefly before we get started.</description>
	</item>
	<item>
		<title>Think WYSIOP, not WYSIWYG</title>
		<link>http://tc.eserver.org/31974.html</link>
		<guid>http://tc.eserver.org/31974.html</guid>
		<description>Several years ago, someone used the term WYSIOP (What You See Is One Possibility) when talking about the RoboHelp HTML editor, because what developers saw in the editor didn&apos;t usually match the results. I had what I thought was an absolutely brilliant leap of logic ;-) a couple of months ago when I realized that today&apos;s WYSIWYG (What You See Is What You Get) editors are really WYSIOP, because the results are determined by whatever layout template is assigned at the time the results are viewed.</description>
	</item>
	<item>
		<title>Systems That Get Better the More People Use Them</title>
		<link>http://tc.eserver.org/31740.html</link>
		<guid>http://tc.eserver.org/31740.html</guid>
		<description>In Publishing 2.0, Tim O&apos;Reilly says Web 2.0 is &apos;any network effect that makes a system better the more people use it.&apos; Web 2.0 isn’t just user-generated content; it’s harnessing the collective intelligence of your users to make your system better.</description>
	</item>
	<item>
		<title>Is Your Website Poised to Deal With Its Growth?</title>
		<link>http://tc.eserver.org/30766.html</link>
		<guid>http://tc.eserver.org/30766.html</guid>
		<description>Every webmaster nourishes the dream that his or her website will make it the big way. This is very much human because people carry out any task in ardent hope. What is more human out here is that earthy fellows like us base our aspirations more on speculation rather than specific set of steps undertaken to bring the dream a bit closer to reality. And this is not all, particularly in case of growth of a site which brings newer problems in the wake of its growth.&#xD;&#xD;It cannot be disputed that you can probably get some good web hosting on economy price. But if you expect top of the line service on this price, acknowedge gracefully that your are just asking for the moon. Probably you are not catching up with wisdom that business needs decisive investments.</description>
	</item>
	<item>
		<title>Applying Web 2.0 Technologies to Technical Documentation </title>
		<link>http://tc.eserver.org/28228.html</link>
		<guid>http://tc.eserver.org/28228.html</guid>
		<description>This article is based on my presentation at the Institute of Scientific and Technical Communicators&apos; annual conference in October, 2006.  Every now and then, there is a change in the value of what technical authors deliver. These are moments when organisations pay attention to technical documentation. This is because they recognise that these changes mean they can create something that will be of real value to the business and to their customers. &#xD;&#xD;In recent years, there have been three &quot;waves of interestingness&quot;. The first wave was the introduction of Windows Help (WinHelp). The second major wave was the introduction of the Internet and intranets. This was a time when organisations looked at how they could transfer large amounts of information from paper to online. They were faced with issues such as how users could access and understand all this information easily - issues that technical communicators deal with on a day-to-day basis. &#xD;&#xD;I believe we&apos;re just about to approach the new wave, which we have called &quot;Tech Writing 2.0&quot;.</description>
	</item>
	<item>
		<title>Constructing a One-Stop &quot;Answer Station&quot; Website for Software Users</title>
		<link>http://tc.eserver.org/27658.html</link>
		<guid>http://tc.eserver.org/27658.html</guid>
		<description>The web allows us to easily provide updated documentation to our users, but why stop there? There is more to making users successful quickly than just providing documentation. By creating a complete &apos;Answer Station&apos; that is accessible from the application or product, we can not only direct users to that updated documentation, but we can also provide information about technical support, consulting, training, sales, etc.&#xD;&#xD;This article discusses writing a proposal for an Answer Station, determining content, working with other departments to gather information, designing the site, making that design work with an existing corporate website, dealing with tool issues, and finally, going live.</description>
	</item>
	<item>
		<title>Six Tips for Improving Your Design Documentation</title>
		<link>http://tc.eserver.org/25619.html</link>
		<guid>http://tc.eserver.org/25619.html</guid>
		<description>Good organization, complete information, and clear writing are, of course, key to the success of any design document, but there are some other, less-obvious techniques you can use to make your documents more readable and understandable. Here are a few of them.</description>
	</item>
	<item>
		<title>Hypertext for Handling Conceptual Material</title>
		<link>http://tc.eserver.org/23264.html</link>
		<guid>http://tc.eserver.org/23264.html</guid>
		<description>Turning &apos;help&apos; systems and &apos;browsers&apos; into robust structured-document viewers: the DocBrowser.</description>
	</item>
	<item>
		<title>Restructuring Online Documentation for the World Wide Web</title>
		<link>http://tc.eserver.org/20551.html</link>
		<guid>http://tc.eserver.org/20551.html</guid>
		<description>Technical communicators around the world are turning to the World Wide Web us their primary delivery agent for&#xD;on-line documentation. The transition from older forms of&#xD;on-line documentation to HTML-based documents pre -&#xD;sents new challenges in every phase of the documentation&#xD;process: document creation, layout, access, and especially&#xD;hypermedia capability The constant development of new&#xD;web tools presents an even greater challenge for an organization&#xD;seeking to stay abreast of technology with an ever&#xD;decreasing budget. This panel will outline the basic steps&#xD;in migrating to the web while focusing on one&#xD;organization’s solution to meeting the challenges of restructuring&#xD;its on-line documentation for web migration.</description>
	</item>
	<item>
		<title>Building the Treasure House: Creating Knowledge Bases on the World-Wide Web</title>
		<link>http://tc.eserver.org/20287.html</link>
		<guid>http://tc.eserver.org/20287.html</guid>
		<description>Web knowledge bases offer an excellent platform for delivering technical documentation and customer support information. They also represent an area of great&#xD;opportunity for technical communicators to expand their&#xD;skills, satisfy their customers, and create value for their&#xD;employers or clients. This session explores the&#xD;components of a web knowledge base and the tasks&#xD;involved in planning and building one.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Web-Design/Document-Design.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>