I help developer teams ship documentation that works.

I write API references, tutorials, and concept guides for developer tools—documentation that gets developers up and running faster and keeps support queues shorter.

Available for contract work

Technical writing & UX writing · alex.gekas@gmail.com

I work with
MkDocs · Material for MkDocs · Diataxis · Markdown · REST APIs · OpenAPI/Swagger · JWT authentication · Node.js · Git · GitHub Pages · Vale

Writing Samples Five pieces across API references, tutorials, explainers, and style guides

#	Sample	Audience	Format	Read
01	Task API Documentation Full API reference suite—covers setup, JWT authentication, all endpoints, and error-first troubleshooting Tools MkDocs, Material for MkDocs, Markdown, JWT auth, PM2 How to structure a reference so a developer can go from zero to their first authenticated call without reading the whole thing. Read the case study →	Backend developers, API integrators	API Docs	Read docs
02	Slack Webhook Integration Step-by-step integration tutorial for event-driven Slack notifications via webhook Tools MkDocs, Markdown, Slack Webhooks API, Node.js How to write a tutorial that gives developers enough context to understand what they're doing, while staying out of the way of actually doing it. Read the case study →	Developers, DevOps engineers	Tutorial	Read article
03	GeoJSON Explainer Concept guide explaining GeoJSON spatial data formats for non-engineering audiences Tools MkDocs, Markdown Wrote a GeoJSON concept guide from a minimal specification, translating a technical format into plain language so developers can quickly understand and use NWS API responses. Read the case study →	Product managers, data analysts	Explainer	Read explainer
04	VR Style Guide Writing standards and terminology guidelines for documentation contributed to a VR product—covers voice, tone, and language decisions Tools MkDocs, Material for MkDocs, Markdown Defined voice and terminology for a complex product where standard style guides didn’t apply. Read the case study →	Technical writers contributing to a VR product	Style Guide	Read guide
05	NWS API Reference Full reference for the National Weather Service public REST API—endpoints, authentication, caching patterns, key concepts, and developer use cases Tools MkDocs, Material for MkDocs, Markdown, REST API conventions Making sense of a large public API with inconsistent official documentation—organizing six endpoint categories plus the conceptual groundwork (gridpoints, forecast zones, weather offices) into something a developer can actually navigate. Read the case study →	Backend developers, API integrators	API Docs	Read docs