1. Part VII: Conclusion (Value arguments for docs and tech comm)

  2. Part VI: Deepening documentation's value by simplifying complexity (Value arguments for docs and tech comm)

  3. Part V: Influencing the content experience (Value arguments for docs and tech comm)

  4. Part IV: Enabling information flow (Value arguments for docs and tech comm)

  5. Part III: Determining value through usage (Value arguments for docs and tech comm)

  6. Part II: Reviewing past research (Value arguments for docs and tech comm)

  7. Value arguments for docs and tech comm — Part I: Introduction

  8. Why is TC Camp's unconference format so popular? Interview with Liz Fraley, TC Camp Founder

  9. WTD Episode 12: Founding ideas behind Write the Docs

  10. Biking down Coyote Creek Trail

  11. How to become a voracious reader

  12. WTD Podcast Episode 11: Exploring the Mozilla Developer Network's Web Docs project

  13. How do you communicate user progress in a course without a Learning Management System (LMS)?

  14. Case study: Switching tools to docs-as-code

  15. Intro to API Documentation -- recording of presentation to STC Silicon Valley chapter on 11/20/2017

  16. Balancing writing, editing, and learning in equal measures

  17. New OpenAPI 3.0 specification tutorial in my API Course

  18. The Untold Story of Techwriter.pl: A Polish website about technical communication for technical writers, trainers, and translators

  19. Question: Which software tools should I use if my goal is to write API docs?

  20. WTD Episode 10: What's going on in our lives as documentarians and product owners

  21. SwaggerHub: A collaborative platform for working on OpenAPI/Swagger specification files, and more

  22. Convert Google Docs content to Markdown or HTML using the gd2md-html add-on

  23. Has plain language deepened or ruined our delight in language?

  24. Write the Docs Podcast Episode 9: Chatbots in Documentation

  25. Discoveries and realizations while walking down the Docs-as-Code path

  26. Why Stack Overflow's Documentation effort failed -- a few thoughts from a technical writer's perspective

  27. Tech docs and Agile: Alternatives to integrating into engineering Scrums (Part 2)

  28. Tech docs and Agile: Problems with integrating tech writers into engineering Scrums (Part 1)

  29. Why simple language isn't so simple: the struggle to create plain language in documentation

  30. When the pain of ignorance exceeds the pain of learning

  31. Transparency in documentation: dealing with limits about what you can and cannot say

  32. Write the Docs Podcast Episode #7: Let The Robots Do The Work

  33. Circle review -- How to manage your kids' access to Internet devices

  34. My second-chance points strategy with documentation

  35. The problem with Frequently Asked Questions (FAQs) in documentation

  36. Recording of my WTD Portland 2017 presentation on Building navigation for your doc site -- 5 best practices

  37. Write the Docs Podcast Episode #6: Metadata and UI copy

  38. Limits to the idea of treating docs as code

  39. How big should your documentation repo be?

  40. Impressions from the Write the Docs Conference -- and thoughts on achieving sustainability without selling out to vendors

  41. Slides for Write the Docs Portland presentation on doc navigation best practices

  42. Testing your documentation -- updates in API doc course

  43. Write the Docs Podcast Episode 5 -- Where do we belong?

  44. My Calm Meditation app -- another experiment to test my docs

  45. Tutorial on converting an HTML site into a Jekyll theme

  46. Following instructions involves learning a new language -- adventures with Tinker Crate projects

  47. Write the Docs Podcast app now on Fire TV, and the importance of testing your docs with sample apps

  48. Amazon begins pilot with voice-interactive user manuals

  49. Tutorials versus docs -- why you need both

  50. Moved my API doc site into separate repo

  51. Simplifying my life and writing

  52. Guest post -- The effects of terminology consistency on the reader's comprehension and attitude

  53. Crowdsourcing docs with docs-as-code tools -- same result as with wikis?

  54. Write the Docs Podcast Episode 4 -- Continuous Integration and Docs as Code

  55. Adobe FrameMaker 2017 -- time, tools, and the tech writer’s focus on content

  56. Upcoming 2017 Write the Docs Conference in Portland

  57. Guest Post -- MadCap Central: A Review for Companies Delivering Technical Communication Services

  58. How do you learn what you need to learn to be successful as a technical writer?

  59. Guest post: Design choices for organizing API reference content with other documentation

  60. Recording of User-Centered Design Principles for Organizing Documentation

  61. Write the Docs Podcast #3 - Trends for 2017

  62. Technical Writing Trends and Predictions for 2017

  63. Simplified Technical English and HyperSTE

  64. Recording: Modern Technical Writing, by Andrew Etter (STC Silicon Valley chapter)

  65. Recording: Writing tech docs like a hacker with Jekyll

  66. My top 3 posts of 2016 are all Swagger-related -- lessons learned from 2016 analytics

  67. Swagger presentation recording -- Harnessing the Chi of Swagger in your REST API documentation

  68. FrameMaker and the mobile web: Evaluating Adobe FrameMaker's responsive HTML5 output

  69. MadCap Central -- a first look at MadCap’s new cloud-based collaboration and publishing solution

  70. How much code do you need to know to create API developer documentation?

  71. Attend my upcoming TC Dojo presentation on Swagger on Jan 9, 2017

  72. TC Camp in Santa Clara to be held Jan 21, 2017


Stay current with the latest in tech comm
Keep current with the latest trends in technical communication by subscribing to the I'd Rather Be Writing newsletter. 4,500+ subscribers