Friday and we have another Readings issue on content. Today’s issue includes taxonomy standards, IA for phone, DITA2.0. ROI of documentation, Confluence for UX documentation, headless and not brainless CMS, and Minimum Viable Content!
Since “taxonomies” are rather loosely defined, standards specifically for taxonomies do not exist, but there are standards that are relevant to taxonomies.
We wanted to look at: how many support calls an organisation needs to have resolved by users reading the Help content instead of calling Support, before it starts to see a return on the cost of creating the Help.
Why is Confluence our tool of choice when it comes to documenting UX design concepts? The answer: collaboration, flexibility, and creating a single source of truth.
So began Mirhonda Studevant’s (@okKMchef) twenty-five minute Information Development World presentation, one of the most compelling talks on empathy in content I have ever heard.
With the rising buzz of headless CMS, comes the rising misunderstanding that CMS systems must fall into one of two categories: fully headless systems that require a…
The problem-solving information our Technical Authors create can also attract prospects to your website. It helps convert your trial users into paying clients. It can also reduce your support team’s workload.
Tweet
Share