René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Doc]: Move non user guide related content out of `/users`","articleBody":"### Problem\n\nGiven that `/doc` is now the root folder/index, a lot of the indexing that used to live on the `users` index page is now on the `doc/index` and it's a little easier to find things when the code structure matches the indexing. Also currently it's a little hard to define what we mean by user guide and scoping the contents of the folder can help in defining the purpose. \n\n### Suggested improvement\n\n- [x] `/users/project` -\u003e `/doc/project` \n- [x] `/users/installing`-\u003e`doc/installing` \n- [x] `/users/{generate_credits, github_stats, *_whats_new, release_notes*}` -\u003e `/doc/release`\n- [ ] `/getting_started/* -\u003e quickstart guide\n- [ ] `/users/users_explain/*` -\u003e `/users`\n\n#### Consensus\n\nAs discussed on the call, the rough consensus is this organization makes sense but should be done in stages, roughly one folder at a time. Largest concern was getting all the [redirects](https://matplotlib.org/devdocs/devel/document.html#move-documentation) correct and making sure that any links and instructions related to those docs are updated as needed. The stages are:\n\n- [x] move the `/project` folder up -\u003ehttps://github.com/matplotlib/matplotlib/pull/27560\n- [x] move the `/installing` folder up -\u003e (might be a good chance to change the name to install?) https://github.com/matplotlib/matplotlib/pull/27747\n- [x] move the release related folders and docs {generate_credits, github_stats, *_whats_new, release_notes*} into a folder and up one level\n- [ ] merge the contents in `users/getting_started` into the `gallery/users_explain/quickstart guide` and remove the `getting_started` folder\n- [ ] remove `doc/users` and rename `gallery/users_explain` to users \n\n#### Motivation\n\n* currently `/users/index/` is scoped to `users_explain` + `getting_started`, this would be matching structure to stated structure, in turn making it easier to find where a doc is to change it\n  * also means we can remove the symlink, which currently trips folks up when trying to edit documents under /user \n* the contents under `/project` are I think version independent (though we may want to keep the versioning on the site b/c the historicity is also important) but also for the most part should not be changed w/o consensus/streering-council sign off and it's a little easier to communicate that if it's not lumped with other user docs\n* I'm half/half on `/doc/install` b/c I understand why it would be inside a users guide but we also write those documents as a more general installation guide/reference for both \n* there are a lot of files related to the release process and unlike `/api/changes` it's not clear why they are here. \n","author":{"url":"https://github.com/story645","@type":"Person","name":"story645"},"datePublished":"2023-11-29T20:22:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/27396/matplotlib/issues/27396"}