Background
The Developer Documentation OEP PR landed Jan 14th. The community came together with reviews and comments, which culminated in this OEP resulting in a much better state than where it started. Now, 3 months later, let us reflect and review the impact and adoption of this OEP to date. We look forward to continuing to work with the community to adopt documentation best practices, reminding ourselves and our teammates of this OEP, reflecting back on the impact of these changes and updating this OEP as we go and learn from our experiences.
We appreciate your participation in our common goal of creating a more approachable and maintainable platform (codebase), resulting in sustainable improvements to developer velocity and usability of our features, eventually resulting in an open source platform that we are proud of.
Retrospective
Please enter your thoughts on what benefits we are already seeing from Dev Docs and should continue to do (Keep doing), what you'd like to see us (Start doing) going forward, and what you propose we discontinue (Stop doing).
...
- Grant Goodman (Deactivated) See if there's a best practices document from the Docs team that we can link to in the OEP. Audience summary: Doc Team Work Information
- Nimisha Asthagiri (Deactivated) Refactor oauth_dispatch ADRs - to break out docs that should be elsewhere.
- Adam Butterworth (Deactivated) Update OEP to include embraced exceptional cases for MD/MDX.
- Nimisha Asthagiri (Deactivated) Update OEP to announce ADRs in #dev slack channel.
- How-to for Developer Docs; Add Dev-docs how-to in onboarding documentation. (Jeremy Bowman (Deactivated) - is this something your team would be able to tackle?)
- Albemarle (Deactivated) Follow-up on closing out OEP-27.