2016 archives

  1. Generalist versus specialist: What should you focus on with knowledge building in your tech writing role?

  2. Write the Docs Podcast Episode 2 (which Focuses on Findability) Now Available

  3. Updating a single page versus updating the documentation as a whole

  4. Write the Docs Podcast episode 1: New podcast from the Write the Docs community

  5. Recording of Open Authoring -- Collaboration Across Disciplines presentation, by Ralph Squillace

  6. Review of Coding for Writers course by Peter Gruenbaum on Udemy

  7. How to avoid becoming extinct in your technical writing career

  8. How to get crisp text callouts like in Apple's new Touch bar documentation -- and why you might not want to with translation projects

  9. Markdown or reStructuredText or DITA? Choosing the right format for tech docs

  10. How to tell if you're a content strategist

  11. Apple's Two-Step Verification versus Two-Factor Authentication, or, When Marketing's lingo makes it impossible to communicate with plain speech

  12. How to respond to product disasters: Analyzing Samsung's response to their exploding phones in contrast to Dyn's response to the DDoS attack

  13. How to deliver newsletters for your Jekyll site

  14. Coding the sidebar navigation element for documentation websites

  15. From podcasts to audio books and now back to podcasts -- experimenting with a new angle

  16. Saving Your Sanity Through Better Client Relations -- with Alisa Bonsignore

  17. My gravity towards tools

  18. Zooming out and in with navigation

  19. Kanban may be a better fit than scrum when you support large numbers of engineers

  20. How can technical writers thrive in agile environments? Event recording and details

  21. Implementing Swagger in your API documentation -- My ISTC article

  22. Recording of Let's Tell a Story -- Scenario-Based Documentation, by Matt Ness (STC Silicon Valley Presentation)

  23. Balancing the never-ending list of documentation to write with your natural interests and passions

  24. The variety of tools tech comm professionals use

  25. Presentation recording: Hunting for API developer documentation jobs in the San Francisco Bay area, by Andrew Davis

  26. The complexities of translation and the need for dynamic variables in the build process

  27. Will the docs-as-code approach scale? Responding to comments on my Review of Modern Technical Writing

  28. The Story of Paligo: A new browser-based CCMS with all the features you'd ever want

  29. Review of Andrew Etter's ebook on Modern Technical Writing

  30. Applying Tim Ferriss' 4-hour work week rules to tech comm projects

  31. Thoughts on Transforming Documentation Processes presentation at WTD: Evaluating the trend to treat documentation as code

  32. Context switching and efficiency -- Kanban to the rescue?

  33. Why Programming Sucks and the fallacy of documentation in the context of code chaos

  34. Thoughts on Documentation Avoidance for Programmers

  35. How the Solve This! meetup format turned out -- plus some unachieved parallels with the Dead Poet Society

  36. The difference between marketing writing and technical writing in one small sign

  37. A jump in Google traffic due to content quality?

  38. Attend the "Solve This!" Write the Docs Meetup tomorrow (June 23, 2016)

  39. Examples of visual communication in developer documentation with the Android Vocabulary Glossary

  40. My technical communication contribution to the UX Careers Handbook

  41. Advanced formatting with Markdown using Jekyll and Includes

  42. More complex user process maps in documentation systems

  43. Interested in working as a technical writer at Amazon?

  44. Examples of linear workflow user maps built with JS and CSS

  45. 8 image translation issues for tech doc — guest post by Jeanine Shepstone

  46. 11 images issues for tech doc systems — guest post by Jeanine Shepstone

  47. Presentation recording: Move Fast And ... Document Things? Lessons learned in building documentation culture at a startup, by Ruthie Bendor

  48. Recording of 'Move fast and ... document things,' by Ruthie Bendor at Write the Docs

  49. Recording of 'Two great teams that work great together: Bridging the gap between documentation and support,' by Neal Kaplan at Write the Docs

  50. Some post-STC Summit thoughts

  51. Slides for Writing Tech Docs Like a Hacker with Jekyll presentation

  52. Slides for Documenting REST APIs Workshop — 2016 STC Summit Anaheim, Calif.

  53. How do you establish more context in a topic-based writing model?

  54. Getting sharp, clear text in screen captures — and making sense of Retina displays

  55. Jekyll Conf 2016 slides and video: Overcoming Challenges in Using Jekyll for Tech Docs

  56. Creating professional looking graphics in the easiest, simplest way possible

  57. Visual communication overview

  58. Three types of knowledge every technical writer needs to be successful

  59. Recording of WTD presentation on Video Documentation, by Alicia Avrach

  60. Recording of STC-SV presentation on the Shape of a Modern Technical Communication Organization, by Sanborn Hodgkins

  61. Seeing things from the perspective of a learner

  62. Eight reasons why documentation fails for users, and what to do about it

  63. API documentation workshop opportunity at the STC Summit

  64. Lightning talks from San Francisco Write the Docs meetup

  65. Xeditor, a CMS editor for XML content

  66. REST API documentation workshop recording (STC Sacramento)

  67. Version 5.0 of my Documentation Theme for Jekyll now available

  68. Hi there – Let’s get casual… Guest post by Lavanya Krishnamurthy

  69. Shannon got into Stanford's MA Liberal Arts program

  70. Selling Girl Scout cookies

  71. Starting a new series on visual communication

  72. 10 minute podcast on API technical writing with Ryan Weber on Stitcher

  73. Retrospective — Looking back at the good and bad of previous experiences

  74. So People Don't RTFM? Write a FM That's Worth R'ing — Guest post by Marcia Riefer Johnston

  75. Lightweight DITA article in Technical Communication Journal

  76. I'm starting a new job at Amazon Lab126

  77. Answering questions in James Gill's upcoming book, How to Get Started as a Technical Writer

  78. What is the ideal tool for developer documentation environments?

  79. Updating from redcarpet and Pygments to Kramdown and Rouge on Github Pages

  80. Why didn't WordPress take off with tech docs?

  81. Two upcoming API documentation events this Thursday

  82. Is the only way to plug into a documentation CCMS through DITA/XML?

  83. Three models for single source publishing — and challenges with each

  84. My YAML tutorial in the context of Jekyll

  85. The third API course from Peter Gruenbaum on Udemy

  86. Upcoming REST API documentation workshop in Sacramento

  87. New section in API documentation course: The Job Market for API technical Writers

  88. Challenges in documenting long JSON objects

  89. How to apply agile processes to manage your life's projects

  90. The problem with adopting bleeding-edge tools

  91. Spec-driven Development with RAML -- presentation by Michael Stowe to STC Silicon Valley chapter

  92. First video for API documentation course -- your feedback?

  93. Are technical writing blogs growing or dying?

  94. What is the technical writer's role in content marketing?

  95. Analyzing top posts on my blog during 2015 — Deciding between brand versus readership

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.