Technical writing portfolio

Ewa Jabłońska

Technical writing is more than content.

This portfolio explores how technology, product, and users connect. AI can help create documentation, but a technical writer must always keep these three areas in mind.

  • Technology
  • Product
  • Users

Concept

Technical writing does not exist in isolation.

Technology, product, and users overlap and influence each other. I use this diagram to show how these areas connect.

Technology, Product, and Users: where each skill meets a project Venn diagram with three areas: Technology, Product, and Users. Promo Video Skill is where Technology and Product meet. StickerStart is where Product and Users meet. Quoteable Service API is where Technology and Users meet. In the centre: Technical Writer + AI. Technology Product Users Promo Video Skill Quoteable Service API StickerStart Technical Writer + AI Technology, Product, and Users: where each skill meets a project Venn diagram with three areas: Technology, Product, and Users. Promo Video Skill is where Technology and Product meet. StickerStart is where Product and Users meet. Quoteable Service API is where Technology and Users meet. In the centre: Technical Writer + AI. Technology Product Users Promo Video Skill Quoteable Service API StickerStart Technical Writer + AI

Projects

Three projects. Each one is where two areas meet. Documentation is at the centre of each one.

  • Technology + Product Docs for people and AI

    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. I also made a pull request that makes the skill work on Windows and with non-English voiceovers. It is merged.

    • Documentation
    • AI skills
    • Pull request
    In progress
  • Product + Users Brand, marketing, adoption

    StickerStart

    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
    In progress

Process

What started as an overwhelming set of ideas became a structured workflow. I plan the work in Jira: epics, sprints, and tasks. Claude Code reads a task and makes the changes in GitHub. I set the direction for each task. I check each change in a local preview and review the pull request before it goes live.

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.

View Confluence process documentation

Blog

Posts from my earlier technical writing blog, revisited and updated to reflect how I approach the field today.

Latest post

How technical writers can use Excel in their daily work

A practical guide to time tracking, task tracking, documentation checks, and small automations

  • Tools
  • Excel
  • Technical writing

View all posts

Contact

Do you want to talk about documentation for people and AI? Write to me: