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.
Email me at firstname.lastname@example.org.
Invite me into a chat room at The Public House.
If we do business, I will open a Sub Rosa account for you.
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 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 have a Technical Writing Certificate with Honors from Humber College. I am a craftsperson who knows how to use his tools.
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.
Tools for FreeBSD
|gonzalo | prospero | caliban||2.35|
|libserver | libserverevents||3.23|
|libdombey | libdombeyevents||5.38|
|Munger requires databases/sqlite3 and textproc/libtre from ports.|
|Dickens requires munger.|