API references, getting-started guides, how-to guides, and SOPs for SaaS, cybersecurity, and financial services products; written and maintained docs-as-code in Markdown with Git and GitHub.

Tools: Markdown · HTML (basics) · Git and GitHub · VS Code · markdownlint · Mermaid · Confluence · curl

Contact: [email protected] · **linkedin.com/in/georgialainiotis** · GitHub

Below are three documentation samples I wrote and tested independently: an API reference with a Getting Started guide for the Have I Been Pwned API v3, a how-to guide for verifying a business customer's Legal Entity Identifier (LEI), and a standard operating procedure (SOP) for contributing documentation changes through GitHub. Each sample was tested step by step against the live product or tool. The API reference and the how-to guide also point out where the official documentation no longer matches what the product actually does.

You'll also find two articles for technical and business readers: one on composable SaaS architecture, and one on AI-driven cybersecurity threats.


Technical Writing

API Documentation — Have I Been Pwned API v3 (independent project)

Six pages: an overview, a Getting Started guide, three endpoint references, and a changelog.

Published on GitHub: **hibp-api-docs-sample** — the documentation is in Markdown, with its full commit history.

How-To Guide — Verifying a Business Customer's Legal Entity Identifier (independent project)

A task-based guide for KYB analysts at a fictional payments company, built on the public Global LEI Index and tested step by step against the live site. Where GLEIF's own search help page no longer matches the current site, the steps follow the live interface.