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
API Documentation
REST API documentation created as the final project for the University of Washington API documentation course.
Mobile App Documentation
Coming soonDocumentation for a mobile application that adapts my technical writing approach to a different product type.
Process
The live Jira project is available on request. If you'd like view-only access, contact me and I'll grant you access.
What started as an overwhelming set of ideas became a structured workflow. I broke it down into epics, sprints, and tasks. Jira is integrated with GitHub, so tickets connect directly to commits and deployments.
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.
If You Love Writing, Technical Writing Might Frustrate You
Good writing habits can work against you in technical writing. Here's why clarity, not style, makes the difference.
Contact
If you'd like to connect, discuss ideas, or ask about the project: