Re: Using forms instead of templates

["Paul Strasser" <paul -dot- strasser -at- windsor-tech -dot- com>]

First, recognize the fact that you'll probably have to do some editing of
whatever comes back from the developers.  No matter how terrific your form
or doc might be, most developers can't write worth a darn anyway.

We use a series of "fill in the blank" technical docs based on templates
I've created.  And regardless of how detailed or specific the headings or
instructions are for a doc, each project will be a bit different, so the
steps or procedures will differ.  One client's User Requirements doc will
differ from another client's.

In general, though, a bit of tweaking is a lot easier than completely
re-inventing the wheel for every document for every project.

If your templates are clean and logical, one reasonable step is for you to
let the people who are blank-filling exactly which style is used for a
particular process ("use Body Text for all narratives.  Use List 1 for
step-by-step procedures.  Use Bullet 1 for unordered lists")  Even if they
totally muck it up, you know how to fix it.

Good luck

Paul Strasser
Windsor Technologies
Lafayette, CO

more resources and info.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you 
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of 
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit 
http://www.raycomm.com/techwhirl/ for more resources and info.