You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the notebooks within a package are ordered alphabetically. For some packages this breaks the logical flow (pointpats for example).
One solution to this might be to have a README.md in the package notebooks directory that lists the specific order by which the notebooks should be visited by an interested user. Alternatively, maybe a yaml file in that directory could serve the same purpose. Either way, the notebooks project would consume these files to set the ordering of the notebooks.
The text was updated successfully, but these errors were encountered:
Thanks, good point! Another idea so it's all automatable would be to agree to have notebooks "numbered" on the notebooks folder of each package (e.g. 01_read_data.ipynb, 02_advanced_analysis.ipynb).
Thanks, good point! Another idea so it's all automatable would be to agree to have notebooks "numbered" on the notebooks folder of each package (e.g. 01_read_data.ipynb, 02_advanced_analysis.ipynb).
For the notebook project, is there a limit on the number of notebooks per project?
Currently the notebooks within a package are ordered alphabetically. For some packages this breaks the logical flow (pointpats for example).
One solution to this might be to have a README.md in the package notebooks directory that lists the specific order by which the notebooks should be visited by an interested user. Alternatively, maybe a yaml file in that directory could serve the same purpose. Either way, the notebooks project would consume these files to set the ordering of the notebooks.
The text was updated successfully, but these errors were encountered: