 Okay, so hello everyone and welcome to today's online workshop. These are hosted by volunteers in the training team. And these are, I guess, official education hours by the WordPress project. So welcome to today's online workshop. Today's topic, we'll be talking about how to vet content topic ideas for the WordPress training team. So what is the WordPress training team, first of all? How many people know about the website Learn WordPress? Hopefully everybody's heard of it before. If you haven't, okay, yep, I see a few hands. If you haven't heard about Learn WordPress, this is the official education website for the WordPress project. So you can go to YouTube and find videos, you can find information on people's blogs. But this is where the WordPress project publishes different types of learning material. And we have four different types of content on Learn. There's an easy way to see it on this homepage. I'm just going to click in here. All right, and I want you to focus on the menu bar at the top here. So Learn has four different types of content. We have tutorials, we have online workshops, we have courses, and we have lesson plans. So tutorials are five to 10-minute short videos that talk about a specific topic. Online workshops are hour-long interactive sessions, like we're hosting right now, where people can ask questions, investigate new features of WordPress, test out new ideas, and meet other community members as well. Then courses, these are online courses where you can work through on your own. The Learn WordPress website will record your progress. So if you have to step away in the middle of a course, you can come back at the late today and continue with your learning. And then finally, lesson plans. Lesson plans are for teachers to use when they teach a classroom or a WordPress meetup group, different topics about WordPress. So the first three resources are aimed at learners of WordPress, and lesson plans are aimed at teachers of WordPress. This is an important part in the topic vetting process. So keep in mind we have three types of content for learners and one type for teachers. Now, for any of these content types, before content creator creates the content, the topic of the content is first vetted. And so that's what we'll be talking about today. So somebody has an idea. It'd be great if we had, say, an online workshop about building an online store. So somebody makes that suggestion to the training team. And then there are a group of people who look at that topic idea and flesh it out a bit. So making an online store is important, but what does that actually mean? What does the user have to learn throughout the process of the course in order to achieve that? And then they also assess whether that's a priority for the training team right now. So currently, the training team has like 100 topic ideas we had submitted. And so it's important to line those up in priority so we can work on the high priority content first. And so vetting content topic ideas involves fleshing out a topic idea in preparation for the content creator and assessing the priority. And until now, this process has been very limited in that you needed special GitHub access in order to vet the topic ideas. And so for about two years, there's basically been no one in the training team vetting topic ideas. Whereas in the last month, we finally updated the process and open it up. So now anyone in the WordPress community can vet topic ideas. And so I'm here excited to share with you today how you can also fit content topic ideas for the WordPress training team. All right, so that's what we're going to be talking about today. Any questions so far? Anything you want to clarify before we jump into the content? Who votes on or who makes the final determination as to what will be selected topic-wise? Yes, so we call the people who vet topic ideas subject matter experts. And anybody can become a subject matter expert. That's what I'll be introducing today. But in the training team, we also have a group of dedicated contributors. We call faculty members. So we have general subject matter experts, which anybody can become. And then we also have faculty subject matter experts. And these people have the special access on GitHub and they can make the final say. So a general contributor can say, I think this is high priority. And I think these should be the learning objectives and they can flesh the idea out. But that will get passed through a faculty person that will just make sure everything is correct. And on the other hand, because anybody can do this, we could have like experiments get involved. So we do have a faculty person who does the final check. But basically anybody can vet the content topic idea. Hopefully that answers your question. Great. All right. So for many of the training team processes, the most important document to refer to is the team handbook. Now I have this bookmarked in my browser. I'm going to send the link to everybody in the zoom chat here. And if you want to get involved with the training team, I highly recommend you bookmark this as well. The training team handbook has all the how to guides about the different processes in the training team. So I might sort of increase my forms a bit so it's a bit easier to see. Okay. So this is the handbook. If you're brand new to the training team, then I recommend this getting started link in the top menu bar. If you click on getting started, this will take you to the training teams onboarding program. And that will tell you how the training team communicates with each other. We actually have five different roles in the training team. And so we get the onboarding program will walk you through each of those roles and you'll even walk you to your first contribution. So you can choose the role that meets your interests and then make your first contribution. You'll get an idea of how the training team works. So if you're brand new to the training team, I highly recommend the onboarding program getting started. The handbook is what we're going to look at right now. And then the third link is the faculty members. So I mentioned these are the people who have dedicated certain amounts of time from their week to the training team. So by clicking here, you'll be able to find all the faculty members. And these would be the best people to ask questions if you have questions along the way. So yeah, that's just the menu at the top here. What we want to focus on today is vetting topic ideas. So if you look in the contents down the left, you'll see we have a lot of content. One of those is titled how to guides. So we'll open the how to guides and then further down we'll see how we use GitHub. We actually this this menu actually needs to be tidied up a little I think we have a lot of how to guides at the moment. But what we want to focus on today is how we use GitHub. And then underneath that you'll find vetting topic ideas. So we went to how to guides, how we use GitHub and then vetting topic ideas. And this document has a step by step guide so that anyone can fit topic ideas. So I've just dropped the link in the zoom chat to make sure we're all on the same page. All right. So let me just read this introduction. The first step to getting new quality content on learn WordPress is to vet the various content topic ideas shared by the WordPress community. These ideas can stem from personal interest to crowdsource consensus. But no matter how it comes to the training team, it will require vetting before this green link for content creation and publication on the learn WordPress website. So topic ideas can come from anyone. We have a form on the learn WordPress website that says submit your topic ideas here. So we can have anybody in the world submit topic ideas. And so the vetting process helps those ideas get into content creation. All right, subject matter experts and we call them SMEs are community members who utilize their expertise to vet submitted content topic ideas. In general, SMEs look to assess the ideas for relevance and priority. SMEs may also be contacted by content creators as the content is being developed, requesting additional information and or assistance to create accurate and informative content. So subject matter experts, there are two main aspects to their role. The first one is vetting topic ideas. And we say, and you'll notice, oops, you'll notice it says relevance and priority. So we look at topics to see their relevance and priority. And the other aspect of an SME is content creators may contact them as they create the content. So the way we work in the training team content creators don't have to be experts about the content they're making. Like in an extreme case, the content creator could be making developer focused content, but they themselves don't have to be developers. What they do is they work with the subject matter expert, the subject matter expert hands them the information, and then they turn that into a course or a tutorial or an online workshop. And so when subject matter experts vet a topic idea, they are leaving their name on a GitHub issue and saying, I have expertise in this area. And along the way, if you have questions, you can reach out to me and ask questions and I'd be happy to help. So the subject matter expert is vetting the topic ID, but they're also making themselves available to whoever comes along and makes the content in future to help them out as needed. And then the final paragraph outlined below the guideline are guiding processes for vetting content topic ideas alone WordPress. So under here we have the exact steps, which I'm going to demonstrate on the screen. Any questions so far, let me pause there quickly. Any questions about what the subject matter expert is. You're very clear. Thank you. All right, great great to hear. All right. Now, if you have a question and I don't stop talking you're free to leave it in the zoom chat as well. So let's let's continue down the document. So how a topic ideas submitted. So all new topic ideas are created as a GitHub issue on the learn GitHub repository. Using the topic ideas GitHub issue template. Once submitted issues are automatically added to the learn WordPress topic vetting project board. Issues are first triaged for spam duplicates etc by administrators before landing in the awaiting vetting column for SMEs. All right, so that's a lot of information so let me pause there. And the training team works on GitHub. So in order to vet content topic ideas, you need a GitHub account. But so this is the learn WordPress GitHub repository. And there's a link here to the topic ideas GitHub issue template. And you know what I did this workshop yesterday and realize this link was incorrect. So before I forget, let me quickly update this handbook page so we have the correct link there for everyone. So you'll see the handbook is also a WordPress website. There we go. All right, so coming back down here. So what people do is they use the topic ideas GitHub issue templates when you click on this link. You'll notice the training team has two, four, six, eight, nine different issue a GitHub issue templates people use. We have templates for bug report and we have templates for content feedback, etc. Down the bottom here we have topic idea. And so when somebody has a new topic idea, they will create a new issue here. So when they click that, they can type their topic title up here. There's a bit of an explanation here of what to do. And then they list topic description, audience, learning objectives, content type, WordPress version. And will you be creating this content or not and finally related resources. So somebody feels out as much information as they can and submit this as a new issue. Now what happens to that issue is that lands in the learn WordPress topic vetting project board. I'll open this project board. And this is what this project will look like. So we see somebody submitted a topic idea recently. So that is waiting in the awaiting triage column. And this column is for administrators. So they first check to make sure it's not a spam issue because we have had people submit spam in the past. If it's spam, we disclose it out. And we also make sure it's not duplicate. So learn WordPress already has hundreds of resources and sometimes people might suggest something that actually already exists. And so administrator just make sure everything's filled out. It's not spam. It's not duplicate. And once they've checked that, the issue comes into the awaiting vetting column. And this is where subject matter experts work. So we have 38 topic ideas at the moment waiting to be vetted by subject matter experts. Once a topic is vetted, it moves out of this project board into the content development project board. So then content creators can take that issue and create it. But sometimes issues don't get past the vetting process. For example, somebody may have suggested an outdated issue like that was true with WordPress two years ago, but it's not a WordPress feature now so we don't need it. Sometimes a topic is a good idea, but a very low priority for the training team at the moment. And so sometimes we just close topic ideas. And so we have a closed column here so we don't lose the ideas. The ideas are still here, but they just don't make it to the content creation project board. So you can see issues move from left to right. Now the other thing is, the awaiting vetting column has 38 items. And for a subject matter expert, you're not necessarily an expert in everything that you have specific areas you're an expert in, and finding the issues relevant to your expertise out of out of this whole column can be a bit daunting. And so what we've created are some tabs at the top here that split out the the second column into different areas of expertise. So for example, if a topic was submitted related to the related to accessibility, it would show up in the accessibility tab. At the moment we don't have accessibility topics. So this is blank, but if there was a topic about accessibility, it would come here. We also have block editor. So we see here, we have 10 issues related to the block editor. So if you have a bit of understanding about the block editor, you could triage any of these issues here. We have issues about contents actually writing content for a website. And then we have issues about contributions, so how you can contribute to the WordPress project, etc. So you'll see we have roughly 10 different areas of expertise and topics will fall under at least one of these expertise. And so as a as a subject matter expert. Rather than looking through this whole waiting vetting column, you can simply click through to the area of your expertise and bet one of the topics sitting there. All right. So that's an overview of GitHub and how the issue moves through GitHub. Any questions about that. Just to clarify, for the subject matter expert is that. So that's kind of a self selected thing as far as if you have a GitHub account you just click on what you feel comfortable in and can drop. Hey, I know about this if you want feedback or etc. Yep. Yes, exactly. I do recommend you go through the onboarding program, we have the onboarding program splits into five onboarding paths. And we have a path for, for example, content creators, we have a path for content translators, and we also have a path for subject matter experts. So if you take the onboarding program first. I'll give you the onboarding is about 30 to 60 minutes, but they'll give an overview of your area of expertise. And basically once you've done that, you can jump right into GitHub and just start betting topic items. Got it. Thanks. Yep. All right, so that's an overview of GitHub. So now let's come down to the actual triaging steps. So we have here, I'm back to the main handbook page, the betting topic ideas handbook page. And then, okay, topic items below is the list of details on the topic idea submission. So we had a look at that before in the GitHub issue, whoever submits the idea will fill out as much of this as possible. The next the section says topic idea triaging performed by admins. So, whoops. That was, let's see, moving issues from here to here. In order to move issues between columns, you need that special GitHub access and not every contributor has that so that is reserved for faculty administrators so you can basically just ignore the items here and administrator will triage that at some point or another. So we'll skip all that. And now finally, betting topic ideas. So this is the main focus of today. All right. It can sometimes be difficult to assess topic ideas on an individual level. So don't hesitate to reach out to faculty, faculty, subject matter experts for a second opinion along the way. You can do so by peeing the faculty SME group in the training slack channel. So I mentioned before we have the faculty program and this is a dedicated group of contributors who have given certain amounts of time from their week to the training team. While you're vetting a topic if you have questions, feel free to ping the faculty subject matter experts in slack. So slack is the tool the training team uses to communicate. And you can ping individual faculty members as well. But we recommend using this slack call word. So if you type at faculty hyphen SME, this will ping all the faculty members in the training team at once. And then anybody who's online will be able to get to you. So if you ping one person and they're on vacation for 10 days, you might not hear from them for a while. But if you ping the whole faculty subject matter expert group, then anybody who's online will be able to answer your questions for you. So just hopefully that puts you at ease. Like if you start on this process and get stuck at any way in the process, there is a group of faculty people who can help you with that. Yep. Aileen are you talking about this link vetting topic ideas. Yes, please. All right. Yep. So I've just sent you the link to this section of the handle, the vetting topic ideas section. Perfect. Thank you. Yep. All right, now steps to vet topic ideas. So this is a six step process. And I'm going to pick up an issue right now and actually work through the steps for you. The step one, open one of the topic views link below to vet ideas related to that topic. So we have different links and activity block editor content, etc. And these connect to the tabs at the top of the guitar board here. So as long as you bookmark the handbook page, you can quickly access each of these items. So let me see what am I going to work on today what's contribution. Content. Frequently used blocks review the common blocks and how these are often the most suggested. You might as well look at this issue. All right, I'll open this up, and I will be vetting this one today. So that was step one. Open an issue, then copy paste the following text into the comment. This will act as your guide as you vet the topic. What you do is you just copy all of that. And then I come over here and in a new comment I paste that. And this will act as my guide as I vet this topic. So what does the checklist have it says, first of all priority, either high, medium or low. So I decide a priority. And then feedback regarding the topic description feedback regarding the learning objectives and any other feedback. And then finally related resources. If you know of other related resources that would assist in creating this content, listen below. All right. Well step two was copying that across step three. Take note of what content type this is a suggestion for. This should be listed in the issue body in the issue title and added as a label. So someone might be suggesting a new content type for an existing piece of content. And that is okay. Assess whether the content type would make sense for the topic being suggested. All right, so we come over here. And at the top, maybe I should increase the font size here a bit more. All right. So at the top you'll see this is frequently used blocks lesson plan. So at the beginning of this session I said we have four different content types on learn lesson plans are aimed at teachers who teach a classroom of users. So this is a lesson plan for teachers teaching about frequently used blocks. So just keep that in mind. So we're making this for teachers. So you'll see the audience. So the topic description was review the common blocks and how these are often the most suggested. So it's talking about the block suggestions in the block editor. I guess audiences users learning objectives. Okay, this person didn't suggest it didn't submit any learning objectives. So we'll need to fill that out. Content type is lesson plan. WordPress version optional. We'll be creating this content. Yes or no, it doesn't say. All right. So that gives us an overview of what this idea is about. Next step for assess the relevance of the issue and assign our priority. So if an idea is not relevant at a brief comment describing your reasoning and press close the issue so you can just close an issue. If you feel like this is just not relevant like maybe it's not a WordPress topic. Or maybe it's just nobody's going to need that content. In that case we can just close the issue. If an idea is relevant right either high, medium or low in your comment. A relevant topic. So how do you decide relevance a relevant topic is timely with the latest releases up to date with latest practices and follows the team's promotional guidelines and GP of best practices. Priorities assessed by whether or not the topic is critical to something in the latest release hits on the needs analysis trend or fixes gap. In previously published foundational content. So we talk about relevance and priority here. So if this is something related to the most recent WordPress release. That is a very relevant topic. Or if it's talking about recent practices. That's a relevant topic as well. In this case, frequently use the blocks. Isn't necessarily tied to the recent WordPress release. And it isn't necessarily tied to like best practices either. So in my mind this is going to give us a lower priority. And we also look down here priorities assessed by whether or not the topic is critical. This topic isn't really critical. People don't need to know about the most used blocks in order to use WordPress. Does it fix the gap in previously published foundational content. Now, if you're familiar with the loan WordPress website you'll start to get an idea of what content we're missing. So if you're not sure here you can just skip that. But overall, I'm going to say this topic is is good. But the priority is low because it's not necessary for somebody to be able to use WordPress. So what I would do is I would just type low. All right. Anton asked, do you give one rating on high, medium, low? Yeah. Okay. So we look at relevance and priority to choose one rating. So that was step four. And would you believe this handbook page has two step forwards? Let me quickly update that as well at the moment before we forget. I think topical is one, two, three, four. So this item should be starting at five. There we go. All right. So come back down here. So we just did this. We just assigned the priority step four. So next we'll come to step five. Assess the submitted details of the topic and provide feedback. See also how to finalize description and objectives. So the next point is the feedback. We got feedback regarding the topic description feedback regarding the learning objectives and any other feedback. So to be honest, this topic didn't have a lot of description like review the common blocks and how these are often the most suggested. There isn't a lot of detail here. So the subject matter expert has two options. The first one is to send the issue back to the person who submitted it and say, could you please add a little bit more detail so we can bet this better? Or the second option is for the subject matter expert to just go ahead and flesh out the description and learning objectives a bit more. I'm going to take that path so you can see how I decide learning objectives in that. But if it really, if you feel that there just really isn't enough information here, you can send the issue back and ask the submitter for more information. Now I will say in this particular case, this says Courtney has submitted the issue, but I know it isn't Courtney. So the training team used to use a different software to manage our topics, topic submissions called Trello and Courtney imported all the data from Trello into GitHub. So that's why her name comes up on a lot of topic ideas. Courtney has made a lot of suggestions, but she isn't the one who submitted every single thing. So I would just want to clarify that the fact this issue doesn't have a lot of information isn't necessarily a bad sign about Courtney. It's just what was submitted years ago and Courtney imported that into GitHub. All right, so topic distribution review the common blogs and how these are often the most suggested. I'm going to take a bit of creative liberty here and frequently use blocks. I'm going to imagine we're talking about a casual blogger. And so a casual blogger is probably going to be using the paragraph block, heading block, maybe image blocks. And I'm wondering if like using those blocks from an accessibility and SEO perspective could be an interesting topic to introduce here. So frequently used blocks are like heading, but maybe teaching how to nest heading blocks is something new users could benefit from. Or if we're using image blocks, then the importance of adding alternative text, et cetera, could be something we could talk about here. Another block, frequently used blocks, like the column block, those layout related blocks could be something a new user would benefit from learning from. So I'm starting to form a thought here we can talk about accessibility and SEO when using blocks and also maybe the layout related things. So the details of the description feedback and the description. Let's develop this content with two focuses. And then I might say this ability SEO considerations should make when using any image, et cetera. And the second one is introduce different layout grouping related blocks and how they can be used. All right, so I'm sort of just fleshing out the description a bit more of what this lesson is going to be talking about. And next feedback regarding the learning objectives. So this didn't have any learning objectives so we can finalize that for this issue. And coming back to the handbook you'll see there's a link how to finalize the description and objectives. This is a pretty good page it's short it's short but it gives you an idea of what a learning objectives in a learning objective is. So learning objectives must contain four parts. An audience. Who are we talking about behavior. What is the new knowledge skill or attitude you hope to achieve condition. What are the circumstances under which they will demonstrate the behavior and agree how well or how often will they demonstrate the behavior. That's an ABCD model. And these should be specific measurable attainable and time bound. So, let's say in this case we're talking about users we know the audience is users of people who belong or create websites. What skill do we want them to achieve so we can write two or three learning objectives. And we were talking about accessibility in SEL consideration so that's a skill we want them to achieve. What are the circumstances under which I demonstrate the behavior I'm going to say we want them to demonstrate this behavior when they write content. And so putting all that together. Let me see if I can draft our first learning objective. The users will be able to use headings. We'll be able to nest headings appropriately when writing content. We'll be able to use we're able to let's say we're talking about frequently use blocks or really be able to use the headings locks appropriately when writing content, considering accessibility and SEO best practices. So, this is very, we're trying to make this as specific as possible so who, when, what are they going to do how they're going to achieve that so be able to use any box so let's let's make this a bit more specific. We'll be able to write content with headings. Place appropriate. Throughout considering user to write content with headings, hitting blocks place to probably throughout considering SEO best practices alright that looks like a pretty good objective to me. And the second objective we talked about layout and grouping related blocks so. I think the columns block is something people might be up might be interested in. And the next one is like grouping and you placing things in a row, etc. So, let's see what is something specific we want people to achieve with these layout blocks and users will. Describe recall recognize skills apply modify construct. Construct looks good and pretty. So I'm using the words here sort of brainstorming assistance. So let's see books. Be able to construct pages that include a columns block and learn. I would construct pages that include columns block columns, a columns block. So please include columns block. If anybody has ideas here, feel free to help me out. I'm being watched by half a dozen people which is getting me nervous. How about we talk about how the columns block behaves differently on mobile and desktop and people would still be able to build a page with that in consideration. So you just unmuted. What about are there any kind of add ons. I'm not. I don't have a lot of word word press experience. So what is my terminologies off. Let me know. Is there anything that they could add for SEO is that Yoast or something like that or. Yeah, we couldn't do that. To embellish that, so to speak. Yeah, to build on that. So this is like on page SEO things that you could do. And then do you want to expand to something that you could add to the site that could help once you get your headers. What about running like wave wave checks. You know, those accessibility checks using those tools. Can you say something about that here. Yeah, I'm, I'm, I want to keep in mind the topic here was about frequent years blocks. Okay, I'm sorry. No, I did. Yeah, no, I mean, the ideas you have a good for example if the resource was about SEO accessibility. I think for your topic and I didn't know was what. Yeah, yeah, yeah, yeah, yeah. I just thought something else frequently used block might be the navigation block that one is a bit intricate and so that might be something good to bring up. Anton just left a comment to since users will be able to create a variety of responsive layouts using the columns and roblox and different trade between the two. You know what, I love that. So I am going to copy that and pay sending to get that I okay if I use that as is. Yep. So users will be able to create a variety of responsive layout using the columns and roblox and differentiate between the two. I think that's really good. And I'm going to add one more than navigation block because I think that one is another frequently used block we can talk about so. User users will be able to create a new navigation menu in the navigation block. And other great new navigation and navigation block and position that or add back to the header of their of TTIR site. All right, so let me just switch that to previous it's been easier to read. So feedback and learning objectives so feedback. As there were no learning objectives submitted. Let's use these. All right, so users will be able to write content with heading blocks placed appropriately throughout considering accessibility and as your best practices. Users will be able to create a variety of responsive layouts using the columns and roblox and differentiate between two. And users will be able to create a new navigation menu in the navigation blog and add that to the header of their site. I think we have anything to be said about images. Oh yeah, I mentioned that didn't I. So, hitting blocks. Users will understand the importance of out ticks on images and know where they can edit on their site. How does that look. Yep. I think that looks pretty good. So any other feedback. We're covering a lot of ground in this content. Try and keep trying keep this to an overview. So this was a lesson plan for teachers and so if you start like diving into each of these as you said we can start talking about plugins and all that and they can I think you can get quite in depth. So just a piece of feedback we're covering a little ground in this content try and keep this to an overview and share related resources for students as needed. Can you get an exercise like a minor exercise based on this. Do you do that like for teaching plans say okay. With this information. I'm a content creator would then take this and then build out the lesson plan and the activity and the questions and that. If you have ideas, feel free to leave those here. But it's not a necessary part of the topic vetting process. Okay, okay, sorry. No, no, no, no, no problem. The other thing you can do is, for example, a subject matter expert can also become a content creator. So if you look in the top issue here you'll see it says will you be creating this content so whoever submits an issue can actually raise their hand and say once it's better I would like to make this. In this case we don't have anybody who's raised their hand yet. And so if you really like this issue and you think you can make it. You can leave an extra comment at the bottom so you better that you've added it as an SME. And then at the bottom you could say, I'd also like to create this or something and then we can assign the issue to you. So people can have more than one role. All right. So we were just doing step five, assess the submitted details of the topic and provide feedback. Number six, add links to any other related resource you think will assist the content creator when creating this content. So you see here related resources. Now, you can add whatever you want to. For example, if you've seen a YouTube video that talks about a very similar topic. You can leave a link to that YouTube video and then the content creator can reference that when they make the content. Or like if you've seen an article on let's say WP beginner or like another website like that, you can reference that. Or if there's like documentation official WordPress documentation that's related. We can mention that. So really anything that would help the content creator. You can list. Yeah. So just, just one thing. Yep. Navigation block demo the other day would you could we and it's going to be on WordPress TV I think Courtney posted that could could we put a link to that. Yep. Let me have a look. So this is WordPress dot TV. And something about the navigation block. Yeah. Like this. There it is. It's a bug craft. Yeah. Yep. So we can take that. And the content creator may watch this and add it to their content or they might like a related resource to the content when they share when they create it. So let's see. So you drop the link like that. So you can spend a bit more time on that if you want for the sake of this workshop I'm going to start wrapping up. But that was step six and any other links. And then number seven, the final step. Once you've submitted your comments ping faculty admin in the training site panel, asking them to process the issue for you and move it to the content developer project board. All right so. That's it. We've we've we've added this topic so we'll press comment. All right. And then what we want to do is we want to move this issue from the topic betting project board into the content creating project board and only faculty have the access to do that. So what you would do is you would go to the training slack channel. And this time we're pinging faculty admin. So, I think up here there was a comment about pinging faculty SME if you get stuck with the topic betting process down here you can ping faculty admin. And then admin with availability will be able to move the issue for you. So we even have a message you can use. Hi faculty admin I've read that the topic on this GitHub issue link to GitHub issue. Could you process this issue and move it to the content development project board please. Thanks. I am a faculty admin and I have access to do this so I will just show you what an admin would do. But what an admin would do. Or actually, for the sake of admin who might be watching this video. Let me just show you what the guide says so we actually have a guide here for faculty admin about moving better topics to the content development project board. So the steps are. Label and move topic ideas so ensure all details have been filled in either by the issue the topic submitter or in the comments by the SME. So the admin would check this you would come down here and check that yep this all looks good. All right. And at least one each of the following labels priority audience experience level and version. So what an admin would do is they would look at what the SME wrote down here and the SME said low priority. The admin would go okay so the priority is low. And then an audience so audience was already added here. Experience level experience level was already added as well WordPress version isn't relevant. So all the labels are added. Step three, remove the needs subject matter expert label. So I will remove that. And basically, by me commenting on this issue here. I've told whoever content creator comes along and pick this up that I'm a subject matter expert they can ask questions if they get stuck as they make the content. So commenting is sort of leaving your name there for them to contact you again in future if needed. And then move the issue from learn WordPress topic vetting to learn WordPress content development. So I will move this. So projects I will move it from topic vetting to content development and the status is ready to create. So now a content creator and come along and create this content based on the information we provided. And then finally step five copy paste one of the following as a comment to the issue listing next steps. So when the content creator comes along we want them to have clear next steps as to what to do. And so in this case it was a lesson plan. So I will copy this message here. I will paste that down here. And the comment says this topic is ready to be created please follow the handbook page lesson plans for next steps. And now ready for a content creator to create. All right so those final steps for faculty administrators watching this recording later. But that is an overview of how topic topics created as a GitHub issue, how they move through the flow, how a subject matter expert method and how it's finally sent to the content development project board. Any questions about any of that. So it seems pretty proactive then it's like you grab what you want to work on it's not assigned to you. Correct, but subject matter experts, anybody can just jump in and work on the issue. Okay. Yeah, I want to create content I have to wait until it's in a certain pipe, and then pick it up, like the last piece where you said where it would go. Yeah. So yeah this this would be another totally different online workshop but just to give you a quick glimpse. The training team has a learn WP content development project. So we were looking at the topic vetting project board. If you go to the content development project board this is where content creators generally work. And you'll see here we have 94 issues ready to create. So content creator could pick up any of these issues, which have all been vetted and start working on that. And then these go to draft in progress review in progress and then publish the call so this goes through like a similar process, which is all documented in the handbook, but would be another online workshop. Okay, thank you. Yep. And then I have a question about John can be a topic. Like if something comes up in a workshop, and I'll give you an example from a couple of times ago. Someone, they mentioned that okay there, though, recording will be on, you know, on WordPress TV, and we'll add the captioning. It's like, well, how do you add the captioning. So it's not really WordPress, it could be for anything it's about video but it was came up in a WordPress meetup so would that be eligible to be worked on, or Yep. Very good question. In the trading team, if something is related to WordPress even remotely, then that is a good topic to suggest. So for example, WordPress TV is a WordPress project. And so, in videos that go on to WordPress TV need to be subtitled. And so an online workshop on how to subtitle videos would be totally acceptable. And actually I would say it's like a medium or high priority item because it's it's a very necessary part of the training processes. So, yes. Yeah, to give you another example. I have done online workshops on, for example, domains or like web servers. And these aren't specifically tied to WordPress like you could use non WordPress content management systems, and you would still need a domain you'd still need a web server. But they are necessary for people wanting to build out WordPress websites like knowledge about domain is still important. So although WordPress doesn't come up even once in that presentation. It's still relevant to WordPress and therefore it's a content the training team can work on. So it just needs to be loosely connected to WordPress and it would still be okay. All right. Well, we're at the top of the hour. So thank you everybody for coming and more than anything do come back topic ideas and that was what the session was all about but hopefully after watching this presentation you are now competent enough to go ahead and try betting some content topic ideas. Again, if you have questions, you can reach out to faculty in the training slack channel at any time and people can help you. And so yeah, thank you very much for attending. Thank you. Have a good night. Yep. Morning. And thank you Tracy for, yeah. And thank you Tracy for co hosting. Thank you, Tracy. Anytime. Almost. Have fun on the beach.