 All right. So once again, hello everyone and welcome to this online workshop. These online workshops are hosted by volunteers in the WordPress community. And the goal is to provide a safe space where we can ask questions, learn different features about WordPress. We're in today's case learning about contributing to WordPress. So feel free to use the Zoom chat to ask your questions anytime through the presentation. You can also unmute and ask your questions directly and I'd be happy to answer them for you. So I'm Ben. I have been using WordPress for eight, nine years. I live in Japan. So it is 9 a.m. Friday morning for me right now. And I have been working with the WordPress training team for just under two years now. I joined the team two years ago. And then lastly, I was nominated as the team rep or the team representative. And the team representative's main role is to make sure the team runs smoothly and to then connect the team with the main WordPress project. So if there are any mandates that the project wants the team to work on that will come through the team rep to then distill into the team. And the opposite as well if there's any questions or problems the team encounters that goes to the team rep back into the WordPress project. So, yeah, I'm excited to introduce the training team to you. Today's goal is to give you an overview of what the training team is, what we do, how we communicate, how contributions are made. And then to give you some extra links for you to then investigate further. Ultimately, I would love for everyone in this call to join the training team as a contributor. But hopefully you'll have enough information and resources to take home with you. And to investigate more, consider if this is the team you want to join a lot. So let's start from make.wordpress.org. So I'll drop this link in the Zoom chat as well. WordPress is a software built by volunteers all around the world. It's a free software. It is open source, which means anybody can look at the code. Anybody can contribute to the code. Anybody can redistribute the code. And so it is a software, but WordPress is also the name of the community behind the software. So we have this make.wordpress.org page introduces the community. So WordPress.org will take you to the software download page and the make.wordpress.org takes you to the community page. So you can get to know the community that makes WordPress. And there are thousands of us, tens of thousands, I think, all around the world who contribute to WordPress through different themes. And I won't go through all of them, but on this page, you'll see a list of all the teams involved in creating WordPress. So we have the core team, which are responsible for making the actual core software. And we also have a design team who figure out how the new features are going to look in the software. And we have the mobile team to make sure the software runs correctly on mobile. We have an accessibility team to make sure the software is accessibility compliant. We then have polyglots who translate the software into different languages. We have support. We have documentation, themes, et cetera. And the list goes on, I think we have like 22 teams right now. The newest team was the sustainability team that was created just last year, I believe. So this sort of gives you a quick glance that it's not just coding. There's also people who consider like a performance side of it or people who contribute photos to the WordPress photo directory. So there's a lot more you can do in WordPress besides just coding as well. And today we're going to be looking at the training team. So the training team focuses on creating education resources to help people learn WordPress. So we have the software, we have the documentation, but then when somebody uses WordPress for the very first time, they still need some hand holding to just understand how all the pieces fit together. And the training team's mandate is to create those resources, those video tutorials or these online workshops you're attending right now to help people understand WordPress and help them get involved more. So the training team, we operate the website learn.wordpress.org. At the moment we're on make.wordpress.org, but learn.wordpress.org is the WordPress Projects official education website. So I'll drop that in the meeting chat here. And we call this Loan WordPress. So learn.wordpress.org and the Loan WordPress website. Again, this website is fairly new. So until a few years ago, the main place people would gather and learn about WordPress was at community meetups. So there are meetup groups all around the world happening quite regularly where different people get together, ask questions, share knowledge and learn about WordPress. Well, as you all know, COVID happens and meetups all around the world paused for a few years. And so the WordPress Project realized we needed a new online place where people could get together and continue learning about WordPress. And that's when the Loan WordPress website really kicked off. It was sort of in the works from 2012, I think it was. So just under 10 years, but it really kicked off during COVID. And so the Loan WordPress website, I won't go into too much detail, but I will say we currently have four different types of content here. And it's easiest to see in the top menu bar. So Loan WordPress, we have tutorial videos, we have online workshops, we have online courses, and we have lesson plans. So tutorials are about five minute long videos and that teach you a feature about WordPress. This could be about using a block editor. It could be about how to run site backups. It could be about how to develop your own code for your website. So we really have a lot of different topics here. Online workshops, workshops like you're attending right now, live virtual sessions where you can join, ask questions. And these happen, I think we have like two, three sessions a week at the moment going on at different times all around the world. Online courses are your typical online courses. They'll be the self-guiders, lessons you can take one after the other. Some of them have grade assessments for you to sort of learn a chunk of WordPress. We have like how to build your first website. We have how to build your first block theme. We have how to contribute to the polyglots team, the translation team. So again, many different topics covered in our courses. And then finally lesson plans. Lesson plans are different from the other three in that they are aimed at the teachers of WordPress. So if you are a teacher and you're about to teach a class, some topic about WordPress, you can download our lesson plans and these will give you like a 60-minute class outline. So it gives you the different teaching aids you can use, different activities you can give your class. And these resources are aimed at helping teachers teach WordPress. So we have four content types at the moment. But what we're finding is people are getting lost on the website. So people come to the website for the first time and they want to learn about WordPress, but they end up in lesson plans or they want to teach WordPress and they end up in online workshops. And so currently the training team is doing a full redesign of the Learn WordPress website. Again, this is something the project sort of put together during COVID. We had to quickly get resources together to help the community. So we got through COVID and now that different meetups are starting up again. We're taking some time to actually reevaluate this website and redesign it so that it is the go-to resource for anyone all over the world who wants to learn WordPress. I think now if you want to learn something about WordPress, you'll probably go to your favorite search engine and search it. You might even go to YouTube and search for video and you have tons of resources there. The WordPress projects goal is that all these different content creators working all over the world can come together and contribute their resources into one location. And this Learn WordPress website becomes that go-to resource for learners of WordPress. And the training team looks after this website. All right, let me pause there quickly. That gives you a very high-level overview of where the training team fits in the WordPress project, what our mandate is. Are there any questions so far? You can unmute and ask or you can drop in the Zoom chat. If you don't have any questions, you can give me a thumbs up. Any questions so far? Gwen, thank you for the thumbs up. You're welcome. All right. Everything clear, Carolina, thank you. Okay, so now that you know what the training team's mandate is, how do we actually do that? So we are people living all over the world, all different time zones. How do we actually coordinate and look after the Learn WordPress website? So coming back to the make.wordpress.org page here, each of these team names will take you to that team's blog. Every team has its own blog. I'm going to click on the training team. And this will take us to the training team blog. So URL, pretty simple, it's make.wordpress.org slash training. So you can change that last word between the slatters to get to each team's blog. And actually, when you first come to the blog, the page will look like this. There's a great welcome box here, which gives you some overview of the team. But you can also hide this box. I visit this site regularly so I have the box closed. So first of all, the blog is where the decisions are made. So on the right here, you'll see we have an email updates subscribe form. You can subscribe to the blog and you can start getting the post in your email just to get an idea of how the decisions are made in the team, what discussions are being had. But I want to highlight three links in particular. So in the top blue menu bar, you'll see we have three links. We have getting started, handbook and faculty members. Now getting started is the link I want you to go to if you're getting started with the training team. So this will take you to the training teams onboarding program. And we'll dive into that just a little bit more in just a moment. But if your first time with the training team you want to start contributing, the best place to go is this getting started link. The second link here is the team's handbook and I'll open this and give us a quick show us what this looks like. So every WordPress team has a handbook which documents the different processes in the team. So this is the training team handbook. And you'll see we have quite an extensive table of contents on the left here. And if you open these, you then get another quite extensive sub menu and then the sub sub menu, there's just a lot of content here. So I don't recommend reading through the handbook just right off the bat. The handbook is more resource to go to once you start contributing and you have different questions. So I want to do this. I wonder how you do that. So for example, an online workshop, how can I facilitate an online workshop? How can I host one? So we have a full section here on online workshops, which talk about how to apply to facilitate kind of plan one, how to schedule one, etc. Or maybe you start to get involved with the team and you want to help us build out a lesson. How do you do that? So we have a full section on how to create a lesson, how to review a lesson, how to publish a lesson, etc. So no need to read through the handbook necessarily, but it's good to keep in mind where it lives. And we also have a search bar here for if and when you contribute, you can search through the handbook here. So that was getting started handbook. And the third link are faculty members. So the faculty program is a unique program only in the training team. So WordPress project has many teams, each team, their contribution methods are a bit different. But for example, if you are part of one of the teams that do a lot of coding, then generally your contribution will be, you come to that team, you open the team's GitHub repository, you find a bug or an issue that is waiting for some code. You'll develop the code on your local environment. You'll push the code up to GitHub. That gets reviewed and then that gets added into the WordPress code base. If you're a developer and you're used to this process, then this one contribution could be completed in about 30 minutes. So these code-based teams is easy for people to come in just their spare time, contribute 30 minutes here and there and still leave an impact. The training team is a little different. For example, we published like five minute tutorial videos. If you have experienced creating content, video content, you'll probably know creating a five minute video takes much longer than just 30 minutes. You have to write a script. You have to get your screen slide presentation ready. You have to record. You didn't have to edit. You have to upload this. You have to subtitle it. There are just so many processes involved in creating a single piece of content. And so while we do have different areas of contribution, people can come and do in their spare time. There are some things that we need people to dedicate a little bit more time to really take to completion. And that's where the faculty program comes in. So the members of the faculty program are people who have said, I am going to dedicate slightly larger chunks of my time to help the training team reach their goals and complete their mission. So there's no time requirement specifically for the faculty program. Some people have just said I can contribute two hours a week. Some people have said I can contribute 20 hours a week. So that time does vary between contributors. But these are people who have said, I support the team. I understand what the vision is. And I will contribute just a little bit more time than the average contributor might to help us get to get our content created and published. So there's a big list of people here. These faculty members, we have a check-in survey yearly. So it's generally a year by year commitment. And I mean, if things come up, people can leave the faculty program. We are accepting new applicants any time throughout the year. And so again, if you're stuck on something, these faculty members are the best people to ask because they have the most experience and knowledge working in the training team. So the faculty members are your go-to people to ask for help if you need, if you get stuck. And the handbook is written documentation about how all the different team processes work. And we also have getting started our onboarding program. And I'm going to sort of walk through the onboarding program now with you in this video to give you an overview of the team. But once again, let me just quickly pause there. Are there any questions so far? Hopefully I haven't lost anyone. How is it going? So far so good. Okay, great. I can answer for everybody. Yeah, no, but thank you, Gwen. Thank you for conducting the presentation. Yep, my pleasure. All right, well, so we have a look at the great big WordPress project and where the training team fits in that. We know what the Learn WordPress website is. We know we're starting to get into the details of how the training team operates in order to maintain that website. So the rest of this time, I'm going to walk us through quickly the onboarding program here. I'm not going to go through all the details, but this will give you a better idea of how we communicate with each other, where you might be able to start with your first contribution and so on. So just let me share this link once more in the Zoom chat. We came to the WordPress training team blog. We clicked on Getting Started and this is the onboarding program. So it starts off, welcome to the training team. And it says, please take a moment to watch the video below. This will introduce the training team's mission, how we operate as a team. And it is the first step in onboarding to the team and making your first contribution. And if you scroll down a bit more, you'll see a familiar face here, who then takes three minutes to give you a quick overview of what the training team does, which I've already covered in this call. Okay, so the training team, we communicate in three locations. We communicate on the team blog, which I introduced to you before. We communicate in an application called Slack and we also communicate on GitHub. So Slack, hopefully people here are familiar with it. It's like a chat application. The WordPress project has been gifted unlimited Slack accounts from the Slack company. So they agree with the WordPress mandate and how we want to contribute to WordPress, the open source, the open web. And so they've provided us Slack accounts, which people can use for free, to communicate with each other. So this is a real-time communication tool. So if you're getting started with the training team and you're going through the onboarding program and you're stuck, then you have a question, you need it answered right away. Then Slack is the place to go to. And then you can ask your question in the training team channel and anybody who's online at that moment will see the notification and they can help you and answer that for you. So Slack is where the real-time communication happens. But in the training team, we make it very clear that Slack is not where decisions are made. So decisions are made on the team blog. So conversations happen in Slack, but decisions are made on the team blog. And the reason for this is you need an account to log into Slack and see the conversation. So although it's free and anybody can create an account, it's still sort of closed behind doors a bit. Whereas the team blog is just a website on the internet. Anybody can comment on it. It is indexed by search engines, so it will be recorded in the internet history forever. So we want to make our decisions as open and public as possible. So while we might have different conversations in Slack, if a decision needs to be made, it will always be taken to a post on the training team blog. And we generally have things open for two weeks. So a post is published with a call for feedback. And then two weeks later, the person who submitted the post will make a final comment and say, thank you for your discussion based on all the input. This is the decision we're going to move forward with. So there's a clear distinction there. Decisions are made on the team blog, and real-time communication happens in Slack. Then the third tool we use is GitHub. Now, GitHub can seem overwhelming. So please give me three minutes to give you a quick overview of GitHub so it doesn't overwhelm you. And I can show you, you don't need to be a developer to use GitHub. So the training team, we have the WordPress slash learn GitHub repository. This is what it looks like. There's a lot of stuff on this screen, which you can mostly disregard. The most important link on this screen is this one that says projects. So I'm going to click into that. The training team, we do a lot of things. We create content. We translate content. We collect feedback from learners to then apply to content. We have topics where new contributors can submit new topics they want to create content for. We have administration. We do have website development, and so there's just a lot going on. And so we use GitHub to organize everything moving in the team into different projects. So you'll see we have seven projects in the training team. The top one, I'll thank you Tracy for sharing the link. The top one here, learn WordPress content development. So this is where content is created. I'll click into that in just a moment, but let's quickly look at the others. This one, learn WordPress content feedback. So if somebody watches a video on YouTube or on the learn WordPress website, and they know this like something might be outdated or there was a typo. If they take an online course and one of the quizzes doesn't work, they can send us feedback and then editors will look at that feedback and apply the changes to the content. So where does that feedback come to? It comes to the learn WordPress content feedback project board. So feedback from learners coming to its own project here. We then have learn WordPress content localization. So this is where our translators track their translation progress. And we then have training team administration. So everything that goes on behind the scenes. We then have learn WordPress website development. So this one is a code based project where people are editing the learn WordPress website code. And when we redesign the website, this is where that's going to happen as well. We also then have learn WordPress topic vetting and another one learning pathways project. So we have all these projects going on here. So let me click into the content development project and just give you a quick look at what that looks like. So GitHub projects are built up from columns. So you'll see we have different columns going down the page here and issues start in the left column and they move through to the right column. So we're in the content development project board at the moment. The first column says ready to create 93. So this means there are 93 topics that have already been vetted which are ready for folks to create. So 93 topics you can create a tutorial for a lesson plan for. So these topics are things you can jump into right away and start creating. Now when you start creating on an issue, you'll say I'd like to take this issue. I'd like to start working on it. And then that moves into the second column drafts in progress. So we can see here we have 57 items at the moment where somebody has said I would like to work on this and the draft is in progress. So now once the content has been created, it is then uploaded to the issue and shared with the team and it moves into the ready for review column. So every piece of content that gets published online is first reviewed by at least three people before it becomes public. And there are a few reasons for this. The first one is it can be quite daunting to publish your own content on the Internet. And so having the reviewers make sure there are people there to check everything is right, no typos, make sure the content is accurate and support you before your content goes out live. And it's also a chance for people to give feedback like maybe you've covered most of the content but there was something important that you overlooked. And so the review stage allowed for folks to give their feedback for you to make the final polishes on your content. So once three reviews have been conducted, it then moves into the preparing to publish stage and this is where we technically upload the video into YouTube and add the captions and different things like that. Just the final stages to publish the content and then once it's published, it moves into the published or closed column. So we simply use GitHub to track the progress of all this content development. As you can see, we have easily over 100 pieces of content in this process. We have 554 closed issues. So 554 things have moved through this process and you can see the different phases you see here, the people who have taken on the content. So these pieces of content have been assigned to them and they are working on that content. So that's how we use GitHub. So going back to the onboarding program, those are the three places the training team communicates. So we make decisions on the team blog, we have real-time communication in Slack, and then the actual project management is done in GitHub. All right. Quick pause. Any questions? So far so good. Thank you, Glen. Same here. Same. Yep. Thank you, Eagle. Okay. So that is where the training team communicates. So then let's get set up. So what the onboarding program will walk you through is creating an account so you can contribute to those three places, the blog, the Slack, and the GitHub. So while the blog is open and public, anybody can read the blog. You need a WordPress.org account to comment on the blog. So the first thing we walk you through is setting up a WordPress.org account. And the WordPress.org account is also used to track your contributions, not just to the training team, but to the whole WordPress, make WordPress project. So every time you make a contribution, that is all recorded in your profile, your WordPress.org account profile. And then you can share that with people. We know sometimes people share this with potential employers. And there's a track record of how they've contributed to this project. So the first account you need is a WordPress.org account. The second one you need is a Making WordPress Slack account. And again, if you click on this link, you'll take you through the steps of making that Slack account for free. And then the third account you need is a GitHub account. And again, there's a link here to Join GitHub. And this then allows you to assign different issues and get home to yourself and contribute there. All right. So that's all the technical stuff in order to get set up and ready to contribute to the training team. Once that's all set up, the next thing the onboarding program walks you through is finding your interest and making your first contribution. So you've probably started to see there are many moving parts in the training team. And we've categorized this into five areas of contribution. So you'll see in this table, we have area of contribution. We've split the training teams different tasks and roles into five areas. The first one is content creator. The second one is content translator. Third one is editor. The fourth one is subject matter experts. And the fifth one is administrator. So going through the top, the main role of the content creator is to create content. So these are the people who write the video script. They make the slides to use in this video. They record the videos, they edit the videos, and then they finally publish the videos. So those are our content creators. Content translators take those English resources and translate them into different languages. Now learn WordPress. We actually publish content in any language. It doesn't have to start in English. So we do have some content creators who create content in non-English languages. But just overall, it's been a minority. Most of the time we are creating English content first and then a group of translators translate that into different languages. So we have a content translator, area of contribution. The next one is editors. Editors have two main roles. The first one is reviewing content before it gets published. So you saw before in the GitHub, we have that ready for review column. They look at the issues in that column, review it, and give the goal sign for it to get published. The other thing editors do is they look at the feedback that comes in from learners and they assess whether the feedback is true. We sometimes get spam. Sometimes the issue is a local issue with that person's computer rather than with the content itself. So the editors sort of assess the feedback and then if there is a valid point there that means changing, they will then apply the change to the published content. So editors review content before it is published and they also edit content after it is published based on feedback we get. Subject mother experts. So subject mother experts are experts of specific topics and they assist content creators in making content. So for example, a content creator doesn't need to know the topic they're creating content for. For example, I'm not a developer, but if I'm a content creator, I could still make developer focused content by working with a subject mother expert who is a developer. So that subject mother expert would give me the resources, which me as a content creator, I would then turn into a video or a lesson plan or an online course. And the subject mother expert would sort of review the content and I do the technical terminating into a content. So subject mother experts work alongside with our content creators to build content. And the second thing subject mother experts do is they vet content topic ideas. So we have a open board where anybody can suggest new topics for content on learn. And so people submit different ideas. And the subject mother experts, because they are very knowledgeable of the different areas of content, they will look at the submitted ideas. First of all, see if it's a valid idea. But then second, they will assign a priority to the idea. So somebody might say, we need a video on low WordPress about the 2024 block thing. And then if we don't, oh, there's my zoom come up. So the subject matter expert will look at that. They'll actually look at the learn website content. Do we already have this content? If not, is it a high priority content? Is a low priority content? So they will vet the content idea and then submit that to the content development project board. So before you saw there was a column, the very first column in the project development project board said ready to create. So all the ideas in that ready to create first went through a vetting process by subject matter experts. So the subject matter experts have said, yes, this is relevant content. We need to create it. And then they send that to the project development content development project board. And then content creators pick that up. They make the content and then editors edit the content. And once it's published, the translators translate the content. So these four roles sort of work together to create a content from start to finish. And the administrator's main purpose is to make sure these four areas are working smoothly together. So me personally, I probably do a lot of administrating stuff. And so what I do is I keep an eye open to the different roles and how their processes are going. Is there something we can put in place to support them? Maybe they maybe something's broken and they need it fixed. Maybe they need special assistance from the WordPress project. And so administrators will pick up on that and support these people in order for them to create content. So those are the five areas of contribution. And you'll see each of these is a separate link. So we have a content creator onboarding, content translator onboarding, editor onboarding, subject matter expert onboarding and an administrator onboarding. So because the training team, we have so many different areas of responsibility. Although the onboarding everybody starts from this page you're seeing right now. It then breaks off into five different pages. So you get to choose which onboarding you'd like to move into. And that's why I'm not going to go into all the details of the onboarding, but hopefully you're starting to get a pretty good idea of how the training team operates. All right. And so we have just a few minutes left. Thank you, Gwen. We have just a few minutes left. So I'm going to quickly go into the content creator onboarding, give you an overview of what that looks like. The others will be similar. And then we'll open it up for final questions. So content creator onboarding. It gives you a bit of an explanation about the role. And then this section here is introducing our faculty content creators. So rewind about half an hour. You'll remember I introduced you to the faculty members in the training team. These are people who have dedicated specific chunks of time to help the team meet its goals. Each of the faculty members are actually part of these five areas of contribution. So we have faculty content creators. We have faculty editors. We have faculty subject matter experts. We have faculty administrators. And we have faculty translators. And so whichever part you choose, if you choose to be content creator, if you choose to be an editor, once you're in that part, you will have a subset of faculty members who are experts in that area of contribution which you can connect with and ask questions. So each onboarding page has a section that introduces you to the faculty members of that area of contribution. So if you come down here, it says, when reaching out to a content creator faculty, you can also mention the act of faculty content creators Slack group in the training channel in Slack. So once you have a Slack account, most of the conversations happen in the training channel. So everybody talks in the training channel. And then you can ping specific people in Slack to get the attention. So if you have a question you need somebody to help you right away, you can ping them individually. But in the training team, we have what's called a Slack group set up. So if you type, this is an example message down here, if you type at faculty content content creators and send this message, this will send a notification to all our faculty members who are registered as content creators. What's good about this is you don't have to know the specific names or accounts of each faculty member. You can just ping this group and then all the faculty content creators are notified and whoever's online can look at your message and help you right away. So we've set this up for each of the five areas of contribution and then it's a way to get people's attention just that much quicker. So I wanted to point this out because if you do start getting involved with the training team, for example, I live in Japan. I'm not online 24 hours. So the best way to get help is to ping the faculty members with these Slack group pings. And then that will give you the assistance you need the quickest. All right. And then the onboarding next walks you through your first contribution. So this first contribution is different for each area of contribution. You'll be asked to do one thing if you're a translator. You'll be asked to do something else. And this is a step-by-step guide into you making your first contribution to the training team. So the goal is after, by the time you've worked through this onboarding program, you would have made your first contribution to the training team or to the WordPress project. You would have left your mark on the WordPress project. These first contributions generally take somewhere between 30 and 60 minutes, depending on what area of contribution you choose. So once you've made your accounts and you've read through this material, you've made your first contribution, but after about an hour or so, you would have contributed to the training team and got a taste of what it feels like to contribute to an open source project. So finally, there's a section to come at your name to our list of contributors. So we have a simple form here you can fill out. This will then notify the faculty administrators so we can know who has completed onboarding, who might need some more assistance to get involved with the team. But basically, it's just a way for you to let us know you're eager, you want to join, and you're ready to take on more. So then finally, we'd like to hear your feedback and then what's next, and so depending on what area of contribution you chose, we have tons of things you can then work on next. So while your first contribution is sort of guided through in the onboarding program, your second contribution and on is more create your own adventure type experience. So if you're a content creator, you can next write a list and plan, or you can facilitate an online workshop, or you can create a tutorial. And each of these links will then take you to that next adventure, your next contribution to WordPress. And then the final link we share in the onboarding program is the training team meeting times. So this will be the last link I'll share with folks. So I'll share this link in the Zoom chat. And this calendar will show the meeting times in your local time zone. So at the moment this says the training team weekly meeting starts at 9 a.m. That's because I'm in Japan, so it's 9 a.m. for me Thursday. But for most of the folks in this online workshop right now, it will probably be Thursday, sorry, Wednesday evening for you. So open this link in your own browser and you'll be able to check the times out there. So these meetings, so the training team weekly meetings, this happened in Black, and so this is the Black channel, the training channel. But once again, decisions aren't made in Black. So Slack is where we have the meetings and we have conversations. But if there is ever anything that needs to have a decision made on it, that is then taken to a blog post, which we can then have asynchronous conversations there as well. So the training team weekly meetings is more a place for you to just get a feel of what's going on right now and the important notices from the WordPress project that he needs to know of. And so it just gives you a pulse check of what the training team is at that moment. We then have two other types of meetings. The second one here, training DevSquad triage session. So this one is more developer-focused if you have a developer background. Each week, the DevSquad takes 13 minutes to go through our GitHub project boards and triage the new issues that came in that week. So just make sure if it's spam, we close it out. If it's relevant, just make sure it's labeled properly. Has it been put into the correct project board? Can they move anything forward? So if you have that developer background, join the team in the Meta Learn Slack channel. And that's a 30-minute meeting each week which you can get involved with as well. And then finally, training team coffee hour. So these coffee hours are very casual video sessions where most of the time we're working with Slack and blog posts, so it's text-based. But these are times each week where we actually have a video session where you can show your face, connect with other contributors, get to know each other, ask your questions in person, and clear things out. Currently, these run at 10 p.m. my time, so I don't attend these, but depending on where you are in the world, you might be able to attend these as well. So these are the different meetings that happen in the training team. And yeah, that's pretty much what I had prepared today. So we started from the big WordPress project, figured out where the training team sits in that, what the training team does, and then we went into some of the details of where we communicate, how we communicate, and how you can now get involved as well. So that was a lot of talking on my part. We have a few minutes left. Are there any questions people have, anything? Maybe I didn't quite answer for you. Eagle, I see you unmuted. Did you have something? I was just looking at your training team meetings on your calendar. They're 5 a.m. on Friday and 11 p.m. for the training dev on Wednesdays. That's like, wow. Yes. So these meeting times are basically decided on where people show the most interest. So for example, the Dev Squad triage session, we did have an American time zone one going at one stage. And I think this is more European time zone. But then the interest in the American time zone sort of winged off a bit. So we cut that. But if people are interested again, we can definitely start these different meetings, especially that triage session up again. And we'll connect faculty members with you to start that up. If you're interested, comment in the Slack channels. Say you'd like to join just the wrong time zone and we can take the conversation from there. Gotcha. So if you're interested in, say, like the web development part, where is that? OK, good question. I don't see any meetings about that. Good question. So the web development, we actually don't have a big focus on. So it's there, but the developers are sort of coming in and doing it based on their experience with other teams. So now that you mention it, that is something we can probably create an onboarding path for developers. Let me share a specific link with you. So under our how-to guides, we have developing loan workers. OK, so let me share this link in the Zoom chat. And this page will walk you through how you can start getting involved with the development part of WordPress. So take a look at this page. And then if you have any questions, you can definitely ask in the training channel. I will say that with that development project board, if you're familiar with GitHub, then basically these are the issues that are open and you can work on. You have some triage issues which you can also take up. We have issues in progress. We have then, for example, PR, something in the review stage and then completed. So if you're familiar with GitHub, you can even just jump right into this GitHub project board and take up an issue and contribute there. No. OK. Yep. Yeah. And I will also make a note that we can probably have a developer focused onboarding program now that you mentioned that. So thank you. No problem. All right. So Nick Diego works on documentation. Where does he fit in? Is he involved with the training at all? So he's more liaison between training and documentation or training and we have a team called Meta which looks after the infrastructure of the WordPress project. So he's not part of the training team, but we do work with him to collaborate with other teams. I think he does online workshops every now and then, though. He does. Oh, yeah. He's very active. He was at the engine before he went over to automatic. So I interacted with him in the build mode group and stuff. Oh, OK. One of the things that I see come up in our help desk a lot is that with the introduction of full site editing, well, back up a step in the general settings for WordPress, the default settings are the homepage is a blog archive from the classic setups. So basically your homepage is Hello World. And then if you want to change that, you go in, you create a homepage and you create a blog, an empty blog page, and then you change your general read settings to a static homepage and then to the blog page. But in full site editing, the trend that everybody seems to be following is that the blog archive page, the blog template is treated differently. It's actually turned into, in some cases, static homepages. And it's very confusing for people getting started. How do I actually go about setting things up? There's not a lot of instruction about the fact, oh, if you really want to create your own homepage, you need to set up a homepage, you need to set up, you know, and change these settings. Everybody just talks about going in and oh, you can change templates, you can change stuff. Of course you can. If you have a lot of experience in that and understanding it, really have a head wrap around the hierarchy of the templates, it's easier to get a grip on. Even for myself and for my peer help desk organizers, getting our head wrapped around what happened with the templates and full site editing took a while. We had to really do some deep discovery to find out what in the world is going on because people would come and ask us questions. It's like, oh yeah, we can fix that. And it's like, oh, we can't. We had to do some really deep digging to find out what was going on in terms of how people, how the new themes were being built. And it's a very confusing thing. And I see a lot of training about oh, here's a site editor. Here's the templates. Here's the page. You can change it. Here's the views. Here's the filters. But not really a lot of practicality about how to actually go about setting up your site. Right. So that's, that's one of the things I've run across. And that's. Yeah. I don't know how to get that part of my life and where that fits into the training because I don't really want to create content. I'm not the most beautiful person or the best speaker. You know, I appreciate you for your feedback. Tracy, did I say you were going to step in with a comment or something? Oh, I was just going to say it. Well, number one, you don't have to be on screen when you create the content. A lot of people on the lessons or the tutorials are all speaking in the background. And you're looking at the screens changing. And I agree with the, especially 2024 when you, when you open it up. It's difficult with the blog. Blog archive page being the homepage. And you don't really notice. It's about three quarters of the way down the page before you actually see the blog archive. All the rest is fixed information. In the template. I agree with that. It can be confusing, especially for someone new. Yeah. I guess what I'm saying is that there really needs to be some sort of like the Ali theme tried to do with an own, an onboarding process. There need to be some sort of onboarding process for new users to, to get their, their site editing going. In a way that's like. I mean, people, you know, the most people that come to us, they've, they've already destroyed their templates. Yeah. And they come to us and ask us to fix it. And it's like, wow, how in the world. And, and I've got like a co co-sponsor or organizer. And he's like, Oh, I always edit everything in the, in the site editor, all my pages. I was like, dude, that's just asking for trouble at this stage. But, you know, things are coming together. Six from five looks a lot better. Yeah. And I mean, you're not the first person I've heard talk about onboarding, like, there definitely needs to be a better onboarding. From the training team's perspective, we, one of the things we're going to be looking at after the loan relaunch is can we get some of our key videos linked in the WordPress dashboard somehow, like onboard, like, so like exactly what you mentioned, that homepage changing that initial setup. If we could have like a link to a loan WordPress video, which is the official WordPress video that walks you through that step, that would be ideal. I know different teams are sort of approaching this from different angles. It's definitely a conversation I've heard. And I think maybe as a training team, for the moment, the best we can do is, for example, if you can just come in and make a video that meets your audience's needs perfectly. And then we can just share that with other people as well. That might be one way. Yep. Setting up or tweaking your WordPress to get started. I don't know. Onboarding is a good word. I know there are a lesson that there are at least one or two lessons in progress on the settings, just the settings page. And all the different sections of that and how to, how to set them up correctly for a new site. Yeah. I mean, because, you know, those are basic things. Anyway, I don't mean to turn this into a, but like I said, short of going, like you just said, create the content myself. I'm not sure how I take all of this energy and how that fits into the piece, because I'm not currently the content creator. It just isn't my forte. This is not the face I want to put out there. Yeah. I like helping people. I don't want to be the YouTube face. Don't lose that passion though of wanting to help people. Oh, I didn't. Yeah. The training team focus right now is the site redesign, but I think there's a lot more we can do to really get our content in the hands of the users after that. So even just to get feedback from you and your ideas and that, I think that would be really great. Yeah. Well, I talked to Laura every Friday. So. Yeah. Perfect. Perfect. And Carolina has asked whether there are specific areas of contribution that are lacking people that she could help out with. Okay. Yep. That's a great question. I would say at the moment we are lacking content creators and administrators. I feel like the content that is getting created is getting reviewed at a good pace. So we need more people to just help us get the content created, especially in preparation for the site relaunch. It's scheduled for July this year. We're working towards that. And also administration. I think we just have like two or three people who are doing the majority of administrative work at the moment. So if we could give assistance there, that would help us. What is administrative work? Okay. Well, for example, each of our tutorial presenters are actually better before they're allowed to record a video. And so when somebody applies to create a video, the administrator will actually go into their, for example, social network history, make sure they haven't done like discriminatory action. Like this is a face and a voice we want to have on the website. And so we have people who are like vetting bags. And then we also have like people who send us feedback about content. And we collect that feedback in GitHub, but not everybody is comfortable using GitHub. And so we have an email account where people send us feedback or send us different things. And so the administrator then takes that into GitHub and anonymizes it, of course, but puts it in GitHub. So then anybody can view it and then work on that piece of feedback. So the administrators sort of have a bit of back-end access to different things to bring the task to the different areas of contribution. Organize an organization. Yeah. Okay. Very good. All right. Well, thank you so much for joining and for your imports and your questions. It was so good to see you all. I also see Gwen did leave us a bit earlier, but she did say send us a thank you message. And then Carolina, great. Thank you for your time and guidance, huge work you are doing. Thank you so much for attending today. And I would love to see you in the training channel. But if you have any questions on that, you can reach me in Slack or even contact me on the meetup.com event page as well. And yeah, I think we'll call all the reps there. Thank you for your time today. Thank you. It was a great presentation. Thank you. All right. Bye.