Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: how to write documentation #3948

Open
lnielsen opened this issue Jul 22, 2019 · 2 comments
Open

docs: how to write documentation #3948

lnielsen opened this issue Jul 22, 2019 · 2 comments

Comments

@lnielsen
Copy link
Member

Write a new section that defines how to write documentation.

  • Review examples from other libraries (e.g. django)
  • Brainstorm in sprint what the policy should look like.
  • Write it :-)
@monaawi monaawi assigned monaawi and unassigned monaawi Jul 23, 2019
@vlad-bm vlad-bm self-assigned this Jul 24, 2019
@diegodelemos diegodelemos self-assigned this Jul 24, 2019
@vlad-bm
Copy link

vlad-bm commented Jul 29, 2019

[Draft] Document Structure

  • General style and tone
  • Writing structure, language and grammar
  • Technical writing style guidelines
  • Highlighting and formatting
  • Code samples
  • API documentation
  • Test-driven documentation
  • Diagrams
  • Deprecation, Notes, Warnings
  • File structure
    • AUTHORS
    • CHANGES
    • CONTRIBUTING
    • INSTALL
    • README
    • OVERVIEW
    • RELEASE-NOTES
    • init.py
  • Do's and Don'ts
  • FAQs

@ntarocco
Copy link
Contributor

ntarocco commented Apr 5, 2020

@lnielsen @slint
I summarized here a few notes that might be useful for us from the technical writing course by Google, I hope it can help:

  • acronyms: always spell out the full term before use it extensively
  • pay attention when using it,their, this, that` (more details here)
  • prefer active voice from passive voice in simple sentences:
    • A wrapper is generated by the Op registration process. -> The Op registration process generates a wrapper.
    • imperative verbs are typically active:Open the configuration file.
  • prefer strong verbs: any form of be but also occur and happen are weak verbs.
  • limit the use of there is or there are
  • write short sentences, limiting subordinate clauses
    • use lists (bullet points or numbered list)
    • use imperative verbs in list items, punctuate items appropriately
  • understand when to use which and that
  • write great opening sentences:
    • busy readers focus on opening sentences and sometimes skip over subsequent sentences
    • should contain what, why, and how
  • Write in the second person. Refer to your audience as "you" rather than "we".
  • Place conditional clauses before an instruction, rather than after (See [link to other document] for more information. -> For more information, see [link to other document].)
  • Provide text under each heading:
    ## Creating the site
    Some text
    ### Running the carambola command
    Some text
    
  • Disclose information progressively

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants