This repository has been archived by the owner on Oct 24, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 41
Documentation plans #61
Labels
documentation
Improvements or additions to documentation
Comments
This was referenced May 25, 2022
Merged
This was referenced Dec 31, 2022
Merged
Just took a look at the docs. They are looking great and much more complete than I was expected. Some comments on the current docs site:
Small nits:
|
This was referenced Jan 5, 2023
Thanks @jhamman for the feedback! I've fixed most of the quick things you mentioned, except for for the intersphinx / code API links which I'm a bit stuck on (see #183). For the tutorial page I was imagining creating some kind of example tutorial dataset and doing a mock analysis of that (see #142, which I've neglected). |
27 tasks
6 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Datatree needs some documentation, even if it has to change in future.
I think most of the documentation would remain relevant even after some changes, as long as we keep the same basic data model (e.g. DataTree vs DataGroups, with no hierarchy).
I really like this breakdown for documentation, which theorizes that there are 4 types of documentation, along two axes, as shown in this diagram:
Another thing to consider is how the documentation we write now might eventually be incorporated into xarray's documentation upstream. We don't need to duplicate anything, and we want things we write to neatly slot into sections in xarray's existing documentation.
Some ideas:
Tutorials
How-to Guides
(Some of these could possibly go in xarray's Gallery section)
Explanation
(A lot of this could be grouped under one page on "Working with hierarchical data".)
Reference
This should be pretty much covered by ensuring that the auto-generated API docs work properly. The hard bit will be copying / duplicating the large API of
xarray.Dataset
thatDataTree
inherits.The text was updated successfully, but these errors were encountered: