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

Chapter on how to write documentation for a project #2020

Open
pgadige opened this issue Jul 8, 2021 · 5 comments · May be fixed by #2854
Open

Chapter on how to write documentation for a project #2020

pgadige opened this issue Jul 8, 2021 · 5 comments · May be fixed by #2854
Labels
book-dash-nov22 This label is for Book Dash 2022 related issues and PRs communication-book Content for communication book idea-for-discussion This can be used for inviting discussion from collaborators or community in general

Comments

@pgadige
Copy link
Collaborator

pgadige commented Jul 8, 2021

Summary

Write a short chapter on writing minimal and complete project documentation. The chapter will be a useful guide for project owners to get started with writing documentation for their projects.

Discussion Points

List of tasks:

  1. Identify a pattern across documentations of commonly used scientific packages like matplotlib, scipy, numpy, bokeh, xarray
  2. Briefly explain (in 1 or 2 sentences) the purpose of each documentation element found in the above pattern
  3. Design a generic project documentation template (or outline) for project owners to use in their projects.

Resources

Documentations of commonly used scientific packages:

  • Matplotlib
  • Bokeh
  • Scipy
  • Numpy
  • Xarray

Who can help?

Collaborators: @malvikasharan

Updates

  • discovered the following common elements found in documentations across commonly used scientific software packages
  1. Project design
  2. First steps guide
  3. User guide
  4. API reference (or reference guide or API overview)
  5. Releases
  6. Project roadmap (or development roadmap)
  7. Usage examples (or tutorials or demos)
  8. Community
  9. Troubleshooting FAQs
@pgadige pgadige added communication-book Content for communication book idea-for-discussion This can be used for inviting discussion from collaborators or community in general labels Jul 8, 2021
@malvikasharan
Copy link
Collaborator

@malvikasharan
Copy link
Collaborator

Fab example from Rachel: https://programmer-rachel.medium.com/

@bouweandela
Copy link
Collaborator

This looks related to #879.

@amangoel185 amangoel185 added the book-dash-nov22 This label is for Book Dash 2022 related issues and PRs label Nov 14, 2022
@amangoel185
Copy link
Collaborator

amangoel185 commented Nov 14, 2022

Working on this issue for the November 2022 Book Dash. Collating the resources and updates here:

Title

Documentation

Guide

Guide for Project Design

Resources

Draft

documentation.md

Updates

  • Write chapter outline
  • Add material to the chapter
  • Combine materials into a readable chapter
  • Proofread
  • Create PR and link in the comments
  • Request reviews
  • Address reviews
  • Merge to main branch

@malvikasharan
Copy link
Collaborator

malvikasharan commented Nov 17, 2022

Outline

  • Landing page: Explain the 'why and how', also explain what your chapter covers (overview: project documentation chapter highlights, Data documentation and metadata chapter, Technical document)
  • SC1: Technical Documentation
  • SC1: Language and Platform
  • SC1: Workflows and resources: what process you can take (pandoc) - invite contribution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
book-dash-nov22 This label is for Book Dash 2022 related issues and PRs communication-book Content for communication book idea-for-discussion This can be used for inviting discussion from collaborators or community in general
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants