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 am not a web designer.
I strive for clarity in my writing and clarity in my designs. Good writing is vigorous. Good design is transparent.
I strive to make 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.
Direct your initial queries to email@example.com
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.
My language, design, and technical skills converge naturally on technical writing. I make text-centric designs suitable for manuals and textbooks.
I wrote the server software supporting this site. If your product is software, and if you give me read-only access to your source code (I will sign NDAs), I will be able to answer many questions for myself without bothering your developers.
|Tiny Tools for FreeBSD|
|nellie | sample | web | mac.app.1.9||3.63|
|charles | sample | web | mac.app.1.2||3.43|
|libdorrit | libpip||1.4|
|The Public House | connect||8.12|
|ephemera | connect||6.54|
|multifile | libmultifile||3.39|
|libmessage | libmessageclient||3.14|
|libindex | libyarb | libtable | libstringstack||1.0|