MK
000+

Countries documented at Google scale.

000+

Countries documented at Google scale.

00.00%

Quality score. At Google velocity.

00.00%

Quality score. At Google velocity.

0

Tools built. Without being asked.

0

Tools built. Without being asked.

Every document is a decision. Here are some of mine.

API Documentation

Developer-facing API guides, endpoint documentation, authentication schemas, error state documentation. Designed to reduce support queries and accelerate integration.

WOPA API documentation (Accenture) · KHEMEIA API developer guides (Cyient)

View Samples →

User Documentation

User guides, help center articles, onboarding flows. Written for real humans trying to accomplish real goals.

View Samples →

Release Notes

Communicating product changes clearly to technical and non-technical audiences simultaneously.

View Samples →

Knowledge Base

Centralized documentation repositories, self-service content systems, reducing redundant support queries.

Established centralized repository at Accenture: 30% reduction in redundant PM queries

View Samples →

Technical Manuals

S1000D and iSpec 2200 compliant aerospace documentation for Airbus and Boeing. Where a documentation error grounds a fleet.

98% compliance rate

View Samples →

Information Architecture

The structure beneath the document. Content hierarchies, navigation systems, localization frameworks.

Billing 2.0 (250+ countries) · Project Setu (Indian regional languages at Google scale)

View Samples →

Docs-as-Code

Documentation that lives where code lives. Git workflows, CI/CD pipelines, Markdown-first systems.

40% faster content deployment. WIKA migration from XML to Git + Markdown pipeline

View Samples →

I don't organize information. I design how understanding moves.

Global Payments

Billing 2.0

Problem
250+ country selectors. Each with unique payment rules, legal requirements, and user expectations.
Insight
The differences are smaller than they appear. The shared infrastructure is larger than anyone had mapped.
Result
A unified architecture serving global complexity without multiplying maintenance burden.

250+ countries. One coherent system.

Read the full case study →
Documentation Infrastructure

WIKA Docs-as-Code Migration

Problem
A documentation system that moved slower than the product it described.
Insight
Documentation debt compounds like technical debt. The interest is developer frustration and user confusion.
Result
Git + Markdown + Markdownlint + CSpell pipeline. 40% faster deployment.

40% faster deployment.

Read the full case study →

I found inefficiencies in my own workflow. So I built tools to eliminate them.

None of these were in my job description. All of them were in my job.

Scale
  • 000+Countries documented
  • 000+Documents delivered
  • 00+Enterprise projects
  • 00+Products documented
  • 0Industries: Aerospace · SaaS · Consumer Tech
0.00%
Quality ScoreAt Google velocity
Speed
  • 00%faster deployment (WIKA)
  • 00%fewer support queries (WOPA)
  • 00%faster turnaround (MD→XML)
  • Zeropipeline disruptions (Culvert)
  • 00%improvement in deliverable standards

Some documentation errors are inconvenient.
Some are fatal.

Aerospace

Airbus | Boeing

S1000D · iSpec 2200 · ASD-STE100

“Maintenance manuals where an ambiguous instruction can ground a fleet.”

98%Compliance Rate

Global Finance

Google Payments

Google Style Guide

“Where a missing localization note can fail a merchant in a market they depend on.”

99.64%Quality Score

Precision is not a preference. It is the product.

API documentation is a user experience problem. Most people treat it as a formatting problem.

POST/v1/documents/transform
Request
POST /v1/documents/transform
Authorization: Bearer sk_live_...
Content-Type: application/json

{
  "source_format": "markdown",
  "target_format": "dita",
  "content": "# Getting started...",
  "options": {
    "validate": true,
    "locale": "en-US"
  }
}
Response · 200
HTTP/1.1 200 OK

{
  "id": "tf_8Kd93hAq",
  "status": "complete",
  "target_format": "dita",
  "output_url": "https://api.example.com/v1/documents/tf_8Kd93hAq/output",
  "warnings": []
}
Error states: documented, not hidden

When documentation is right, developers don't need to ask questions.

Explore the full API experience →

Built With Intention

This portfolio is not a template. It is a production application. Every design decision has a reason. Every technical decision has a reason. Here are both.

Frontend
Backend
Infrastructure

Before I understood information architecture, I understood storytelling.

It turns out they are the same discipline.

Complexity is not the enemy. Unclear thinking is.

What complexity are you sitting with right now?

Let's talk about transforming it.

LinkedIn ↗Download Resume →

I respond to everyone who reaches out thoughtfully.

Open for
  • Senior Technical Writer roles
  • Information Architecture projects
  • AI documentation tool collaboration
  • Filmmaking and creative projects

Technical Writer. Information Architect. AI Builder. Filmmaker.