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.
Beats me, Phyllis. I assume one person would be charged with keeping the
document current. That could be easy or difficult, depending on the
nature of the document and how many people you had to depend on for
input.
Bev
> -----Original Message-----
> From: Palmer, Phyllis [SMTP:PPalmer -at- spherecom -dot- com]
> Pardon me for beating this one to death, but, how does one keep
> control
> over the revisions on this "ever green/living" document?
> Phyllis
>
> > -----Original Message-----
> > From: Parks, Beverly [SMTP:ParksB -at- EMH1 -dot- HQISEC -dot- ARMY -dot- MIL]
> > Good grief. It just makes one want to run screaming from the room.
> > Never
> > heard of it (until now), but it probably means the same as a "living
> > document". In other words, the document is updated as changes
> > occur--always current.
>
> > > -----Original Message-----
> > > From: Judy Fraser [SMTP:jfraser -at- GLINX -dot- COM]
> > > Has anyone heard the term "evergreen document"?
> > > i.e., ...the manual [...] should be maintained as an evergreen
> > > document"
>
