Technical Writing for Docs, Guides & Knowledge Bases
Contact for pricing
About this service
Summary
Process
FAQs
What types of content do you write?
I specialize in creating API documentation, user manuals, developer guides, knowledge base articles, onboarding materials, and product feature documentation—tailored for both technical and non-technical audiences.
How do you learn about our product or technology?
I begin with discovery calls, existing resources, and interviews with subject matter experts (SMEs). I also explore the product hands-on whenever possible to ensure accuracy and clarity.
What tools do you use for documentation?
I’m proficient in tools like Markdown, Confluence, Notion, Git, Google Docs, and MadCap Flare. I can also adapt to your preferred tools or platforms.
Can you work with our developers or product team?
Absolutely. I frequently collaborate with devs, PMs, and designers to gather insights, validate information, and maintain alignment throughout the writing process.
Do you offer updates or revisions after delivery?
Yes. I include a set number of revisions in each project and can provide ongoing support for updates or content maintenance if needed.
Do you offer SEO or content strategy?
While my primary focus is technical accuracy and usability, I can structure content for discoverability, clarity, and performance—especially for searchable help centers or public-facing docs.
What's included
Documentation Package
User manuals and step-by-step guides API documentation (with examples and integration instructions) Developer documentation and SDK guides Setup/configuration instructions Product or feature release notes
Knowledge Base Content
FAQs and troubleshooting articles Internal and customer-facing knowledge base entries Help center content tailored for searchability and clarity
Training & Onboarding Material
Onboarding guides for employees or customers eLearning scripts or slide content Quick-start guides and job aids
Content Files
Final documents in requested formats (PDF, DOCX, HTML, Markdown, etc.) Editable source files for easy future updates Version-controlled copies (e.g., via GitHub or shared drives)
Style & Structure Documentation
Content style guide or editorial guidelines (if needed) Information architecture or content outline
Review & Revision Logs
Tracked revisions and comments Peer review or SME feedback incorporated Summary of changes for client transparency
Skills and tools
Content Creator
Content Strategist
Technical Writer
Confluence
Google Docs
Jira
Medium
Microsoft Word
Industries