Presentations and Publications

Wrote a blog post for technical writers exploring Redocly for their API documentation.

In this episode, I was interviewed by Zohra Mutabanna, where I shared my thoughts on the evolution of technical communication in Australia, especially since the pandemic.

Successful API products have always been around before then, but we have all missed signs until 2020. What is the secret sauce behind successful APIs and their uptake?

In this episode, I was interviewed by the host of the Not Boring Tech Writer podcast to talk about the Write the Docs Australia community and what tech writer advocacy involves.

In my talk, I take share some of my frustrations (turned into learnings) on how technical writers can bring their tech game to the table when it comes to products, and make a huge impact by establishing documentation tools, processes and workflows.

In this talk, I offer my recommendations on making our content sustainable, especially now when our content is growing at an unprecedented rate. As part of the conference theme, I compare content with the key principles of sustainability such as reducing waste, creating maximum impact, placing emphasis on longevity and relevance, and providing a sense of social responsibility or governance.

This is a presentation I gave at STC Summit 2019 and Madworld 2018 about the importance of Release Notes in product development and how they can help shape your initial conversations with customers.

This is a presentation I gave at Write the Docs Prague 2016 about my experiences of working with teams that do not understand the value of providing good screenshots for documentation.

Wrote a guest blog post for KnowledgeOwl on why the review is the most critical piece of the documentation process.

Wrote a guest blog post for KnowledgeOwl about how I got started with API documentation.

In this episode, I joined the Write the Docs podcast team to talk about the Write the Docs Australian conference and more.

Wrote a guest blog post for Madcap Software, around justifying the use of single sourcing in documentation.