humanizing your documentation
play

Humanizing Your Documentation bit.ly/docs-talk-resources - PowerPoint PPT Presentation

Humanizing Your Documentation bit.ly/docs-talk-resources @carolstran Why do we write documentation? Tyner Blain - bit.ly/goal-drive-docs Use case driven documentation Tyner Blain - bit.ly/use-case-docs Tyner Blain - bit.ly/goal-drive-docs


  1. Humanizing Your Documentation bit.ly/docs-talk-resources @carolstran

  2. Why do we write documentation? Tyner Blain - bit.ly/goal-drive-docs

  3. Use case driven documentation Tyner Blain - bit.ly/use-case-docs

  4. Tyner Blain - bit.ly/goal-drive-docs

  5. How to adjust the speed How to change the direction How to change the drill bit Tyner Blain - bit.ly/goal-drive-docs

  6. How to drill a hole in a flat surface How to select the right screw How to stir paint with your drill Tyner Blain - bit.ly/goal-drive-docs

  7. Who do we write documentation for? @carolstran

  8. Humans @carolstran

  9. @carolstran

  10. Slack API Portal - bit.ly/slack-docs

  11. Making messages interactive Subscribing to Event Types Events API vs. RTM API Slack API Portal - bit.ly/slack-docs

  12. Slack API Portal - bit.ly/slack-docs

  13. Goal Use Case Tyner Blain - bit.ly/use-case-docs

  14. Goal Use Case Functional Requirement Design Implementation Tyner Blain - bit.ly/use-case-docs

  15. Goal Use Case Functional Requirement Design Implementation Tyner Blain - bit.ly/use-case-docs

  16. Goal Use Case Functional Requirement Design Implementation Tyner Blain - bit.ly/use-case-docs

  17. This is cool @carolstran

  18. But it doesn’t happen @carolstran

  19. JavaScript @carolstran

  20. What’s going on? Why is this so confusing? Do people actually enjoy this? @carolstran

  21. No one wants to read your docs @carolstran

  22. No one wants to read your docs @carolstran

  23. People don’t mind reading docs… @carolstran

  24. …as long as they’re actually helpful @carolstran

  25. Ethan McQuarrie - bit.ly/EthanMcQuarrie-tweet

  26. Killian McMahon - bit.ly/kilmc-tweet

  27. Leigh Momii - bit.ly/jetleigh-tweet

  28. Leigh Momii - bit.ly/jetleigh-tweet

  29. Leigh Momii - bit.ly/jetleigh-tweet

  30. If only developers cared about docs… @carolstran

  31. If only developers cared about docs… @carolstran

  32. Writing docs is only part of the job @carolstran

  33. The words we choose Lucie Le Naour - bit.ly/wtd-lucie

  34. Insensitive language @carolstran

  35. If the programmer wishes to uphold the invariant, he must satisfy the function’s preconditions

  36. Problematic but common terms @carolstran

  37. Master / Slave Whitelist / Blacklist

  38. Think before you type @carolstran

  39. Primary / Replica Denylist / Allowlist @carolstran

  40. bit.ly/alex-js

  41. bit.ly/alex-js

  42. Linters aren’t a replacement for human editing @carolstran

  43. Tatiana Mac - selfdefined.app

  44. Saying ‘simply’ or ‘easy’ @carolstran

  45. Don’t say it @carolstran

  46. Be specific Jim Fisher - bit.ly/dont-say-simply

  47. Be comparative Jim Fisher - bit.ly/dont-say-simply

  48. Be absolute Jim Fisher - bit.ly/dont-say-simply

  49. Show, don’t tell Jim Fisher - bit.ly/dont-say-simply

  50. bit.ly/write-good

  51. write-good *.md write good - bit.ly/write-good

  52. Bloated language @carolstran

  53. Plain language @carolstran

  54. hemingwayapp.com

  55. “No one has ever complained that something was too easy to read” Ashley Bischoff - bit.ly/ashley-fronteers

  56. Unexpected errors @carolstran

  57. Address common errors @carolstran

  58. What might happen Potential reasons why What to do next @carolstran

  59. Apple Computer Inc - bit.ly/appleII-manual

  60. Django Girls - bit.ly/django-girls-tut

  61. You’re in too deep @carolstran

  62. Everyone is a beginner at some point @carolstran

  63. Take a step back @carolstran

  64. The code we write @carolstran

  65. Code snippets shouldn’t be screenshots @carolstran

  66. <code> for inline MDN <code> docs - bit.ly/mdn-code

  67. <pre> for blocks MDN <pre> docs - bit.ly/mdn-pre

  68. ```javascript Markdown Cheatsheet - bit.ly/md-cheatsheet

  69. Foo / Bar / Baz @carolstran

  70. Meaningful placeholders @carolstran

  71. “We can have variable names that are both meaningful and generic that expose their purpose via their semantics” Eli Schütze Ramirez - bit.ly/elibelly-reply

  72. var baz = [‘foo’, ‘bar’]

  73. var fruits = [‘apple’, ‘banana'] MDN JS array docs - bit.ly/js-array-mdn

  74. var array_name = [‘item1’, ‘item2’]

  75. The structure of our documentation @carolstran

  76. Poorly defined structure @carolstran

  77. Mindful structure @carolstran

  78. Explain the feature Describe the use case(s) Recommend tooling @carolstran

  79. Your product isn’t the right solution @carolstran

  80. Be transparent @carolstran

  81. bit.ly/reasonml-docs

  82. Final note @carolstran

  83. Accuracy and consistency @carolstran

  84. Aim to be honest, helpful and human @carolstran

  85. bit.ly/docs-talk-resources @carolstran

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend