2015 archives

  1. Recording of Creating Documentation for Startups: Panel Discussion -- Write the Docs San Francisco

  2. My upcoming 2016 STC Summit workshop and presentation

  3. How do you stay updated with changes developers are silently making?

  4. Those pesky authoring tool questions, and an update on my adventures with Jekyll

  5. Recording of Version Control, Writers, and Worfklows by Richard Mateosian

  6. Question: How long does it take to ramp up on your Jekyll theme?

  7. Swagger UI probably the coolest thing I've done in API docs

  8. 10 realizations as I was creating my Swagger spec and Swagger UI

  9. Guest Post: Could Software Perform Technical Writing? by Robert Desprez

  10. Single sourcing the Swagger spec and main documentation using Jekyll

  11. Version 4.0 released for the Jekyll Documentation Theme

  12. Planning my API doc course

  13. Upcoming Write the Docs Meetup

  14. My pros and cons of using Jekyll for documentation

  15. Can you replace a CCMS with version control such as Git or Mercurial?

  16. Tell me about your career as a technical writer...

  17. Why incremental regeneration in Jekyll 3.0 is such a big deal

  18. Increase efficiency 24 times faster when fixing errors — implications for technical writers on agile teams

  19. Podcast: Spec-driven Development of REST APIs, with a focus on RAML -- interview with Michael Stowe

  20. Udemy podcast (with me) and infographic on technical writing

  21. 5 REST API resources to add to your reading list

  22. Tutorial for creating interactive consoles with RAML

  23. Question: If you weren't a technical writer, what would you be?

  24. Why so little focus on API doc at tech comm conferences?

  25. Question: Can I earn a living blogging?

  26. Question: How long has your API doc course been available?

  27. Question: How are you publishing and delivering your docs?

  28. Question: How do I tell what platform people are using for API docs?

  29. Experimenting with a shorter post style

  30. Added native library API section to API doc course

  31. Upcoming "Ask Me Anything" (AMA) session

  32. Swagger tutorial for REST API documentation

  33. Survey analyzing skill requirements in job postings

  34. Editing workflows and reviews through Github's pull requests

  35. Comparing object-oriented design to content reuse

  36. How authorization works with APIs

  37. What is a REST API?

  38. Proposals for 2016 *STC Silicon Valley Chapter* presentations now accepted

  39. My process for creating vector diagrams with Illustrator

  40. Version 3.0 of my Documentation theme for Jekyll released

  41. Question: What qualities should technical writers have to work at startups?

  42. Podcast: The divide between academics and practitioners -- Interview with Lisa Meloncon

  43. Why is there a divide between academics and practitioners in tech comm?

  44. When are wikis ever successful?

  45. An easy way to support my site: Sign up for technical writing job alerts

  46. Podcast: How do design, length, and relevance affect how people use API reference docs -- interview with Bob Watson

  47. LearningDITA.com: A new online learning resource for DITA by Scriptorium

  48. How do you test content that's beyond your skill level?

  49. Should you add your testing scenarios into your documentation?

  50. Peter Gruenbaum has released part 2 of his Udemy course on API technical writing

  51. Survey results about the possible REST API workshop

  52. Is it inefficient to frequently switch contexts among multiple projects?

  53. Survey about possible REST API workshop — your feedback would be helpful

  54. Getting mobile friendly display and responsive design just right, especially with ads

  55. Reader question: How do I move forward out of a stagnant tech writing career?

  56. Should technical writers care about more than documentation?

  57. Build a technical writing portfolio by writing documentation for startups

  58. Communicating feedback from testing documentation

  59. Guest post: 10 New Things to Love and Hate About Flare

  60. Should QA test documentation?

  61. Listen to Ed Marsh's Content Content podcast with me as a guest

  62. The key to writing good documentation: Testing your instructions

  63. Pingdom reports with WordPress on Bluehost/MaxCDN versus with Jekyll on Github

  64. Three questions people ask me each week

  65. Slides, notes, and lessons learned at the STC Summit 2015 in Columbus, Ohio

  66. My upcoming workshop and presentation at the STC Summit 2015 in Columbus, Ohio

  67. How to avoid early death from sitting down all day

  68. How do you authenticate your documentation?

  69. My daughter published a real video game through "Girls Make Games" camp

  70. Check out my conversation on ContentHug

  71. How can technical writers cut through engineering jargon and decode complex information?

  72. Why no one stopped by my technical writing booth at career fair day

  73. Moved my blog from WordPress to Jekyll

  74. Integrating Documentation into engineering code and workflows

  75. API technical writing course on Udemy from Peter Gruenbaum, and some thoughts on documenting JSON

  76. Switched commenting systems to Disqus

  77. Introduction to technical writing -- slides and audio recording

  78. API Documentation presentation to East Bay STC chapter -- slides and recording

  79. How to design documentation for non-linear reading behavior

  80. Recording and slides from "Jekyll vs. DITA: Bridging the Gap Between Tech Comm and the Web" presentation

  81. User-centered documentation slides

  82. Upcoming presentation: Jekyll versus DITA: Bridging the Gap between Tech Comm and the Web

  83. New series: User-centered documentation

  84. Final analysis between DITA and Jekyll

  85. Producing PDFs in DITA versus Jekyll

  86. Reviewing content in DITA versus Jekyll

  87. Newbie to Technical Writer in 4 Easy Steps

  88. Building a table of contents with DITA versus Jekyll

  89. Creating re-usable chunks (conref) in Jekyll versus DITA

  90. Variables and conditional processing in Jekyll versus DITA

  91. Authoring with Markdown in Jekyll versus Authoring with DITA in OxygenXML

  92. Check out Ed Marsh's podcast, and also My New series: Jekyll versus DITA

  93. Some thoughts on attending tcworld India 2015

  94. PDF still trumps browser-based help?

  95. Recording of API documentation workshop (REST and Javadoc) at tcworld India 2015

  96. Recording of Innovation in Technical Communication keynote at tcworld India 2015

  97. Slides for tcworld India 2015 presentations

  98. Reveal JS: An HTML5 alternative to PowerPoint, with support for SVG graphics

  99. Pushing content into any format with Jekyll

  100. How to create a help API

  101. Static site generators start to replace web publishing platforms like WordPress

  102. Some web tools worth using in help solutions

  103. Piggybacking onto the innovation of the web

  104. Microsoft and the last 5 great technological innovations

  105. Interactive video workshop in San Jose this Saturday, 1-5pm

  106. The genius of Github and how it can transform tech comm

  107. XML and the web: drifting farther apart?

  108. The only significant innovation for tech comm

  109. A long list of technical innovations semi-relevant to technical writers

  110. Sustaining and disruptive innovations

  111. Podcast: The upcoming tcworld India conference on March 12-13, with Akash Dubey

  112. Why do we need PDFs?

  113. Upcoming workshop: Creating Interactive Video Tutorials, with Bernard Aschwanden on Feb 21

  114. Best practices for API documentation -- podcast with Andrya Feinberg

  115. Survival strategies for API documentation -- slides and recording

  116. Creating context-sensitive help by converting your help into a JSON API with Jekyll

  117. Writing is like sorting laundry -- practical advice for tackling documentation projects

  118. 10 reasons for moving away from DITA

  119. API workshop video + audio + slides + workshop files from TC Camp

  120. Reinventing the table of contents

  121. Implementing ScrollSpy with Jekyll to auto-build a table of contents

  122. Moving from passive to reactive documentation -- recording of presentation by Greg Koberger, ReadMe.com founder

  123. Most important factor in APIs is complete and accurate documentation

  124. API doc survey: Do engineers write API doc in the source code?

  125. API doc survey: How much of your doc process is automated?

  126. Several REST API tutorials using the EventBrite, Klout, and Flickr APIs

  127. Experimenting with Jekyll for tech comm

  128. API doc survey: Most challenging aspect of API documentation

  129. Jan 12 Silicon Valley STC meeting: Passive vs. reactive doc + readme.com

  130. Question: How do I add my DITA content in Confluence for SME review?

  131. Podcast: Unifying the API doc publishing toolchain, with Mark Baker

  132. API doc survey result: How to learn what you need to know?

  133. API doc survey result: How do you get the source files that contain code comments?

  134. API doc survey result: Automating REST API documentation

  135. Podcast: Automating REST API documentation, with Peter Gruenbaum

  136. New cost-per-click feature for advertising on I'd Rather Be Writing During 2015

  137. My *real* top 10 technical writing trend predictions for 2015

  138. Top 10 posts, podcasts, tweets of 2014 -- and what it all means

  139. API doc survey: Do you create API doc by looking at source code?

  140. API doc survey: What IDE do you use?

  141. API doc survey: Do you test out the API calls used in your doc yourself?

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.