— KnowledgeOwl's blog for knowledge base knacks and hacks
This blog post covers some ideas on building a tech writing portfolio, along with my recent personal experience of building a portfolio using a combination of Markdown, Git, and a Static Site Generator.
Here's a guest post from technical writer Swapnil Ogale about how he got into writing API documentation.
What kind of etiquette should you use when attending Zoom meetings with your coworkers? Is there even a consensus at all? It’s a hot topic, so read on!
This short article will introduce the practice of docs like code: what it is, its pros and cons, some of the skills and tooling involved, and how to decide if it’s right for you.
Information Architecture describes the way we organize data in a website, knowledge base, wiki, software interface, or information technology system. However, as an abstraction of what you actually build, you might encounter challenges when turning that vision into something more tangible.
As much fun as stories are, when we play out these dramas in real life, conflict inevitably occurs. This is a particular risk when it comes to working in customer support, because you are working directly with people.
Customers use our software in the course of their work, in jobs which are often complex, demanding and stressful. When they ask us puzzling questions, it’s our job to decode their true meaning, so we can provide the best support experience possible.
The value of a knowledge-centered business is more obvious during times of stress. You have already captured what is important for use at a later date. And if you haven’t been capturing knowledge already, it’s never too late to start.
We need to meet regularly to review and make decisions on bug reports and feature requests from our customers, and we use a combination of tools to make this happen.
Here are some suggestions on tweaks or features you can use in KnowledgeOwl to help streamline some of those new processes.