As the first step for #1414988: [Meta/Plan] Create a new Getting Involved Guide section we need to audit Getting Involved Guide (https://www.drupal.org/getting-involved-guide).
Currently that guide is using 'book page' content type and is a mixture of different types of content aimed at different audiences. There are 'how to contribute' type materials, there is detailed developer documentation, such as How to use Git, etc. The content needs to be audited so we knew:
- which pages will be migrated into the new Documentation system
- which pages will be the basis for the new 'Contribute' section
- which pages will be moved elsewhere
- which pages will be deprecated
Remaining tasks
- Go through every page in the Getting Involved Guide.
- If the page is empty / outdated / deprecated / in any way broken or irrelevant, move it to "Migration archive" book (https://www.drupal.org/migration-archive) via Book Outline UI. These pages will not be migrated into the new system and will eventually be deleted.
- If the page is up-to-date and relevant, add it to the spreadsheet and specify where it should be migrated.
Comments
Comment #2
jp.stacey commentedComment #3
jp.stacey commentedComment #4
tvn commentedUpdating issue summary.
Comment #5
jhodgdonWe've started a Google Sheets spreadsheet to audit the pages of the Guide. It's at
https://docs.google.com/spreadsheets/d/1vbIdtL-HAPK3bqiCamRIak048fcEqaWP...
If you would like to help with the content audit, find me in Slack or send me a message on my drupal.org contact form, and give me the email address you use with Google, and I will give you edit access to the document.
Comment #6
dddave commentedComment #7
jhodgdonI think that going through every page, throughout all the tree of pages in Getting Involved Guide is probably too much to ask. However, in the spreadsheet, we now have an inventory of the top-level pages and some key second-level pages that are under Getting Involved, as well as the pages in other parts of what is currently the /community section.
So... I think we can close this as Fixed for now, since I think the purpose of the audit for the moment at least has been served.
Comment #9
jhodgdonAfter the fact, moving this issue to another project so we can track it with the rest of the Getting Involved tasks.