Edit of the repositories overview page #1488
Conversation
Less wordy and more direct
but don't go into too much detail
I tried to balance the objective of the original issue (WordPress#1259) and this PR: - @adamziel's intention (as I understand it) is to clarify the ecosystem: > Let's write a page that explains the structure of the larger Playground initiative, especially around GitHub repositories and what are they for. - @flexseth's PR focuses on "action": > guide users to submitting issues as accurately as possible To achieve this, I did the following: 1. Reorder the repos by relevance. 2. Add an intro. 3. Revise the content to describe "what you'll find here" _and_ how to participate (contribute/get help). Finally, I removed redundant references, fixed formatting, and polished the wording.
|
@flexseth, there are two files... thought your plan was to merge both |
Good catch, removed the duplicate file. I used some of the text you provided, some of what I came up with, and some of what came from the repos (but simplified due to links for more info) Let me know what you think! I'll request review from @adamziel on Friday, so please review ASAP if you can. Trying to get this in before WCEU if possible |
|
I'll try to take another look at this over the weekend and submit for review, thanks for the ping, @bgrgicak |
|
Looping in @juanmaguitar who's overhauling the documentation for reviews here |
|
As of #1602, the ecosystem information is now contextually included in the relevant documentation sections which effectively solves the same problem. I'll go ahead and close this PR. |
|
Thanks everyone for collaborating on this. I started school earlier this year and did poorly my first semester, made Dean's List last semester and on track again for that. Looking to get involved for contributor day if time permits! Cheers/Seth |
Motivation for the change, related issues
update of copy to reflect what was found on the repositories with a good voice. A collaboration between @ironnysh, @adamziel and myself.
Implementation details
discuss changes needed and approve PR
Testing Instructions (or ideally a Blueprint)
minor formatting changes needed, feedback needed