Skip to content

Conversation

@bjnath
Copy link
Contributor

@bjnath bjnath commented Jul 25, 2020

Writing guidelines for how-to docs.

Writing guidelines for how-to docs.
how_to_how_to.md Outdated

* Three miles, take a right at Hayseed Road, follow the signs.

If the information is already in the docs, link to it -- don't repeat it. If the API doc is sufficiently clear, link directly to it after you've given the prefatory information ("Three miles, take a right").
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I had no idea what prefatory meant (loved learning about it!), maybe change it to a simpler word for the benefit of non-native English speakers?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I really like this How-to guide for how-tos @bjnath - thank you!

As @melissawm said, maybe change it to a simpler word. What do you think about using "introductory"? (Ref: https://developers.google.com/style/translation#be-inclusive)

Cheers!

Copy link
Member

@melissawm melissawm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bjnath thanks, I liked the guide and it does make it much simpler to organize thoughts around how-tos. I can see what you mean in #15 . I do think I'd like to see some discussion here to see if more people agree or if we're looking for something different for how-tos.

@melissawm
Copy link
Member

Maybe @rossbar or @mattip would like to take a look?

Replaced the word "prefatory" with a simpler paraphrase.
@melissawm
Copy link
Member

As discussed in the Documentation Team meeting, I'd like to merge this. However, this guide (just like the I/O How-to #15 ) needs to be in notebook format, which would make it easier for people to browse using Binder, for example.

@bjnath
Copy link
Contributor Author

bjnath commented Sep 14, 2020

Something we haven't discussed: While notebooks are perfect for tutorials, they're wrong for how-tos.

Tutorials are meant to be executable, so notebooks are great for them.

How-tos aren't meant to be executable. You can see that in #15 -- there's nothing to execute there. It's just names of commands and pointers to other docs.

Thus there's no value in putting a how-to in a notebook. It would consist of a single text cell.

Two conclusions:

  1. If how-tos aren't notebooks, they probably belong not in this repo but with the main Sphinx docs.

  2. If people nonetheless see a need for how-tos to be notebooks, it suggests we haven't converged on what a how-to is, and it's probably too soon to merge.

@bjnath bjnath mentioned this pull request Sep 14, 2020
@melissawm
Copy link
Member

This makes sense. My thinking was that writing them in notebooks might make the barrier of entry a little smaller for people. However, if you're writing a how-to, maybe that barrier is not so relevant. In that case, this how-to should be submitted to the main repo instead of here.

@bjnath
Copy link
Contributor Author

bjnath commented Oct 2, 2020

Per discussion, the content is now on the Sphinx pages: https://numpy.org/devdocs/user/how-to-how-to.html

@bjnath bjnath closed this Oct 2, 2020
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

Successfully merging this pull request may close these issues.

3 participants