René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[Doc]: Sort out doc mechanics/formatting/content guides","articleBody":"### Documentation Link\n\n_No response_\n\n### Problem\n\nWe have these two documentation guides where the write docs page is a mix of \"how to build\", and formatting and content guidelines and the \"style guide\" mixes formatting and content:\r\n\r\n* https://matplotlib.org/devdocs/devel/document.html\r\n* https://matplotlib.org/devdocs/devel/style_guide.html\r\n\n\n### Suggested improvement\n\nBuild related docs should go on a different page from formatting and content related guides. The content is of a different type and scope and separating it out will down the line help us surface it more cleanly in TOCs, sidebars, and the like and give us more flex if we decide it belongs in workflow rather than guidelines. \r\n\r\nI also think we should separate out formatting from content guidelines. The major reason is that the general formatting guidelines apply to all the docs regardless of what type, while content specific guides are specific to docstrings/examples/tutorials/user guide and seperating this out may make it easier to communicate that. It will also allow us to reduce some of the replication we're currently seeing across the style and writing guides. My bias is to put each set of content guidelines on its own page (so like \"docstring content guidelines\") in a docsdoc/content folder but that's mostly b/c of my preference for small scoped docs pages.  \r\n\r\nSomewhat inspired by @esibinga's GSOD work and trying to figure out where to put it. ","author":{"url":"https://github.com/story645","@type":"Person","name":"story645"},"datePublished":"2023-07-26T18:49:08.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/26392/matplotlib/issues/26392"}