I am a one-man documentation team specializing in user’s guides and reference manuals in PDF, ebook, and web form. I make documents that communicate and instruct. I do not make marketing materials.
I strive for clarity in my writing and clarity in my designs. Good writing is vigorous. Good design is transparent. I use Adobe’s tools, but if your company keeps its documentation in Word format as a matter of policy, I can make Word docs that look professional.
I strive to create documents that are useful. To lower the volume of your customer support queries, I will consult your support department to determine the most common problems that your users need help with and highlight those issues in your documentation.
Precision and attention to detail are second nature to me. In my former career in Quality Assurance, I discovered and documented variation in material, process, and specification on products with up to multimillion dollar values. I know first hand how poorly executed internal documents increase non-conformances. I know first hand how poorly executed manuals influence customer satisfaction and subsequent purchasing decisions.
I wrote the server software supporting this site. If your product is software, and if you give me read-only access to your source archive (I will sign NDAs), I may be able to answer many questions for myself without bothering your developers.
I have a Technical Writing Certificate with Honors from the Humber Institute of Technology.
I understand formal English.
I write fiction.
Tools for FreeBSD
Most of the following programs are in the ports collection, but I have stopped maintaining the ports. The most recent source code is always available here.
|drood | humdinger | droodpipe | libdorrit||5.30|
|humdinger requires libserver|
|gonzalo | trinculo||1.5|
|trinculo requires libserver|
|libserver | libserverevents||3.13|
|libdombey | libdombeyevents||5.31|
|munger requires sqlite3 and libtre from ports (pkg install sqlite3 libtre)|
|dkns requires munger|