-
Notifications
You must be signed in to change notification settings - Fork 206
Convert doc-strings for sphinx and add standalone sphinx docs. #117
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
Conversation
Some additional consistency to the docsting format and layout as well to conform to standards and internal style-guide.
docs/usage_tips.rst
Outdated
==== | ||
|
||
**Smart Cut Fields**: These fields are available only in the browser UI. You can read more about | ||
smart cut fields and the API in the Smart Cut Fields doc (link TK):: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should actually link to the smart cut fields doc.
Possible to update the TOC? Currently getting this:
Seems like something along these lines would be a more intuitive ordering:
|
- address CR note for linking to smart cut fields page.
Ready for CR again. All docs from the wiki have been added. This version has been pushed to http://developer.shotgunsoftware.com/python-api/ We can probably still improve the organization and update various things (like the svn integration docs... add a github version). But again, the goal here to to get to a point where we can shut down the wiki, then we can iterate on these to get them perfect. 🎉 |
Suggested feedback before roll-out
Suggested post-rollout tweaksOther than that I think it looks amazing: I did a really quick readthrough and jotted down the following feedback - maybe some of this should be considered for a quick subsequent post-doc-transition pass?
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here are my suggestions, thoughts and comments:
With the two suggested changes (remove internal classes and TOC rejig to reduce number of high level items) I think this is really to go. It's a huge improvement over the wiki based doc. Amazing work Sir.
I think we should
- "soft launch" this by removing the old github wiki docs and replace these with a link to the sphinx docs. Also update
developer.shotgunsoftware.com
and other places where we reference the docs. We now again have one place to go for docs. And these new docs are fantastic. - Do a post rollout pass where we do further tweaks and see if there are any quick wins and improvements we can make. I added some suggestions in the CR, i am sure there are more tweaks. Once this is done we reach out to the shotgun-dev list and let them know about the change.
@manneohrstrom great notes! What were you referring to by this one?
|
@kporangehat in the filter syntax section, you currently have this: I think what would be great would be to:
|
Users shouldn't rely on these as they are internal and can change at any time.
- reorganized TOC - some files were moved or combined for better organization - removed docs for ServerCapabilities and ClientCapabilities as they are internal classes that may change at any point - added Cookbook section as a container for detailed usage examples. - split up Shotgun class methods into logical groups of methods. - added link from Event Types docs to the shotgunEvents event daemon repo - updated working in Event Types. - added warning to Smart Cut Fields about it's deprecation with a link to Cut Support in Shotgun v7 - Modified date in Shotgun Server API Changelog to be more internationally understood - Renamed "Working with Local Files" to "Working with the Local File type" as part of the Working With Files docs to make it slightly ? clearer. - Moved Iron Python info to the advanced section - Re-ordered installation sections to have manual Github install instructions at the top and pip instructions underneath - Lots of other misc tweaks and edits.
Pushed and built a new version at http://developer.shotgunsoftware.com/python-api/ Addressed most of the things you brought up above (marked with ✅ ). Outstanding items:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good. The one thing I think should be changed is that an actual link to the changelog section of the readme on github should be added to the index.
Potentially we could even get rid of the changelog section in the developer docs if they really are out of date and redundant. Other than that, AWESOME stuff.
What do you think about moving that changelog to its own CHANGELOG file? KP From: Rob Blau notifications@github.com notifications@github.com @robblau commented on this pull request.
|
I'd be game for that. Feels pretty equivalent, but he docs should have an easy to find pointer to them. |
- Changelog is now published in the docs as well as included as a HISTORY.rst file in the repo.
- Removed the server changelog info as it was out of date and not very useful.
This is a large commit almost entirely focused on the doc-strings and related formatting in order to release sphinx docs to replace the wiki.
This also adds some additional consistency to the doc-sting format and layout as well to conform to standards and internal style-guide.
A live preview is available at http://developer.shotgunsoftware.com/python-api/