Technical Writing Portfolio
Ewa Jabłońska
Technical writing is more than content.
This portfolio explores how documentation, tooling, and process come together in practice. It reflects that through projects, experiments, and continuous learning.
Concept
Technical writing does not exist in isolation.
Documentation, tooling, and process overlap and influence each other. I use this diagram to show how these areas connect.
This portfolio explores those connections across projects and experiments, rather than presenting isolated writing samples. Each section focuses on a different part of that concept.
Projects
Three projects, three kinds of documentation. Each one is written for people and for the AI tools that now read documentation alongside them, and each one shows how documentation helps a product get used, understood, and chosen.
- Finished
Quoteable Service API
REST API documentation created as the final project for the University of Washington API documentation course: endpoint structure, tutorials, and reference.
API documentation Reference Tutorial - In progress
Promo Video Skill
Documentation for an AI skill, written so that both the people who use it and the model that runs it can understand what it does, when to use it, and where its limits are.
AI-friendly Skills Product - In progress
NieZamulaj
Printable chore boards for families, built and documented with AI as a working partner. The documentation covers the product itself and the story around it: what it is for, who it helps, and why they would pick it.
AI-assisted User documentation Product
Process
What started as an overwhelming set of ideas became a structured workflow. I broke it down into epics, sprints, and tasks in Jira. I work with Jira every day through its connections to Claude, ChatGPT, and GitHub, so planning, AI-assisted work, and commits stay linked.
I also use Confluence to document the process itself. Together, these tools show not just the outputs, but how I plan, organize, and deliver the work.
Blog
Posts from my earlier technical writing blog, revisited and updated to reflect how I approach the field today.
This section remains a space for exploring ideas, approaches, and questions around technical writing.
How technical writers can use Excel in their daily work
A practical guide to time tracking, task tracking, documentation checks, and small automations.
Contact
If you'd like to connect, discuss ideas, or ask about the project: