- Own end-to-end documentation for African developers building in the Polkadot ecosystem, from first-time guides to deeper technical explainers.
- Work directly with engineers and Web3 community leads to research and verify technical content before publishing, cutting back-and-forth on accuracy.
- Define content structure and tone standards so contributor-authored guides stay consistent and easy to maintain.
Portfolio — updated 2026
Isaac Bayo Arogbonlo
Technical Writer — API, Developer & Product Documentation
I turn dense technical systems into documentation people actually finish reading. Five-plus years writing API references, SDK guides, and onboarding docs, most recently for developer platforms in the Polkadot ecosystem.
§ how I edit — one real pass
Leveraged synergistic off-chain computational paradigms to optimize decentralized throughput.
Moved the expensive work off-chain so the network stays fast.
Same fact. Fewer words standing between the reader and it.
Profile
I write documentation that developers actually use: API references, SDK guides, and onboarding material that holds up against a real integration, not just a skim. Most of my recent work has been in Web3 — helping first-time Substrate developers on Polkadot go from a blank editor to a working feature, and working directly with engineers and community leads to verify technical claims before they publish.
Before documentation, I spent two years as a DevOps engineer. That means I read Python, YAML, HTML/CSS, and REST specs (OpenAPI/Swagger) comfortably on my own, and I understand what a CI/CD pipeline or a container orchestration decision actually costs an engineering team — which shows up in how I structure docs and how little back-and-forth I need from the people who built the thing.
I use AI-assisted tools to move faster through drafts and research, but nothing publishes until I've independently verified it against source code, specs, or the engineer who owns the feature.
Toolkit
- Documentation
- API & SDK documentation, OpenAPI/Swagger, docs-as-code (Git, Markdown, GitHub, Jira), style guides & content standards, content audits & gap analysis, content strategy & SEO.
- Technical fluency
- Reading Python, YAML, HTML/CSS & REST APIs well enough to verify docs against source, plus AI-assisted documentation workflows with critical review before anything ships.
- Infrastructure background
- CI/CD pipelines (Jenkins, GitHub Actions), cloud infrastructure (AWS, Azure, GCP), containers & orchestration (Docker, Kubernetes), DevOps automation & monitoring.
- Collaboration
- Cross-functional work with engineers and Web3 community leads to research, verify, and structure content before it goes out.
Changelog
- Partnered with founders and engineers under NDA to translate product and platform knowledge into technical articles and thought leadership content.
- Audited existing content for gaps and outdated information, restructuring pieces for clarity and tone across technical and non-technical readers.
- Wrote accessible articles explaining software test automation concepts to a broad developer and QA audience.
- Published developer tutorials and platform use-case guides covering setup and integration workflows.
- Simplified DevOps workflows into step-by-step articles and tool explainers, cutting down repeat support questions.
- Built and maintained CI/CD pipelines (Jenkins, GitHub Actions) to automate build, test, and deployment across projects.
- Provisioned and managed cloud infrastructure on AWS, Azure, and GCP to support application hosting and scaling.
- Containerised applications with Docker and orchestrated deployments with Kubernetes to improve release consistency.
- Wrote automation scripts and set up monitoring to catch issues early and keep environments stable.
Writing samples
Introduction to Ink! for Writing Smart Contracts on Substrate
A beginner-focused walkthrough of ink!, the Rust-based smart-contract language for Substrate chains, written for developers building on Polkadot for the first time.
Read the pieceExploring Off-Chain Computation on Polkadot: Possibilities with Substrate Extensions
A practical explainer on off-chain workers and signed extensions in Substrate — when to keep logic off-chain, how a worker fetches and validates external data, and a short code walkthrough building one from scratch.
Read the pieceIs Polkadot Dead? Common Myths Explained
A myth-busting piece unpacking six common misconceptions about Polkadot — parachain security, DOT's tokenomics, and its governance model — for readers who've heard the skepticism but never seen the mechanics underneath it.
Read the pieceMore essays & tutorials
Additional writing spanning Web3 tutorials, DevOps explainers, and essays on technology and human behavior.
Browse the archive