TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I use both headers and footers in my curricula, although I used footers only
for most of my other clients.
In the curricula, I use the following as the recto header (reversed for
[product name, e.g., Microsoft Project Version 3.0]
In the manuals I use the following for the recto footer (reversed...etc.):
[product name -- book name]
(e.g, Assessment Management System -- Network Guide)
I feel that the information most useful for identifying the correct page
should be on the outside of the page, as close to the edge as possible.
For example, in my indexes, I include a header even if the rest of the book
doesn't use one. I put the letter range to be found on the page at the
outside edge of the page.
Headers and footers are location clues, just like indexes (yes, this is a
valid alternate spelling) and TOCs. Use what's necessary to help the
reader find what they're looking for and to identify where they are in the
book. One thing I try to avoid is a multi-line header or footer (which is
why I sometimes use both). It's too easy to bury the important info if
there's more than one line of text.
I think the footer you've designed is informative and too the point, which
is how it should be, IMO (I'm not particularly humble, so why pretend?
Director, Region 8 Conference
bgraham -at- electriciti -dot- com