A directory of resources inthe field of technical communication.Articles
151-174 of 7,763 found. Page 7 of 311.
   
About this Site | Advanced Search | Localization | Site Maps  
 
 

« PREVIOUS PAGE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25  NEXT PAGE »

Typography is the study and process of typefaces; how to select, size, arrange, and use them in general. Traditionally, typography was the use of metal types with raised letterforms that were inked and then pressed onto paper. In modern terms, typography today also includes computer display and output.

 

151.
#30448

Affordances

An action possibility available in the environment to an individual, independent of the individual's ability to perceive this possibility.

Soegaard, Mads. Interaction-Design.org. Articles>Human Computer Interaction>Interaction Design

152.
#27360

Affordances

The concept of an affordance was coined by the perceptual psychologist James J. Gibson in his seminal book The Ecological Approach to Visual Perception. The concept was introduced to the HCI community by Donald Norman in his book The Psychology of Everyday Things from 1988. There has however been ambiguity in Norman's use of the concept, and the concept thus requires a more elaborate explanation.

Soegaard, Mads. Interaction-Design.org (2006). Articles>User Interface>Usability

153.
#20526

Afraid of Freezing During a Presentation? Some Thoughts on Why We

In a memorable scene from the movie “8 Mile” the character played by rapper Eminem enters a competition and gets on stage to prove his prowess in front of a rowdy crowd. Using rhyme and rap, he must show his skill at cleverly putting down the reigning champion. Winning the contest could mean fame, fortune and a way out of his grimy, dead-end life. We know he’s up to it. In the preceding scenes he’s brilliant in front of his friends and the bathroom mirror. But when he faces the jeering crowd on the big night he freezes and is unable to speak. As the crowd chants “Choke! Choke!” he leaves the stage in shame. Freezing in front of an audience is every speaker’s worst nightmare. Eminem was clearly facing a hostile crowd. But why do some speakers freeze even when they are in front of an audience that is friendly and receptive?

Berkley, Susan. Presenters University (2003). Articles>Presentations>Rhetoric

154.
#24578

Afraid So: Horrible Web Monstrosities

Here they come. Nightmare web sites that, from a usability perspective, are horrid monsters. When you're tired and in a hurry, you want a web site to quickly and easily provide relevant content to you, so you can solve a problem or perform some task. Discover common hideous impediments to web usability. WARNING: Not for the faint hearted!

Streight, Steven. Blogger.com (2004). Articles>Web Design>Usability>User Centered Design

155.
#28615

Afraid to Measure: The State of Communications Accountability  (link broken)

With all the emphasis on ROI of public relations in the so-called 'marketing mix' to increase sales, the communications goals of most leaders and communicators go far beyond public relations ROI connected to sales.

Journal of Leadership Communication Counsel (2007). Articles>Management>Communication>Business Communication

156.
#30163

After Enron: Integrating Ethics into the Professional Communication Curriculum   (peer-reviewed)   (members only)

Recent scandals in the business community have alerted professional writing teachers to the importance of highlighting ethics in the curriculum. From former experiences in teaching courses emphasizing ethics, the authors have adapted the curriculum to include a limited discussion of ethical approaches and terms and assigned group writing projects that consider the effects of business on the broader community. As a result of the integration of this ethical component into the entire course, students learn major ethical approaches; gain a vocabulary of ethical terms they can apply in the business world; interrogate the larger questions of business and its interactions with the local, national, and international community; and engage in the kind of dialectical discussions that require critical thinking.

Kienzler, Donna S. and Carol David. Journal of Business and Technical Communication (2003). Articles>Education>Ethics

157.
#13698

After Hypertext

The final decade of the last century witnessed the dramatic rise of hypertext as a literary, technical, social, and intellectual phenomenon. Today, despite the fact that hypertext provides the conceptual underpinnings for the World Wide Web (among other things), 'hypertext' remains a relatively peripheral term. In this talk, I'll track some of the ways that 'hypertext' has been articulated during the last five decades, describing how the social construction of hypertext inscribed the technology(ies) in limiting and ultimately self-defeating ways. I'll then attempt to track (and construct) some possible futures for a dramatically redefined hypertext, one constructed as an 'ethic of reference' within and among social communities rather than a technical practice.

Johnson-Eilola, Johndan. Clarkson University (2001). Articles>Information Design>Hypertext

158.
#27997

After the CMS Implementation Project

Much effort is focused, on the selection and subsequent implementation of a content management system (CMS). While it is obviously vital to ensure that the initial implementation project is successful, this is only the beginning of an ongoing commitment to growing and enhancing the use of content management throughout the organisation.

Robertson, James. CM Briefing (2004). Articles>Content Management>Project Management>Workflow

159.
#21283

The Age of Findability

It doesn't replace information architecture. And it's really not a school or brand of information architecture. Findability is about recognizing that we live in a multi-dimensional world, and deciding to explore new facets that cut across traditional boundaries.

Morville, Peter. Boxes and Arrows (2002). Articles>Usability>Search

160.
#13658

The Age of Information Architecture

For the most part, information architects are communicators and strategists. While others merely tolerated the mishmash of responsibilities, they relished it. Designers often put up with having to write HTML but jumped at the chance to 'just do design.' Programmers were forced to meet with clients and work on strategy, but all along probably wanted to just write code. When these two ends of the spectrum split off, the empty middle was a perfect place to be. At the same time, there was an increased (but still hidden) need for information architecture. As the average web project process matured, more problems arose. Formal documentation was needed, business objectives were taking on increased importance, and, as the size increased exponentially, information organization became a much more important role. (The fact that this evolution took place during the 'dot.com fallout' is not insignificant, as this led to the placement of web projects under the same microscope as other business endeavors.) Some of these positions could be filled by existing disciplines; project managers, business analysts, and usability specialists transitioned from 'traditional' work and were added to web teams. Still, there was something missing. The connection between 'the big picture' (business strategy, high-level user tasks, basic structural architecture) and the nitty-gritty (categorization, labeling, bottom-up information hierarchies) often wasn't being made. This is where information architects fit in.

Lash, Jeff. Digital Web Magazine (2002). Articles>Information Design>Usability

161.
#26374

Agent vs. Agent

The phrase User agent or user-agent or UA or browser or client or client application or client software program...all pretty much refer to the same thing. Or maybe not.

evolt (2002). Articles>Web Design>User Interface>Web Browsers

162.
#18539

Aggregated Article Databases: Research Beyond the Internet   (PDF)

Introduces aggregated article databases—searchable collections of magazines, newspapers, and journals—and explains their relevance to the research work of technical communicators.

Sheffield Hulick, Jennifer L. Intercom (2003). Articles>Research>Online

163.
#27801

Agile Development Checklist

The purpose of this article is to define a set of ideal practices for an agile software development project.

McLennan, Liam. Code Project, The (2006). Articles>Project Management>Agile

164.
#27589

Review: Agile Documentation: A Pattern Guide to Producing Lightweight Documents for Software Projects

In Agile Documentation, Rüping gets to the heart of the documentation dilemma, offering a two-word solution: minimum necessary.

Davis, Donna L. developer.star (2003). Articles>Reviews>Agile>Documentation

165.
#27588

Agile Documentation: Strategies for Agile Software Development

When I initially started work on Agile Modeling (AM) I wanted to focus solely on principles and practices for effective modeling but quickly discovered that this scope was not sufficient, that I also needed to consider the issue of how to be effective at the creation and maintenance of documentation too. Some agile models will �evolve� into official system documentation, although the vast majority will not, and therefore it is relevant to discuss how to be agile doing so.

Agile Modeling. Articles>Documentation>Agile>Extreme Documentation

166.
#30762

Agile Documentation (Using Tests as Documentation)   (PDF)

Storytelling can make documentation more exciting for both writers and readers. Stories provide context and people tend to remember them. More all-∆around fun when stories are tests.

Gheorghiu, Grig. Business Information Review. Articles>Documentation>Agile>Testing

167.
#28121

Agile Documentation with doctest and epydoc

A Test Map is a list of unit tests associated with a specific function/method under test. It helps you see how that specific function/method is being exercised via unit tests.

Gheorghiu, Grig. Blogspot (2005). Articles>Documentation>Agile

168.
#30707

Agile Principles Are Changing Everything

There's an irony about agile development. There is no hard evidence that it produces better software, faster. And formal adoption rates, admittedly hard to measure, don't reach the 20 percent mark. Yet the ideas that underpin agile development--defining requirements incrementally, writing software in short stints, seeking customer feedback, testing code as it's written, frequent builds--have caught on like wildfire. They are widely accepted as sound development practices, even among teams that have not formally adopted them.

deJong, Jennifer. Software Development Times (2008). Articles>Collaboration>Agile>Methods

169.
#27355

Ajax

Asynchronous JavaScript And XML, or its acronym, Ajax (Pronounced A-jacks), is a Web development technique for creating interactive web applications. The intent is to make web pages feel more responsive by exchanging small amounts of data with the server behind the scenes, so that the entire Web page does not have to be reloaded each time the user makes a change. This is meant to increase the Web page's interactivity, speed, and usability.

Wikipedia. Articles>Web Design>DHTML>Ajax

170.
#27044

Ajax and Your CMS

If a modern day Rip van Winkle woke up after just a year's sleep, he would be stunned by the buzz around Ajax today. Technology is moving very quickly in this space and whether you are a web author, a CMS developer, or a regular web user, Ajax will make some exciting changes to your world.

Downes, Jonathan and Joe Walker. CMSwatch (2006). Articles>Content Management>Web Design>Ajax

171.
#30659

Ajax for Chat

Learn to build a chat system into your Web application with Asynchronous JavaScript + XML (Ajax) and PHP. Your customers can talk to you and to each other about the content of the site without having to download or install any special instant-messaging software.

Herrington, Jack D. IBM (2007). Articles>Web Design>Community Building>Ajax

172.
#27052

Ajax for Java developers: Build Dynamic Java Applications

The page-reload cycle presents one of the biggest usability obstacles in Web application development and is a serious challenge for Java™ developers. In this series, author Philip McCarthy introduces a groundbreaking approach to creating dynamic Web application experiences. Ajax (Asynchronous JavaScript and XML) is a programming technique that lets you combine Java technologies, XML, and JavaScript for Java-based Web applications that break the page-reload paradigm.

McCarthy, Philip. IBM (2006). Articles>Web Design>Interaction Design>Ajax

173.
#27053

Ajax for Java Developers: Java Object Serialization for Ajax

If you're doing Java Web development using Asynchronous JavaScript and XML (Ajax), then delivering data from the server to the client is probably your top concern. In this second article in the Ajax for Java developers series, Philip McCarthy walks you through five approaches to Java object serialization and gives you all the information you need to choose the data format and technology best suited to your application.

McCarthy, Philip. IBM (2006). Articles>Web Design>Programming>Ajax

174.
#29966

Ajax for Ratings and Comments

In the age of the people-powered Web, allowing your readers to rate and review content on your site is critical. Discover just how easy it is to add rating and commenting features to a site with Ajax.

Herrington, Jack D. IBM (2007). Articles>Web Design>Ajax

175.
#26907

Ajax Mistakes

Ajax is an awesome technology that is driving a new generation of web apps, from maps.google.com to colr.org to backpackit.com. But Ajax is also a dangerous technology for web developers, its power introduces a huge amount of UI problems as well as server side state problems and server load problems.

Bosworth, Alex. Sourcelabs.com (2005). Articles>Web Design>DHTML>Ajax



 
« PREVIOUS PAGE  |  NEXT PAGE »

 

Copyright © 2001-08 by the EServer. All rights reserved.Add a Work | Site Preferences | Discussion Forum | Habitués  

There are 6 readers currently online: 0 registered users and 6 guests. Register.RSS feedClick here to learn how to embed the RSS feed of this category in your website.