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.
Subject:Re: Document Naming Conventions From:Writers Book Mall <steve -at- writersbookmall -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Fri, 16 Nov 2007 11:49:40 -0800 (PST)
I'm not speaking from expertise, but my favorite
system (years ago) was a hierarchical, meaningful
structure. Document sets were planned in advance, and
were organized in a fairly consistent (but not rigid)
structure. Anyone could look at a doc number and know
which project it belonged to, and those who cared more
closely could also identify which part of the project
it belonged to and what sort of doc it was.
Admittedly, that was some time ago when things were
simpler (and there were fewer docs).
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-