Skip to content

Latest commit

 

History

History
13 lines (10 loc) · 977 Bytes

self_review.md

File metadata and controls

13 lines (10 loc) · 977 Bytes

Self review

You should always review your own PR first.

For content changes, make sure that you:

  • Confirm that the changes meet the user experience and goals outlined in the content design plan (if there is one).
  • Compare your pull request's source changes to staging to confirm that the output matches the source and that everything is rendering as expected. This helps spot issues like typos, content that doesn't follow the style guide, or content that isn't rendering due to versioning problems. Remember that lists and tables can be tricky.
  • Review the content for technical accuracy.
  • Review the entire pull request using the translations guide for writers (N/A).
  • Copy-edit the changes for grammar, spelling, and adherence to the style guide (N/A).
  • Check new or updated Liquid statements to confirm that versioning is correct.
  • If there are any failing checks in your PR, troubleshoot them until they're all passing.