-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Master documentation plan #317
Comments
I'd suggest splitting out "Interoperability Specifications" as their own document type - they're not "You may want to know this" the way the other discussions are, they're "You probably need to know this if you're a tool developer, otherwise you shouldn't need to care". The package metadata page and the index API page would then move into that section. I'd suggest leaving the setup() args discussion where it is, though (since that's only an "interoperability spec" for anyone wanting to emulate distutils or setuptools at the Python API level, but is going to be generally useful for users of setuptools and distutils) Aside from that, the suggested overall structure looks good to me. |
I'm pretty happy with what I'm seeing here (@ncoghlan's comment included). Thanks! |
New org structured is merged (yay). Now to write a better landing page. |
All done. :) |
This is the master plan for restructuring this guide. This issue's description will be edited as discussions occur. It's the plan of record for what the end state is and what steps we will take to get to the end state. This is proposed as a minimal set of changes to improve these docs and encourage contributions, once we have this foundation we can build on this to improve even further. Specifically, the work started by @ddbeck for new tutorials will be significantly easier after this structure is in place.
Documentation Types
This guide will consist of 3 distinct documentation types:
We may revisit and add additional documentation types as needed.
Documentation plan
This is the set of docs that we want to provide, organized in the final toctree.
These pages will be moved to other projects:
Steps to get there
Once we're there
After this work is done, we should be able to more easily divide and conquer handling new tutorials, addressing issues, and revising existing content. My next task will be to work on revising the two top-level tutorials and possibly breaking them up according to @ddbeck's guide (and taking a page out of Django's book).
The text was updated successfully, but these errors were encountered: