Awesome
Learning technical writing
Just one of the things I'm learning. https://github.com/hchiam/learning
My favourite parts of 2 technical writing courses:
one/summary (click for summary)
tech-writing/two (click for summary)
-
<a href="https://developers.google.com/tech-writing/two/large-docs#:~:text=after%20you've%20completed%20the%20first%20draft%2C%20check%20your%20entire%20document%20against%20the%20expectations%20you%20set%20in%20your%20overview.%20does%20your%20introduction%20provide%20an%20accurate%20overview%20of%20the%20topics%20you%20cover%3F%20you%20might%20find%20it%20useful%20to%20think%20of%20this%20review%20as%20a%20form%20of%20documentation%20quality%20assurance%20(qa)." target="_blank" rel="noreferrer noopener">two: "After you've completed the first draft, check your entire document against the expectations you set in your overview. Does your introduction provide an accurate overview of the topics you cover? You might find it useful to think of this review as a form of documentation quality assurance (QA)."</a>
-
<a href="https://developers.google.com/tech-writing/two/illustrations#:~:text=according%20to%20research%20by%20sung%20and%20mayer%20(2012)%2C%20providing%20any%20graphics%E2%80%94good%20or%20bad%E2%80%94makes%20readers%20like%20the%20document%20more%3B%20however%2C%20only%20instructive%20graphics%20help%20readers%20learn." target="_blank" rel="noreferrer noopener">two: "According to research by Sung and Mayer (2012), providing any graphics—good or bad—makes readers like the document more; however, only instructive graphics help readers learn."</a>
-
two/illustrations#constrain_the_amount_of_information_in_a_single_drawing