— KnowledgeOwl's blog for knowledge base knacks and hacks
It’s important to get a sense of how your knowledge base is performing in order to continuously improve your content. More importantly, you must actually do something productive with the information you gather. Turn information > insights > action with these five easy steps.
Why you should use metadata in your knowledge base articles.
Learn 8 best practices to ensure your knowledge base articles are consistent and easy to understand.
A roundup of tools to help you create screenshots for your documentation.
From MailChimp to Airbnb, there are a number of companies that have struck gold with their knowledge bases. We share four examples with you.
As the famous Stephen King said of writing, you should “kill your darlings”. This means we need to let go of things that we feel emotionally attached to but are no longer serving us, which is a big part of the KonMari approach. This idea applies to our documentation as much as anything else.
Here are four tips you can use to make customers aware of its existence and drive traffic to your knowledge base.
Data governance defines who (within a company) can use and manage data. Tech writers will be increasingly involved in this work, and affected by data management.
This article suggests tha technical writers should also be UX advocated. It looks at what UX is, and how UX concerns overlap with tech writing.
Things you don’t think about that are reflections of your brand (hint: some of these are in your docs) - by Gwynne Monahan
Your company brand can be represented in everything you publish, including sections of your docs such as release notes.