-
Notifications
You must be signed in to change notification settings - Fork 15
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
Make docs useful #67
Comments
There's a lot of useful content now in hubploy-template readme that could be here instead. I did add some useful info to the main doc page here though: https://hubploy.readthedocs.io/en/latest/ |
I did always find it funny how the overwhelming majority of the docs were in To start, do we want a divide in the docs between As far as docs in those three categories go, what seems good to have setup first? My thoughts are (in no particular order, except maybe what I can think of that I could write):
If you want to pick a couple I can plug away on those a bit in the next couple weeks. Gotta learn a bit of rST first. |
@salvis2 totally agree, re: hubploy-template :D Moving a lot of that here and referencing it from hubploy-template is probably way to go. Your ordering sounds great! Would love for you to take a crack at it... Thank you for offering to put your time on this! |
@yuvipanda quite welcome! The first howto is well underway, mostly because it is the How do you publish the documentation? Neither the GitHub Actions bit nor the CircleCI bit seem doc-related. I'm reading on the Sphinx website that you can build locally and output files, so I could test that way I think. Relatedly, if you have a recommendation on testing the docs that is different than above, I welcome the input. |
First stab at documentation is at #78 . |
@salvis2 @yuvipanda I wonder what parts of this issue you consider to be resolved by #78 and what action points remain to take for this issue. Thanks for your work on this ❤️! |
Of the 6 bullet points I put above, I did 5 of them. The last one I felt was out of the scope of my experience for now, but I added in the files so someone else can get right to writing the how-to if they want. I'll edit the comment above to be a checklist. All three of the styles of documentation that @yuvipanda mentioned in the first comment have something on ReadTheDocs now, but there is more to write. I'll make a list from what I can think of right now and what I see from Yuvi's original comment that opened the issue. We should have docs on such things as:
|
Currently, the hubploy documentation is scattered in a few places, and a few heads. This is issue is an attempt to getting the docs to a place where we can show off hubploy to people.
We intentionally structured the docs of TLJH in very specific ways, and it has worked out really well for us. We should try to copy that. We actually wrote documentation on how to structure our documentation - http://tljh.jupyter.org/en/latest/contributing/docs.html.
Primarily, I want us to have 3 kinds of docs:
I want us to use this issue to think of useful docs in these three ways, and write them one by one.
The text was updated successfully, but these errors were encountered: