The majority of narrative documentation is in the form of notebooks. These are presented in the user-documentation as html-rendered notebooks, but actually downloading a notebook to run is not obvious.
Suggestions regarding the Issue
Somewhere prominent and early in the documentation, there should be clear instructions on how to download the notebook corresponding to a documentation page.
The fact that the notebooks are a submodule can be a further source of confusion if someone has cloned the repo locally. The magic commands to fetch the submodule might be useful. I think this works but I'm never sure!
Thanks @taldcroft. I think the easiest is just addressing the users to our stingraysoftware/notebooks repository, where we store the notebooks that are linked in the documentation. What do you think?
Description of the Issue
The majority of narrative documentation is in the form of notebooks. These are presented in the user-documentation as html-rendered notebooks, but actually downloading a notebook to run is not obvious.
Suggestions regarding the Issue
Somewhere prominent and early in the documentation, there should be clear instructions on how to download the notebook corresponding to a documentation page.
One simple way would be to instruct users to navigate to: https://github.com/StingraySoftware/stingray/tree/main/docs, then click the
notebooks @ <something>
link and then click through to find the desired notebook.The fact that the notebooks are a submodule can be a further source of confusion if someone has cloned the repo locally. The magic commands to fetch the submodule might be useful. I think this works but I'm never sure!