[POP]
All right, so hello, everyone, and welcome
to today's online workshop.
Today's topic is how to validate content feedback
for the WordPress training team.
So the WordPress training team looks
after the Learn WordPress website.
We open that website up.
So this is the Learn WordPress website.
And the Learn WordPress website is
an educational resource for both learners and teachers
of WordPress.
So we have, for example, tutorials, tutorial videos,
online courses, and online workshops,
like this session we're having right now for learners.
And then we also have lesson plans,
which are teaching aids for teachers
to go and teach WordPress.
Now, I'm going to open one of these resources.
So I'm just gonna open tutorials.
And most recent tutorial is about the WordPress 6.3 release.
So that release came out yesterday, the day before.
All right, but anyway, so on each of these resource pages,
if you scroll down a bit on the right,
we have a section for learners or users
to send us suggestions.
So for example, if they find a typing mistake
in the context, or if there's a grammar mistake,
or even an outdated screenshot,
the sometimes WordPress update
and the screenshot needs replacing.
When people find a piece of content needs an update,
they can let us know from this button here.
So I'll press let us know.
And this takes users to the report content feedback page.
And this is what we're going to be talking about today.
So the topic there is how to validate content feedback.
Users send the training team content feedback.
And then there are two steps.
We first need to validate the feedback,
and then we apply the changes if necessary.
And the reason why we have to validate feedback
is because sometimes the feedback people send us
isn't about the content.
So sometimes they are experiencing a browser
issue on their device or a network issue.
So sometimes it's not necessarily
something we can fix.
And so that's why there's first a step
to validate the feedback, see if it is an issue that is still
occurring.
And then once it's validated, then the editors and the team
can edit the content.
So when people report content feedback,
they come to this page.
And if you look at the yellow box here,
it says, if you're familiar with GitHub,
then feel free to submit your feedback directly
to our GitHub repository.
So users can send their feedback directly
into the training team GitHub repository
if they're familiar with GitHub.
And then this automatically puts their feedback
into our triage process.
But underneath the yellow box, you'll also see,
if you're not sure what GitHub is,
or you're not comfortable submitting an issue there,
that's OK.
Please fill out the form below, and our team
will be notified of your report.
If people aren't familiar with GitHub, that's totally fine.
They can fill out this form here,
which will send the training team an email.
And then the training team have administrators
who copy the content of that email
and create a GitHub issue for that user.
So all feedback lands in GitHub.
But depending on whether the user is familiar with GitHub,
it might go directly there from the user.
but might go via an email.
So once the feedback lands in GitHub,
we have a content feedback project board,
which looks like this.
And the project board has three columns
and issues move from the left to the right.
So the first column, awaiting validation.
All the issues first land here.
And you'll see we have 28 issues awaiting validation.
And this is the column we'll be talking about
in today's online workshop.
Anybody can come to the training team's
GitHub project board and validate feedback for the team.
Once feedback has been validated,
it's either closed out if it's not feedback
or sometimes we get spam, people submit spam.
So things like that, people can close out.
But if it has been validated, it then
moves into the Awaiting Fix column.
So once it gets to this column, these changes
need to be submitted to the learn.wordpress.org website.
And to protect the content on the loan website,
edit access is limited to faculty editors in the training team.
So anybody can, oops, anybody can validate content feedback.
And once it moves to the Awaiting Fix column,
it's them waiting for faculty editors
to apply the updates to the content.
And then once the updates have been applied,
the issue moves to the Done column.
So that is an overview of how content feedback
moves through the training team.
We'll step into the actual details of validating feedback
just a moment.
Are there any questions so far about the overview here?
Anyone can reject?
In a sense, yes.
So anybody can look at an issue
in the waiting validation column
and reject the issue.
For example, it's not happening anymore.
So it's something we don't even have to look at.
Or maybe the user needs personal help.
So you send help to the user and you can close the issue.
How is that rejection reason captured
or no reason required?
That is a good point.
And it will come up in the steps I'm about to show.
So every time we either close an issue
or move an issue forward,
that person must leave a note
about why that issue was closed or moved.
And we'll see in a moment,
the normal person is able to validate content feedback,
but they don't actually have a close issue button.
So they can leave their feedback and say,
this issue doesn't happen anymore,
so we can close it out.
But then they still need to wait for a faculty editor
to actually press the close button for them.
So it's sort of a mechanism to make sure
we don't have just any contributor come through
and close all the issues out.
There's always a second person to double check
to make sure issues are indeed worthy of being closed
or worthy of being moved forward.
But we'll get to those steps in just a moment.
All right, so how do we validate content feedback?
I'm going to drop a link here to the Training Team handle.
And so if you're interested in joining the Training Team
and contributing to the Training Team,
I highly recommend you bookmark this link.
You see I've bookmarked it in my bookmark as well.
So I open the Handbook quite frequently.
And down the left here, you'll see
we have a large list of Table of Contents.
What we're going to be focusing on today
is under the How To Guides under How We Use GitHub,
there's a page titled Validating and Applying Content
Feedback.
So let me share this direct link in Zoom chat as well.
There we go.
And so this handbook page will walk contributors
through the steps of validating content feedback.
That's what we're going to look at today,
and applying content feedback.
So applying content feedback can only
be performed by faculty editors, because they
have the edit access on WordPress.
But validating can be done by anyone.
All right, so let's jump into this.
Validating content feedback issues.
So no special access is needed to validate reports.
Anyone in the training team can do this.
So if you're interested, please join us in validating feedback.
Now, 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 banned.
In these cases, the report is no longer relevant
and can be closed.
And then we list here five steps in order
to validate content feedback.
So there's five steps here, and we'll go through each one
together.
So number one, open the list of content feedback awaiting
validation.
So we click on this list.
And this will give us a list of content feedback,
and you can see under status, they're all still
awaiting validation.
So we have 28 issues here.
So step one, done.
Get to open any issue and in a new comment,
copy and paste the following checklist.
We have a grade area here.
I'm going to copy that text and I'm going to
switch over to this browser tab here to work on this.
Let's see, page with incorrect content.
Let's click on that.
All right, so let's have a look at this issue.
I'm going to open the issue.
And what we're going to do is we're
going to paste the checklist I copied from the handbook
into a new comment down here.
So you'll see it says feedback validation checklist.
First point, if this is reporting an issue,
can you, that's me, confirm, reproduce the issue?
or we type here whether we can or can't reproduce the issue.
And then the second point is what should happen next
to apply the feedback.
So we leave a note here about what needs to happen next.
For example, this issue is no longer relevant,
so the issue needs to be closed out.
Or if we have validated the feedback,
we can, for example, upload the screen,
the renewed screenshots into GitHub and say,
please replace the screenshot in this content
with this new one I created.
Or we can say this paragraph needs to be changed this way,
what have you.
So the validator can leave next steps
to make the editor's job a bit easier.
All right.
So coming back to the handbook,
step one was opening the list of content feedback.
We did that.
Step two was open any issue and copy paste
the following checklist.
We did that.
So now, step three.
If the feedback is reporting an issue in the content,
confirm if you can still see reproduced the issue.
So this is where we actually now have a look at the issue
and see if we can validate it.
If you can reproduce the issue, type yes.
Next to the first item in the list,
you just copy the cross and move to step four.
If you can't reproduce the issue, type no.
If it looks like the issue has been fixed already,
leave a comment with your findings and move to step five.
And finally, 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.
And then it says you can skip steps four and five below.
All right, so let's see if we can validate
or reproduce, sorry, reproduce the feedback
that was provided here.
So let's see.
They've given us the content title,
custom post types and capabilities.
They've given us the URL, so let's open that up.
So they've given us feedback about the tutorial here.
And actually let me share this GitHub issue link
in the Zoom chat so other people
can open the same issue with me.
All right, let's have a look at their feedback.
The page described above has mostly the same content
as another page, developing with user roles and capabilities.
I would expect this page to have completely different content,
since it is a different topic.
All right, so let's open this page.
Custom post types and capabilities,
developing with user roles and capabilities.
And they're saying the content is pretty similar.
The learning outcomes are identical.
One pre-hanging question.
Which does the default user roles and capabilities
What is the name of the method?
Comprehension questions are different.
The learning outcomes are the same.
And then the transcript.
The transcript is identical.
At least this first section I'm seeing on screen here.
Alright, so it does look like maybe this person copied the transcript across.
Let's read the rest of the feedback.
So the different elements are title, video, comprehension questions.
The same elements are learning outcomes and everything from introduction down.
Okay.
Learning outcomes and anything from introduction down.
So, introduction down is the same and all right, that is wrong.
So, what we need to figure out, so first of all, we have reproduced the issue.
So, if it can be reproduced the issue, the answer is yes.
We can confirm what this person has said.
So then let's come back to the handbook.
So if you can reproduce the issue, type yes,
and move to step four.
So let's move to step four.
Leave a note about what needs to happen next
and press comment.
For example, if a screenshot needs to be updated
and you are able to create the correct screenshot,
you can upload the image into your comment too.
In this case, it's not a screenshot
that needs to be up there, it's the actual content.
So we can leave a bit of a note here
about what needs to happen next,
and then we'll press comment.
So what I want to confirm is,
is this the correct,
like the correct content for this video,
or is this content correct for this video?
I'm just going to play the first part of the video.
(silence)
All right.
Let's see if the transcript matches that much.
If you want to learn how they can manage and how to add capabilities to an existing role,
and also how to create a new user role.
So it looks like the captions and audio in this video match the content.
So let me come over here and check the same with this video.
[BLANK_AUDIO]
They're talking about restricting access to custom post types.
And when we come down here, this is incorrect.
All right, so we've confirmed developing with user roles is correct.
and the custom post types and capabilities post is incorrect.
So let's clarify that in the comments down here.
So the content of,
let's see, the content of the page and video match
of this tutorial.
and then we'll leave a link to the one that does correct,
that does match.
And then the content of the page and video
do not match for this tutorial.
And then let's look at what the user said once more.
different elements are these so these don't need to be updated the same elements are learning outcomes and
everything from introduction down
so
Please update
Learning outcomes and everything from
They're right introduction
down to match the video content.
Please update learning outcomes and everything from introduction down to match the video
content.
And they also left a note here.
This article seems to have some titles and author notes cleaned up, which probably should
have been applied to the other article instead. So there are probably notes and stuff in this
one which should be applied to this one. So let's also write that. The think-back submitter
noticed there are some typos and notes which were tidied up on...
Let's copy that link across
Which should have been applied to
That one
But summary
one
Copy and apply
Apply the content from custom post-item capabilities to developing with user
roles and capabilities. Pop in the content from this to this and then step
to rewrite the learning outcomes and introduction on the custom post types to match the actual
video.
All right, so let's preview this before we submit it.
feedback validation check.
So we have been able to reproduce the issue,
and what should happen next?
So the content of the page and video match.
Well, let me say that bit differently.
The content of the page,
but this makes sense.
The content of the page and video match
for this tutorial,
the content of the page
The content and video on this tutorial match, the content and video on this tutorial do
do not match, that might be a bit easier to understand.
On the video on this tutorial match,
the content you're viewing on this tutorial do not match.
Please update learning outcomes and everything
from introduction down to match the video content.
The feedback submission notes, if there
are some typos and notes which are tied it up on this one,
which should have been applied to this one for the summary.
Copy and apply the content from custom post types
to develop a user roles and capabilities.
And then number two, rewrite the learning outcomes
and introduction.
And all on Tim from introduction down on this one
to match the actual video.
All right, so we've validated the feedback from the user
and we've written out the next steps that have to happen.
So we don't actually have an edit access
on Loanware Press to fix this,
but this will let the editors know what needs to happen next.
So we press comment.
All right, and that was step four
of validating content feedback.
And so then finally, we come to step five.
If the feedback has been validated
and the next steps are clear, ping faculty editors
in the training Slack channel, letting them know.
They will be able to move the issue
to the awaiting fixed status, apply the necessary changes
to the content, or close the issue for you.
All right, so we don't have access
to change the status of the issue,
but we can ping faculty editors who do have that active
and they can make the edits for us.
So to do this, we open the Training Team Slack channel.
So let me bring my Slack window over into the screen here.
Here's that.
Right, so this is the Slack head on.
And you'll notice we are in the training team.
And so it says, "We have an example message
you can copy and paste here.
High faculty editors, I have validated this content feedback,
link to GitHub issue.
Please move this to the Awaken Fixed Data
and/or acquire the necessary changes back."
So let's just copy that across.
So in the training channel, let me paste that message.
And actually, this section here, what should happen is when you type faculty editors, it
will go blue here, and you'll notice we have different people's names now pop up above
faculty editors.
This @ mention, what it does is it pings all the faculty editors in the training team at
one. So anybody who's logged in or has availability, they can pick up on this message and come
and make the edits for you. So high faculty editors, I have validated this content feedback.
Oh, let's use the actual GitHub link. I will copy that. All right. High faculty editors,
I validate this content feedback,
please move this to the awaiting fixed status
and/or apply the necessary changes.
Thanks. We can close this previous here and we press Enter.
You'll notice a GitHub preview pops up like this.
We don't need that.
You can close that off.
This has notified all the faculty editors in the training team.
they can now come and apply the fix we suggested.
And that is step five.
So we just finished step five.
Thanks for validating contact feedback, GitHub issues.
So, M, before you talked about rejecting feedback
and can anybody reject feedback?
So what would happen is if the feedback needs to be rejected
inside the GitHub issue here.
Here it says, if this is reporting issue,
can you confirm repost issue?
You would type no.
And then what should happen next?
You would leave a brief comment under this.
For example, I've checked the same page,
but the issue doesn't happen anymore.
Or it looks like the issue has been fixed already.
We can close this out.
So you leave a comment like that and press comment
like we did for this one.
and you would still come to the training team channel
and ping the faculty editors.
So you would say, hi, faculty editors.
I have validated this content feedback.
Leave the GitHub link.
But the issue doesn't happen anymore.
Can you please close the issue out for us?
And so you let them know.
And that just makes sure there's a second field of eyes
that checks the content for us.
And so, yeah, the editor would come over here.
They would look at the issue and they would go, OK, yeah,
This one doesn't need to be open anymore,
and they will close the issue for you.
And that's it.
That is how anyone can validate content feedback
for the training team.
Any questions?
Will the editor who rejected
have to add a note to.
No.
So they would just read your comment.
And as long as they agree with whatever
the validator has written, they would just press Close Issue
and close that for you.
They won't necessarily leave a comment.
How do you search for a specific issue?
So let's come back over here.
So at the beginning of the check steps here,
so it says, open the list of content feedback awaiting
validation.
This is the important link in the process.
So when you click on that link, it
opens the page of all the issues awaiting validation.
And most of them have a bit of an explanation
in the title here, so broken linking course,
or not clear that a block theme is needed.
So this will give you a rough idea of what the feedback is about.
You can choose any of these feedback, pieces of feedback,
and validate them.
So really, we need all 28 of these pieces of feedback
validated.
So you can choose any out of this list
and work through the list for us.
So if you don't know the title of the issue,
Someone else created the issue but didn't tell you
the name of the issue or provided the link.
So how do you search for that issue?
So are you talking about a validator
or are you talking about the editor?
When an editor comes and updates an issue,
they do need the link.
So you'll notice I gave the link in the Slack message here.
So we really do need to share the link with each other.
But does that answer your question?
You'll notice what we've been talking here.
One of our editors has put down, and they've
been working on the issue.
So that's good.
Assuming that you created an issue about a problem,
I reported, but you never provided the link
or the title of the issue.
I think that the easiest thing would be to contact
whoever you reported the issue to
and maybe just directly ask them and say,
"I gave this feedback, I don't see the feedback in this list.
And can you help me see and make sure my feedback was accepted?
I guess what you can do, just coming back
to the main screen of content feedback here,
you'll see 46 pieces of feedback have been completed.
You'll see 13 have been triaged and are still awaiting your fix.
So what you could do is try searching here, I guess.
And that will search all columns.
And that might give you an idea of where your feedback has
move to. For example, let's say broken, oops, by type broken link. You'll notice this has
now filtered the issues. So we see there are six issues related to broken links. There's
one issue still awaiting to be triaged, three that are waiting to be fixed, and two that
have been fixed. So this is probably the closest thing to the search feature you're looking
for. So that is in the content feedback project board. Under content feedback, we have all the
issues here. So you can filter issues out by keyword and hopefully find the one you're looking for there.
Otherwise, thank you for joining.
Tracy, were you saying something?
Thank you.
Oh, thank you. All right. Yeah, I'm a co-hosting and yeah, I look forward to having you, Em,
and anybody watching this recording afterwards to join us in validating content feedback.
So thank you for your time today. Thank you, Tracy.