-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Major changes to the documentation #9475
Comments
So... I started a rewrite of pip's documentation. I'm obviously not done yet, but it's up as a draft very-much-in-progress PR now. I'd like to get feedback on stuff I've done so far, to see if folks do like the general direction this is going. :) Broadly, the ideas here are:
There are 2 "new" pages I want to add (i.e. new content that didn't previously exist), based on documentation feedback from our user research:
|
The preview for the draft PR of the rewrite is up at https://pip--9474.org.readthedocs.build/en/9474/. As usual, feedback is welcome. :) /cc @brainwane @nlhkabu @pypa/pip-committers since I'd really like to hear from them. |
Oh yea, and the plan for migration is... to preserve/re-add the old hierarchy as "orphan" pages and add links to the moved content. And then give search engines ~3-6 months to update to the new locations. We can probably also add RTD redirects at some point, but I'm a little uncomfortable since those aren't surfaced in a config file or whatever. And I don't imagine that being being priority for RTD, since, uhm, it's a team that's stretched really thin already. :) |
I think there's basically only one class of redirects we'd need to configure here -- reference -> cli stuff:
And redirecting installation to "Quickstart".
Yup. See readthedocs/readthedocs.org#4221. |
Annnd the first PR (#9693) making the necessary non-content changes for this rewrite is filed! |
Just out of curiosity, why moving from rst to markdown? |
Markdown is a significantly more popular markup format than reStructuredText. It’s likely that potential contributors who are not professional-Python-developers are fairly familiar with Markdown, but haven't used reStructuredText. MyST gives you the best of both worlds – simplicity and familiarity of Markdown with the extensibility power of reST. It's already in use by the Jupyter Book project and is stable enough to write documentation like (most of) https://pradyunsg.me/furo with it. Also, I think it's much easier to write, and I'm doing a lot of the writing here. :) |
I made a GitHub project to track this now, and I'll be updating things there instead of making comments here. |
Picking this back up now, since I'll have additional capacity! |
I've figured out a better name for the "Explanation" section from #9474: Topic Guide Each page within that section is providing mostly-complete information on that specific topic, to aid understanding and maybe provide guidance on what to do. These pages roughly map to https://diataxis.fr/explanation/ within the Diátaxis Framework. |
I'm guessing this is something you already have in mind for this issue, but it would be great if the pip user guide included a section dedicated to discussing the fraught nature of |
This is basically the supporting issue to #9474, with the idea being to have any broad overarching discussions over here, with code review happening in that PR. :)
The text was updated successfully, but these errors were encountered: