Technical Writer
specializing in task-based documentation and modern documentation workflows
I turn complex systems, tools, and tribal knowledge into documentation people can actually use, without jargon or guesswork. My work is grounded in strong information architecture, plain language, and accuracy. I collaborate closely with SMEs to turn tribal knowledge into documentation that actually gets used.
Experience with Markdown-first docs, GitHub workflows, structured content, and accessibility-first writing.
What I Create
→ Task-based procedures & SOPs
→ User guides and help center articles
→ Internal documentation and onboarding guides
→ Quick reference cards and job aids
How I Work
→ Markdown-first writing for clean, reusable content
→ GitHub workflows (repos, commits, reviews, version history)
→ Structured, task-based content design
→ Style consistency and terminology management
→ Documentation QA (accuracy, link checks, revision tracking)
Tools I Use
→ GitHub & Markdown
→ Microsoft Word & Excel
→ Adobe Acrobat
→ Canva
→ Articulate Rise & Storyline
→ AI-assisted writing tools
Documentation Sample: WorkNest
What it is: A sample documentation project demonstrating how I structure, write, and maintain task-based technical documentation using Markdown-first workflows and GitHub.
This project demonstrates:
📄Structured, task-based technical documentation written for real users
📄 Clean Markdown formatting for readability and reuse
📄 GitHub workflows (commits, versioning, pull request-ready content)
📄 UI-style documentation suitable for help-centers or internal knowledge bases
Why this matters: This project reflects how I approach documentation in real teams, writing content that’s easy to maintain, easy to update, and easy for users to follow under real-world conditions.
Documentation Sample: Clearpath
What it is: This project is a fictional internal documentation set created to demonstrate how I design and write onboarding documentation and standard operating procedures for non-technical employees.
This project demonstrates:
📄Task-based SOPs with clear purpose, scope, prerequisites, and outcomes
📄 Internal onboarding documentation designed for non-technical audiences
📄 Consistent structure and formatting across multiple document types
📄 Plain-language writing that reduces confusion and support dependency
📄 Documentation designed to be referenced, not memorized
📄 Realistic revision control and versioning practices
Why this matters: This project reflects how I approach documentation in real organizations, by creating content that helps employees complete tasks confidently, understand expectations, and know where to go for help. the result is documentation that supports onboarding, reduces friction, and scales as teams grow.