February technical writing digest is here!
When you add maps, graphs, charts, infographics, dashboards, etc. to text, you are doing a big favor to readers and yourself. Using visualization techniques as a complementary tool to explain written text brings a lot of value. Your user manuals become more readable.
Learn some tips on how to efficiently implement data visualization in technical docs.
This is a (fairly) brief overview of how the Monzo team writes. It’s for everyone in every team, and it applies to all the writing they do, inside and out.
They’ve opened this up to the world as well, because they want to be held up to the lofty standards they set themselves here.
In this post, the author is going to give you some of that information: what things you should care about when building your docs, and how those things will make the choice of tool the least important thing.
In some technical writing teams, MS Word is still used because documentation is undervalued in such companies and it’s created only as a compulsory measure. Your business definitely needs documentation, but this topic is complicated to describe all the advantages of documentation for your business. However, Ann Green will cover the key principle here — a help authoring tool will improve your writing process, and, as a result, your business.
In this article, Paul answers the question, What does Expert Support recommend for the contents of an ideal documentation suite for software targeted at software developers?
2020 Wellness Theme & Goals // Preventing Burnout // Healthy Life in Tech
Video by Amruta Ranade on healthy life in tech.
How did I become a technical writer? What skills do you need? Read FAQ on Technical Writing.