API and developer documentation
API references, integration guides, tutorials, setup instructions, and other developer-facing content.
Alex Gekas, technical content writer
Technical content for software, APIs, and SaaS
I write API documentation, developer tutorials, technical articles, and search-focused content that makes complex products easier to understand.
Available for new projects
Writing samples
Independent projects and rewrites of public documentation, organized by type of writing. Each sample opens with a short brief on its audience and purpose.
Audience
Backend developers adding weather data to an app.
Purpose
Reorganize a large public API by use case, with a quick start and key concepts.
Audience
WordPress developers comfortable with PHP.
Purpose
A step-by-step plugin build where every step ends in a testable result.
Audience
Product managers, analysts, and developers new to map data.
Purpose
Explain a data format in plain language, using real NWS responses.
Audience
Developers using a small REST API.
Purpose
Setup, authentication, reference, and a troubleshooting guide organized by symptom.
More samples, including a Slack integration tutorial, on my GitHub portfolio →
What I write
Technical content
Blog articles, explainers, case studies, and product education for technical audiences.
Knowledge base and product help
Help center articles, onboarding content, FAQs, troubleshooting guides, and product documentation.
SEO and AI search content
Technical content structured so Google, AI search tools, and answer engines can find and cite it, written for people first and never keyword-stuffed.
Hands-on technical experience
I write about technology I’ve used. I build test stores, call the APIs, and run the code in my tutorials before I document it.
- WordPress and WooCommerce
- Stripe payments and webhooks
- REST APIs (cURL, Postman, JavaScript)
- SaaS and web platform workflows
- Git and GitHub
- Docs as code (Markdown, MkDocs, Vale)
- Basic front-end development (HTML, CSS)
Stripe Professional Payments DeveloperVerify credential → How I work
Understand first.
Write second.
Good documentation starts with knowing how the product actually behaves, so I get hands-on before I write.
Learn the product and the reader
I read your existing docs, use the product or API myself, and confirm who the content is for.
Plan the structure
I outline before drafting, so each page has one job and fits the rest of your content.
Write and test
I draft in plain language and run every command, code sample, and step I document.
Review and deliver
You review a draft. I revise, check it against your style guide (or Google's), and deliver in the format you publish with.
About
I’m Alex Gekas, a technical writer focused on developer documentation and SaaS content. My background is in enterprise IT support, bilingual technical support, and communications, where the job was explaining technical systems to the people who rely on them.
I hold a Duke Technical Writing Certificate and the Stripe Professional Payments Developer certification, and I’ve contributed to The Good Docs Project, an open-source community that builds documentation templates. I’m most interested in APIs, payments, and SaaS products. I speak English, French, Greek, and Polish.
Get in touch
Need clear technical content for your product? Let's talk.
Tell me what you’re working on: the product, who reads the content, and what you need written. I’ll reply within one business day.
Prefer email? alex.gekas@gmail.com
LinkedIn · GitHub portfolio