Help with technical document 1

[nissan240zx]

Hello All,
Not sure if this is the right forum.
I am looking for some examples/templates for writing a technical implementation guide.

Please advice...

Nissan

A good programmer is someone who looks both ways before crossing a one-way street. - Doug Linder

 

[chiph]

Who is the audience?

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[nissan240zx]

Audience is technical development team.

A good programmer is someone who looks both ways before crossing a one-way street. - Doug Linder

 

[chiph]

Just write it as if the person was sitting the cube with you. Then go back and refactor it so that related topics are put with each other.

For a technical audience, content is much more important than appearance.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[stevexff]

chiph

Sensible solution - avoids much of the boilerplate padding you see in most documentation. Have a star.

Steve

[small]"Every program can be reduced by one instruction, and every program has at least one bug. Therefore, any program can be reduced to one instruction which doesn't work." (Object:erlDesignPatterns)[/small]