Title: Validating and Applying Content Feedback
Author: Kaito Hanamori
Published: January 23, 2023
Last modified: August 29, 2024

---

# Validating and Applying Content Feedback

## In this article

 * [Validating Content Feedback issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#validating-content-feedback-issues)
 * [Changing the status on validated Content Feedback issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#changing-the-status-on-validated-content-feedback-issues)
 * [Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#applying-content-feedback)

[↑ Back to top](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#wp--skip-link--target)

When users have feedback about the content on Learn, they submit Content Feedback
to the team. This feedback is recorded in GitHubGitHub GitHub is a website that 
offers online implementation of git repositories that can easily be shared, copied
and modified by other developers. Public repositories are free to host, private 
repositories require a paid subscription. GitHub introduced the concept of the ‘
pull request’ where code changes done in branches by contributors can be reviewed
and discussed before being merged by the repository owner. [https://github.com/](https://github.com/)
for anyone to come along and process. You can find these issues in the [LearnWP Content – Feedback project board](https://github.com/orgs/WordPress/projects/78).

Once an issue has been submitted, it goes through two stages – validating and triaging.
Follow the steps below to validate and triage Content Feedback GitHub issues. The
following Online Workshop recording will also guide you through the feedback validation
process.

There have been updates to this process since this video was recorded. Please refer
to the text version for the latest steps.

## 󠀁[Validating Content Feedback issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#validating-content-feedback-issues)󠁿

_No special access is needed to validate reports. Anyone in the Training Team can
do this._

When you validate a report, you check to see if the report is relevant. Sometimes
a fix may have already been applied to the content, or the report was just spam.
In these cases, the report is no longer relevant, and can be closed.

Follow these steps to validate Content Feedback:

 1. Open [the list of content feedback awaiting validation](https://github.com/orgs/WordPress/projects/78/views/3).
 2.  * _For reference, these are issues with the “Awaiting Validation” status on the
       [LearnWP Content – Feedback](https://github.com/orgs/WordPress/projects/78) 
       project board._
 3. Open any issue, and in a new comment, copy-paste the following check-list:

    ```wp-block-code
    # Feedback Validation Checklist:
    - If this is reporting an issue, can you confirm/reproduce the issue? (Yes or No): 
    - What should happen next to apply the feedback?: 
    ```

 3. If the feedback is reporting an issue in the content, confirm if you can still 
    see/reproduce the issue.
 4.  * If you can, type **YES** next to the first item in the list you just copied 
       across, and move to step 4.
     * If you can’t, type **NO**.
        - If it looks like the issue has been fixed already, leave a comment with your
          findings and move to step 5.
     * If the feedback is unclear, leave a comment explaining what you tried and ask
       the author for more information. You can do this by @-mentioning the author 
       in your comment.
        - You can skip steps 4 and 5 below.
 5. Leave a note about what needs to happen next, and press `Comment`.
 6.  * For example, if a screenshot needs to be updated and you are able to create 
       the correct screenshot, you can upload that image into your comment, too.
 7. If the feedback has been validated, and the next steps are clear, mention the `@
    WordPress/learn-editors` team on the GitHub issue, letting them know. They will
    be able to move the issue to the `Awaiting Fix` status, apply the necessary changes
    to the content, or close the issue for you.

Thanks for validating Content Feedback GitHub issues!

## 󠀁[Changing the status on validated Content Feedback issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#changing-the-status-on-validated-content-feedback-issues)󠁿

The [Learn Content Triage](https://github.com/orgs/WordPress/teams/learn-content-triage/members)
membership on GitHub is required to change the status of issues. Experienced team
members are given this access, and contributors who have shown consistent contribution
may also request access. Please contact a Training Team Representative or pingPing
The act of sending a very small amount of data to an end point. Ping is used in 
computer science to illicit a response from a target server to test it’s connection.
Ping is also a term used by Slack users to @ someone or send them a direct message(
DM). Users might say something along the lines of “Ping me when the meeting starts.”`@
tt-admins` in the[ #training Slack channel](https://wordpress.slack.com/archives/C02RW657Q)
if you lack the appropriate access to perform this work.

 1. In the right sidebarSidebar A sidebar in WordPress is referred to a widget-ready
    area used by WordPress themes to display information that is not a part of the 
    main content. It is not always a vertical column on the side. It can be a horizontal
    rectangle below or above the content area, footer, header, or any where in the 
    theme. of the issue, change the status from `Awaiting Validation` to `Awaiting 
    Fix`.
 2. Remove the `Awaiting Triage` label.

## 󠀁[Applying Content Feedback](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/validating-and-applying-content-feedback/?output_format=md#applying-content-feedback)󠁿

_Fixing issues (or applying changes) in content can only be completed by those with
access to edit content on https://learn.wordpress.org/. Please ping @tt-admins in
Slack to apply the changes for you if you do not have access._

Once content feedback has been validated, the change will need to be applied to 
the content. Please follow these steps to apply the changes and close out the GitHub
issue.

 1. Open the list of content feedback that [have been validated and are awaiting for a fix](https://github.com/orgs/WordPress/projects/78/views/4).
 2.  * _For reference, these are issues with the “Awaiting Fix” status on the [LearnWP Content – Feedback](https://github.com/orgs/WordPress/projects/78)
       project board._
 3. Open any issue and apply the suggested changes.
 4.  * If an issue was assigned to someone but no movement has been made in the last
       two weeks, feel free to work on the issue yourself.
 5. Leave a brief comment about the changes you made and press `Close with comment`.

First published

January 23, 2023

Last updated

August 29, 2024

[  Previous: Triaging Content Localization Issues](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/triaging-content-localization-issues/)

[  Next: Vetting Topic Ideas](https://make.wordpress.org/training/handbook/training-team-how-to-guides/how-we-use-github/vetting-topic-ideas/)