tekom-Jahrestagung 2012 - ActiveDoc

Professionelles Schreiben / Technical Authoring
Other Design Best Practices
We can see the PARCH concepts applied to these basic elements of
design:
−−
White space: Sometimes referred to as negative space, white space is
the empty space between words, lines, paragraphs, at margins, around
headings, etc. Without adequate white space, a document is not readable.
Unfortunately, the automation used by many XML-generated
documents leads to poor use of white space. Headings float meaninglessly
between blocks of text, instead of being properly mated to their
paragraphs. Bullets and layered info floats, rather than being properly
mated to their parent paragraph. In fact, meaningful use of white
space is the biggest casualty of the automation and “content-only”
strategies. For best practices, follow a 3:1 ration of white space with
headings (that is, three times as much white space above as after).
−−
Chunking: The concept of proximity is also seen in how we chunk
information on the page. Paragraphs with overly-opened line spacing,
and without sufficient white space in between, end up looking like
one big lump, instead of visually recognizable chunks of content. This
makes it much harder for users to scan and locate information. For
best practices, always make chunks of information visually separated
on the page through the use of white space. Use single line spacing
and no indent for paragraphs, with ample white space between.
−−
Readability: Every choice we make has to improve the readability
of the document. That includes the typefaces we select, the types of
graphics, and even colors. When designers make choices based on
aesthetics, rather than functionality, they can reduce the usability of
the document. You must learn the functional differences between
serif and sans serif typefaces, plus understand the advantages and
drawbacks of color.
Conclusion
It is time for technical communicators to become better versed in the
language of design. We need to be able to guide and influence the developers
and designers. There is no reason that an XML css cannot be
created to follow better guidelines of chunking, mating, and white space
usage. The representation of content makes a big difference in the overall
usability of the document for readers.
If you have any questions please contact: leah@cowtc.com
tekom-Jahrestagung 2012
397