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

Update user guide #219

Closed
kinow opened this issue Apr 4, 2022 · 5 comments
Closed

Update user guide #219

kinow opened this issue Apr 4, 2022 · 5 comments
Assignees

Comments

@kinow
Copy link
Member

kinow commented Apr 4, 2022

The goal of this issue is to update the user guide, making it a comprehensive reference material, not a tutorial or tutorial material.

The format will be different than the Carpentries format. The first tentative version will be created with Sphinx + markdown + ReadTheDocs. While these tools can still be replaced by others, the goal is to create a low entry barrier for new contributors (e.g. instead of having to learn reStructuredText, use simpler Markdown.)

This is a placeholder issue, and existing issues will be linked here. A few important pointers:

  • This user guide will be integrated with the CWL site, like the existing one
  • It is important to keep links working (for SEO, bookmarks, etc.)
  • Should have GH pull requests preview

Contributions & any other help very welcome! Feel free to link this issue to other issues 🚢

@kinow kinow self-assigned this Apr 4, 2022
@kinow
Copy link
Member Author

kinow commented Apr 10, 2022

MyST syntax cheatsheet from JupyterHub: https://jupyterbook.org/reference/cheatsheet.html

@kinow
Copy link
Member Author

kinow commented Jul 4, 2022

I normally use Draw.io and Inkspace, but looks like Draw.io has a new home, and found another interesting (free) tool too:

Of course if we can use cwltool or the Viewer, then we will use that. But if we need a diagram to illustrate something else, maybe one of the above could be useful (or Inkscape + SVG to store it on GitHub).

@kinow
Copy link
Member Author

kinow commented Jul 19, 2022

Numpy, Canonical, and others are using Diátaxis for guiding how to organize their documentation: https://diataxis.fr/

There are four main axis in Diátaxis, which I believe we have adopted in the proposed new structure #222, even if not following Diátaxis initially:

  1. Explanations (our User Guide)
  2. How-to guides (links in the How-Tos section of the User Guide)
  3. Tutorials (links in the Tutorial section of the User Guide)
  4. Reference material (the Specification)

I will spend some more time reading about it, and about how others have used it to see if there's more that we can incorporate into our user guide.

@kinow
Copy link
Member Author

kinow commented Jul 20, 2022

For later, I will try to go over Discourse & Matrix to see if the new version of the user guide has sections for the answers for user's questions. I saw a post in the Cylc discourse that reminded me they also re-wrote their user guide (but due to a new release) and now they are able to link to it to answer users 🙂

image

(the links in the image above are to sections of the Cylc User Guide)

I will also take a look at their user guide structure, text, and especially at their Sphinx set-up (I hadn't used much Sphinx before, and learned most of what I know from working with the Cylc devs 🙇 ). Even though we are now using Sphinx + MyST, I believe most (if not all) Sphinx/rst extensions are compatible with MyST.

@kinow
Copy link
Member Author

kinow commented Aug 24, 2022

Closing now. We can work on smaller issues for future corrections and improvements.

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

1 participant