Skip to content

Adding recognition content to feedback page

Why is this change being made?

@dsatcher put together some excellent content on Recognition to add to the handbook inspired from this issue she opened to brainstorm forms of sync and async recognition with her team.

It was originally added to the Building Trust handbook page, but we thought it could be a better fit on the Feedback page and cross-link to Building Trust.

Author Checklist

  • Provided a concise title for the MR
  • Added a description to this MR explaining the reasons for the proposed change, per [say-why-not-just-what][transparency]
  • Assign this change to the correct DRI
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in [#mr-buddies][mr-buddies-slack].
    • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.

Merge request reports