Here's my proposal to update the organization of the developer wiki.
The goals are to:
- Improve on-boarding of new contributors.
- Serve as a reference for existing ones (including quickly finding links to share).
- Be a quick launchpad for frequent activities of existing programmers (eg. write release notes)
Overview of all content
Pages are grouped by topic (subjectively done by me :).
Some pages are not existing yet.
Some of the new pages are meant to aggregate content that is currently together with other topics. (eg. Communication and Style Guide for Commit Messages).
Some existing pages were discarded (Glossary, User Reference Manual, Supported_platforms).
Mockup for the links in the main page.
This is meant to be presented in cards with a short description and maybe some direct links to popular pages.
Plan for Renames and Broken Links
With all the content shuffling there will be some broken links.
For pages that get renamed -> Redirect.
For pages that get split or included in others (Commit_Access, Contact) -> Page done manually saying "The content of this page was moved to <link> and <link>."
For pages that don't get copied from the old wiki to the new wiki (glossary, etc) -> Page saying "The content of this page is no longer up to date. See it in the <link>archive</link>.".