1 00:00:04,400 --> 00:00:06,800 Hello. How do you see 2 00:00:06,800 --> 00:00:09,760 WordPress integrating with voice 3 00:00:09,760 --> 00:00:12,880 AI and 3D publishing on the web 4 00:00:12,880 --> 00:00:15,920 in the future? 5 00:00:15,920 --> 00:00:17,600 >> Abha, thank you very much for 6 00:00:17,600 --> 00:00:20,320 that question. I haven't thought 7 00:00:20,320 --> 00:00:22,160 too much about voice AI or 3D 8 00:00:22,160 --> 00:00:24,240 publishing, but the good news is 9 00:00:24,240 --> 00:00:25,600 that I don't need to for it to 10 00:00:25,600 --> 00:00:27,360 be possible. WordPress has so 11 00:00:27,360 --> 00:00:29,440 many great APIs. I have seen 12 00:00:29,440 --> 00:00:31,440 demos before of people using 13 00:00:31,440 --> 00:00:32,880 WordPress to power content 14 00:00:32,880 --> 00:00:34,240 embedded in sort of virtual 15 00:00:34,240 --> 00:00:36,480 worlds or things like Oculus, 16 00:00:37,040 --> 00:00:39,360 and I have seen people use 17 00:00:39,360 --> 00:00:41,000 WordPress to build kind of like 18 00:00:41,000 --> 00:00:43,600 -- kind of like a voice menu 19 00:00:43,600 --> 00:00:45,040 system for I believe it was 20 00:00:45,040 --> 00:00:47,200 Alexa. So I know it's possible, 21 00:00:48,480 --> 00:00:50,640 but we're probably a few years 22 00:00:50,640 --> 00:00:52,320 away from that being in core. 23 00:00:52,320 --> 00:00:53,600 And if there's anything that 24 00:00:53,600 --> 00:00:54,880 I've missed that I should check 25 00:00:54,880 --> 00:00:57,840 out, please send it my way. 26 00:00:57,840 --> 00:00:59,600 >> I'm Christina Workman from 27 00:00:59,600 --> 00:01:01,600 Calgary, Canada. I'm a designer, 28 00:01:01,600 --> 00:01:03,440 developer, enduser and 29 00:01:03,440 --> 00:01:05,360 contributor. We saw with the 30 00:01:05,360 --> 00:01:07,680 release of WordPress 5.6 that 31 00:01:07,680 --> 00:01:09,520 over 600 people contributed to 32 00:01:09,520 --> 00:01:11,280 track tickets and GitHub pull 33 00:01:11,280 --> 00:01:12,960 requests, all mentioned by name. 34 00:01:13,520 --> 00:01:14,960 As well as numerous volunteers 35 00:01:14,960 --> 00:01:16,160 contributing in the support 36 00:01:16,160 --> 00:01:18,080 forums and translating to make 37 00:01:18,080 --> 00:01:20,800 5.6 available in 38 languages, 38 00:01:20,800 --> 00:01:22,880 although unnamed. There's no 39 00:01:22,880 --> 00:01:24,320 doubt these volunteers are doing 40 00:01:24,320 --> 00:01:26,800 great work which is supported by 41 00:01:26,800 --> 00:01:28,320 thousands of other contributors 42 00:01:28,320 --> 00:01:30,080 volunteering their time outside 43 00:01:30,080 --> 00:01:31,520 of core releases throughout the 44 00:01:31,520 --> 00:01:33,840 year every year who don't get 45 00:01:33,840 --> 00:01:35,600 any recognition outside of their 46 00:01:35,600 --> 00:01:37,520 inner circles. Publicly 47 00:01:37,520 --> 00:01:38,880 acknowledging the variety of 48 00:01:38,880 --> 00:01:40,880 contributor roles available goes 49 00:01:40,880 --> 00:01:42,560 a long way to increasing our 50 00:01:42,560 --> 00:01:44,080 community's awareness that these 51 00:01:44,080 --> 00:01:45,440 roles exist for them to 52 00:01:45,440 --> 00:01:47,760 participate in. What plans are 53 00:01:47,760 --> 00:01:49,040 there for recognizing 54 00:01:49,040 --> 00:01:50,800 contributions made by those who 55 00:01:50,800 --> 00:01:52,640 contribute to any team 56 00:01:52,640 --> 00:01:54,640 throughout the year, even those 57 00:01:54,640 --> 00:01:56,240 not involved in a core release? 58 00:01:56,880 --> 00:01:57,380 Thank you. 59 00:01:59,240 --> 00:02:01,840 >> Christina, this was an 60 00:02:01,840 --> 00:02:03,520 excellent question, and I do 61 00:02:03,520 --> 00:02:05,680 agree that recognition is a 62 00:02:05,680 --> 00:02:07,200 fantastic way to get more people 63 00:02:07,200 --> 00:02:08,560 contributing to the things that 64 00:02:08,560 --> 00:02:10,880 we're doing. The WordPress 65 00:02:10,880 --> 00:02:12,800 release post and of course the 66 00:02:13,360 --> 00:02:15,280 core itself is probably better 67 00:02:15,280 --> 00:02:17,520 at recognizing core itself and 68 00:02:17,520 --> 00:02:18,800 contributors there than anything 69 00:02:18,800 --> 00:02:22,080 else. One thing we did build to 70 00:02:22,080 --> 00:02:23,600 improve this was the badge 71 00:02:23,600 --> 00:02:25,600 system on profiles. So if you go 72 00:02:25,600 --> 00:02:27,040 to profiles.wordpress.org/Matt, 73 00:02:27,920 --> 00:02:28,800 you'll see there are a number of 74 00:02:28,800 --> 00:02:30,800 badges there at the very top 75 00:02:30,800 --> 00:02:31,840 that show all the different 76 00:02:31,840 --> 00:02:33,680 things that I've done and 77 00:02:33,680 --> 00:02:34,720 contributed to the WordPress 78 00:02:34,720 --> 00:02:36,320 community. I think there might 79 00:02:36,320 --> 00:02:38,720 be a bug there, because it shows 80 00:02:38,720 --> 00:02:40,320 that I am a translation editor 81 00:02:40,320 --> 00:02:42,160 and I am unable to speak any 82 00:02:42,160 --> 00:02:44,800 language besides English. And 83 00:02:44,800 --> 00:02:46,000 even English I struggle with 84 00:02:46,000 --> 00:02:48,560 sometimes, so -- but I noticed 85 00:02:48,560 --> 00:02:49,840 that on these badges, there's no 86 00:02:49,840 --> 00:02:50,960 way to click on them and see all 87 00:02:50,960 --> 00:02:52,000 the other people that have the 88 00:02:52,000 --> 00:02:53,680 same badges. So that could be a 89 00:02:53,680 --> 00:02:56,000 really nice start to having 90 00:02:56,000 --> 00:02:58,000 pages that recognize folks, 91 00:02:58,000 --> 00:02:59,360 particularly folks whose work 92 00:03:00,240 --> 00:03:01,440 isn't just tied to a single 93 00:03:01,440 --> 00:03:05,200 release within WordPress.org and 94 00:03:05,200 --> 00:03:06,080 it could have some sort of 95 00:03:06,080 --> 00:03:08,000 natural decay function so, you 96 00:03:08,000 --> 00:03:08,720 know, if you haven't done 97 00:03:08,720 --> 00:03:10,240 anything for an amount of time, 98 00:03:10,240 --> 00:03:11,440 maybe you drop off the list. 99 00:03:12,160 --> 00:03:13,040 That would be, I think, a very 100 00:03:13,040 --> 00:03:14,640 natural place to start to add it 101 00:03:14,640 --> 00:03:15,520 and we'll look into it. 102 00:03:15,520 --> 00:03:17,040 Excellent suggestion and thank 103 00:03:17,040 --> 00:03:17,840 you very much. 104 00:03:17,840 --> 00:03:19,840 >> Hi, Matt. I'm Courtney 105 00:03:19,840 --> 00:03:20,880 Robertson with the training 106 00:03:20,880 --> 00:03:22,720 team. You recently shared an 107 00:03:22,720 --> 00:03:24,160 article from ZDNet that 108 00:03:24,160 --> 00:03:27,600 indicates an 834% rise in PHP 109 00:03:27,600 --> 00:03:29,840 developer jobs since January of 110 00:03:29,840 --> 00:03:32,560 2020. It's fair to assume that 111 00:03:32,560 --> 00:03:33,840 some of that would be WordPress 112 00:03:33,840 --> 00:03:36,560 developer-related jobs. W3Techs 113 00:03:37,360 --> 00:03:39,200 indicates that WordPress powers 114 00:03:39,200 --> 00:03:41,760 over 39.3% of all websites 115 00:03:41,760 --> 00:03:44,560 online, surpassing 38.5% of 116 00:03:44,560 --> 00:03:46,080 websites that have no content 117 00:03:46,080 --> 00:03:48,560 management system at all. Given 118 00:03:48,560 --> 00:03:50,000 those stats, what role do you 119 00:03:50,000 --> 00:03:51,520 see for employers in the 120 00:03:51,520 --> 00:03:53,840 WordPress.org ecosystem as it 121 00:03:53,840 --> 00:03:54,560 relates to the 122 00:03:54,560 --> 00:03:57,840 learn.wordpress.org website? How 123 00:03:57,840 --> 00:03:59,520 do you think that the learned 124 00:03:59,520 --> 00:04:01,920 platform can address hiring, 125 00:04:01,920 --> 00:04:04,000 skills and ongoing professional 126 00:04:04,000 --> 00:04:04,880 development needs? 127 00:04:06,360 --> 00:04:08,240 >> Thank you, Courtney, for 128 00:04:08,240 --> 00:04:09,760 highlighting those stats, and 129 00:04:09,760 --> 00:04:10,960 also thank you for the awesome 130 00:04:10,960 --> 00:04:12,320 WordPress swag you have in your 131 00:04:12,320 --> 00:04:13,680 background. One cool thing about 132 00:04:13,680 --> 00:04:15,040 this format is it's really neat 133 00:04:15,040 --> 00:04:17,040 to see people where they are, 134 00:04:17,040 --> 00:04:18,080 not just us all being in the 135 00:04:18,080 --> 00:04:20,400 same auditorium. You know, for 136 00:04:20,400 --> 00:04:22,640 Learn, I think the first step is 137 00:04:22,640 --> 00:04:24,480 really just organizing and 138 00:04:24,480 --> 00:04:26,160 getting really high-quality 139 00:04:26,160 --> 00:04:27,840 educational material up there. 140 00:04:28,560 --> 00:04:29,680 The equivalent -- like if you 141 00:04:29,680 --> 00:04:30,960 were going to take a university 142 00:04:30,960 --> 00:04:32,640 course on WordPress. How do we 143 00:04:32,640 --> 00:04:34,880 walk you from just learning the 144 00:04:34,880 --> 00:04:36,480 basics all the way up to being 145 00:04:36,480 --> 00:04:38,400 able to be able to customize and 146 00:04:38,400 --> 00:04:40,080 basically be a WordPress pro, so 147 00:04:40,080 --> 00:04:41,120 you could build sites for other 148 00:04:41,120 --> 00:04:43,360 people and be kind of like an 149 00:04:43,360 --> 00:04:45,840 expert. Down the line, it would 150 00:04:45,840 --> 00:04:48,400 be great if this platform could 151 00:04:48,400 --> 00:04:49,280 have some sort of 152 00:04:49,920 --> 00:04:51,600 self-certification or perhaps 153 00:04:51,600 --> 00:04:53,040 even some sort of administered 154 00:04:53,680 --> 00:04:55,520 certification that could show 155 00:04:55,520 --> 00:04:56,480 people that, you know, you 156 00:04:56,480 --> 00:04:58,480 mastered a certain skill. That 157 00:04:58,480 --> 00:05:00,320 you, you know, went through -- 158 00:05:00,320 --> 00:05:01,760 either you went through lessons 159 00:05:01,760 --> 00:05:02,640 or you didn't need to, but you 160 00:05:02,640 --> 00:05:03,680 were able to, like, take a test 161 00:05:03,680 --> 00:05:05,200 at the end and show that you 162 00:05:05,200 --> 00:05:06,320 were competent in this. It 163 00:05:06,320 --> 00:05:07,600 wouldn't be a perfect system, 164 00:05:07,600 --> 00:05:09,680 but it could be a nice way for 165 00:05:09,680 --> 00:05:11,840 people to learn more about 166 00:05:11,840 --> 00:05:13,600 WordPress and hopefully as they 167 00:05:13,600 --> 00:05:14,720 go through, since WordPress is 168 00:05:14,720 --> 00:05:16,000 open source, improve the 169 00:05:16,000 --> 00:05:18,160 materials as we go through it, 170 00:05:18,160 --> 00:05:19,360 both from the point of view of 171 00:05:19,360 --> 00:05:20,560 making it more intuitive or 172 00:05:20,560 --> 00:05:21,840 easier to understand, and then 173 00:05:21,840 --> 00:05:23,280 also translating, as well. 174 00:05:23,280 --> 00:05:24,640 Because there is huge demand for 175 00:05:24,640 --> 00:05:25,840 WordPress really all over the 176 00:05:25,840 --> 00:05:26,320 world now. 177 00:05:26,320 --> 00:05:28,480 >> Hey, Matt. Dan Maby here from 178 00:05:28,480 --> 00:05:30,640 Big Orange Hearts, a charity 179 00:05:30,640 --> 00:05:31,680 providing well-being and mental 180 00:05:31,680 --> 00:05:32,880 health support for remote 181 00:05:32,880 --> 00:05:34,960 workers. To support our mission, 182 00:05:34,960 --> 00:05:36,400 we deliver events to help reduce 183 00:05:36,400 --> 00:05:38,320 social isolation for those 184 00:05:38,320 --> 00:05:40,720 working remotely. With more than 185 00:05:40,720 --> 00:05:41,840 12,000 attendees through our 186 00:05:41,840 --> 00:05:43,840 virtual event platform built on 187 00:05:43,840 --> 00:05:45,040 open source technologies this 188 00:05:45,040 --> 00:05:47,200 year, I wanted to ask about your 189 00:05:47,200 --> 00:05:48,640 vision for events within the 190 00:05:48,640 --> 00:05:50,080 WordPress community through 191 00:05:50,080 --> 00:05:52,800 2021. As a regular WordCamp and 192 00:05:52,800 --> 00:05:54,880 meetup organizer myself, I also 193 00:05:54,880 --> 00:05:56,480 wanted to ask your thoughts on 194 00:05:56,480 --> 00:05:58,480 responsibility towards safety of 195 00:05:58,480 --> 00:06:01,040 attendees and fellow organizers 196 00:06:01,040 --> 00:06:02,160 as we start to take steps 197 00:06:02,160 --> 00:06:05,040 towards a vaccinated era. And, 198 00:06:05,040 --> 00:06:06,720 finally, with virtual events 199 00:06:06,720 --> 00:06:07,920 offering a great level of 200 00:06:07,920 --> 00:06:10,240 accessibility for attendees, do 201 00:06:10,240 --> 00:06:11,760 you see the potential for a 202 00:06:11,760 --> 00:06:13,200 hybrid approach towards 203 00:06:13,200 --> 00:06:15,600 WordCamps in the future? Thanks 204 00:06:15,600 --> 00:06:16,100 for your time. 205 00:06:18,520 --> 00:06:21,760 >> Hi, Dan. Andrea here. Thanks 206 00:06:21,760 --> 00:06:24,480 for asking this question. It's 207 00:06:24,480 --> 00:06:26,000 been inspirational to watch 208 00:06:26,000 --> 00:06:28,000 WordPress community organizers 209 00:06:28,000 --> 00:06:30,160 rise to the challenges that this 210 00:06:30,160 --> 00:06:31,840 horrible pandemic has brought, 211 00:06:31,840 --> 00:06:34,080 especially since so many of us 212 00:06:34,080 --> 00:06:37,120 love this work because we love 213 00:06:37,120 --> 00:06:39,840 seeing each other in person and 214 00:06:39,840 --> 00:06:42,160 we know how powerful those 215 00:06:42,160 --> 00:06:44,160 face-to-face, in-person 216 00:06:44,160 --> 00:06:46,640 interactions can really be. And 217 00:06:46,640 --> 00:06:48,480 like other WordPressers, I am 218 00:06:48,480 --> 00:06:50,160 really eager to get back to 219 00:06:50,160 --> 00:06:52,160 those in-person events, just as 220 00:06:52,160 --> 00:06:55,120 soon as it's safe. All that 221 00:06:55,120 --> 00:06:56,640 said, and as you point out, 222 00:06:58,000 --> 00:07:00,800 moving all of our events online 223 00:07:00,800 --> 00:07:02,240 has made them much more 224 00:07:02,240 --> 00:07:04,880 accessible, especially to those 225 00:07:04,880 --> 00:07:07,280 who either can't travel or don't 226 00:07:07,280 --> 00:07:09,360 wish to travel to our in-person 227 00:07:09,360 --> 00:07:12,880 events. When I think about our 228 00:07:12,880 --> 00:07:16,880 return to in-person events, I 229 00:07:16,880 --> 00:07:19,200 think that some sort of hybrid 230 00:07:19,200 --> 00:07:21,680 element will be necessary, 231 00:07:21,680 --> 00:07:22,800 especially in those first 232 00:07:22,800 --> 00:07:25,280 stages. But I also know that 233 00:07:25,280 --> 00:07:26,800 hybrid events are much more 234 00:07:26,800 --> 00:07:29,840 expensive, and so yet again 235 00:07:30,480 --> 00:07:31,760 we're gonna be hoping and 236 00:07:31,760 --> 00:07:33,360 looking for WordPressers who 237 00:07:34,480 --> 00:07:36,240 want to take the opportunity to 238 00:07:36,240 --> 00:07:39,440 really look for innovative ways 239 00:07:39,440 --> 00:07:40,880 to make our community events 240 00:07:40,880 --> 00:07:44,800 accessible at scale. I don't 241 00:07:44,800 --> 00:07:47,600 know all the answers here, but I 242 00:07:47,600 --> 00:07:49,120 know that some of the smartest 243 00:07:49,120 --> 00:07:51,280 people -- that I know, at least 244 00:07:51,280 --> 00:07:52,080 -- 245 00:07:52,080 --> 00:07:53,920 are in WordPress, and I'm really 246 00:07:53,920 --> 00:07:57,280 looking forward to work on this 247 00:07:57,280 --> 00:07:58,320 together with the global 248 00:07:58,320 --> 00:08:01,040 community team. I hope that's 249 00:08:01,040 --> 00:08:02,640 helpful. Thanks for all that you 250 00:08:02,640 --> 00:08:03,680 do for WordPress and the 251 00:08:03,680 --> 00:08:05,520 WordPress community. I hope to 252 00:08:05,520 --> 00:08:06,080 see you soon. 253 00:08:06,760 --> 00:08:08,960 >> Hi, Matt. I'm Dave from 254 00:08:08,960 --> 00:08:10,400 Belgium. Almost 15 years 255 00:08:10,400 --> 00:08:11,920 building sites professionally 256 00:08:11,920 --> 00:08:13,520 with ten years on WordPress 257 00:08:13,520 --> 00:08:15,360 websites. Hope you're okay and 258 00:08:15,360 --> 00:08:16,960 Happy Christmas in advance for 259 00:08:16,960 --> 00:08:19,280 everyone listening. Well, 260 00:08:19,280 --> 00:08:20,560 WordPress is in its nature a 261 00:08:20,560 --> 00:08:22,240 very clean, no-overkill-on- 262 00:08:22,240 --> 00:08:24,000 options kind of software, and 263 00:08:24,000 --> 00:08:25,200 thankfully this created our 264 00:08:25,200 --> 00:08:27,360 beloved WordPress ecosystem. It 265 00:08:27,360 --> 00:08:29,040 also created momentum for page 266 00:08:29,040 --> 00:08:30,720 builders like Elementer to arise 267 00:08:30,720 --> 00:08:32,880 with enormous success. And the 268 00:08:32,880 --> 00:08:34,880 reason for that is simple: The 269 00:08:34,880 --> 00:08:36,720 user got all the options. Just 270 00:08:36,720 --> 00:08:38,160 to mention a few to make my 271 00:08:38,160 --> 00:08:39,840 question more specific, I'm 272 00:08:39,840 --> 00:08:41,920 talking about layout, padding, 273 00:08:41,920 --> 00:08:44,160 margin, desktop versus mobile, 274 00:08:44,160 --> 00:08:47,040 and tablet and so on. Now, the 275 00:08:47,040 --> 00:08:48,960 Block Editor is right now also 276 00:08:48,960 --> 00:08:50,640 that kind of no-overkill-on- 277 00:08:50,640 --> 00:08:52,720 options kind of software. Some 278 00:08:52,720 --> 00:08:54,400 like that. I totally understand 279 00:08:54,400 --> 00:08:56,640 that, but some don't. The 280 00:08:56,640 --> 00:08:58,400 question is, how far do you 281 00:08:58,400 --> 00:09:00,880 think the core blocks must go in 282 00:09:00,880 --> 00:09:02,960 those kinds of customization to 283 00:09:02,960 --> 00:09:04,880 please the mass non-tech 284 00:09:04,880 --> 00:09:06,720 audience because if you look 285 00:09:06,720 --> 00:09:08,480 back, honestly, that's what they 286 00:09:08,480 --> 00:09:10,160 want, that's what they choose. 287 00:09:10,160 --> 00:09:11,680 Or would you rather keep that 288 00:09:11,680 --> 00:09:14,080 WordPress simplicity again to 289 00:09:14,080 --> 00:09:15,760 leave the door open for the next 290 00:09:15,760 --> 00:09:17,520 block page builder plug-in to 291 00:09:17,520 --> 00:09:18,020 arise. 292 00:09:18,720 --> 00:09:20,480 So how dependent on a 293 00:09:20,480 --> 00:09:22,720 third-party layout plug-in do 294 00:09:22,720 --> 00:09:24,160 you want the WordPress block 295 00:09:24,160 --> 00:09:26,080 user to be? Thank you. 296 00:09:27,560 --> 00:09:30,320 >> Hello, Dave. You bring up an 297 00:09:30,320 --> 00:09:31,760 interesting point, which is that 298 00:09:31,760 --> 00:09:33,840 we're trying to walk a very fine 299 00:09:33,840 --> 00:09:35,840 line between creating something 300 00:09:35,840 --> 00:09:37,360 which is intuitive and easy to 301 00:09:37,360 --> 00:09:40,320 use, and also providing the 302 00:09:40,320 --> 00:09:41,440 customization that people 303 00:09:41,440 --> 00:09:43,360 clearly want in WordPress. While 304 00:09:43,360 --> 00:09:44,560 also trying to do something 305 00:09:44,560 --> 00:09:46,080 which has never really been done 306 00:09:46,080 --> 00:09:49,120 before, which is provide a "what 307 00:09:49,120 --> 00:09:50,160 you see is what you get" 308 00:09:50,160 --> 00:09:51,840 WYSIWYG-style interface that, 309 00:09:51,840 --> 00:09:53,280 again, is intuitive and easy to 310 00:09:53,280 --> 00:09:55,760 use in lay out, but that also 311 00:09:55,760 --> 00:09:57,520 creates really semantic markup, 312 00:09:58,560 --> 00:10:01,040 structured data, and is fast and 313 00:10:01,040 --> 00:10:01,600 performant. 314 00:10:03,200 --> 00:10:04,080 I don't know if you've seen any 315 00:10:04,080 --> 00:10:05,360 of the comparisons on the web 316 00:10:05,360 --> 00:10:08,320 between WordPress with Gutenberg 317 00:10:08,320 --> 00:10:09,680 versus other page filters or 318 00:10:09,680 --> 00:10:11,600 other proprietary CMSs. That 319 00:10:11,600 --> 00:10:13,280 page building and functionality. 320 00:10:13,280 --> 00:10:14,320 Gutenberg blows them out of the 321 00:10:14,320 --> 00:10:16,160 water. It is really fast, really 322 00:10:16,160 --> 00:10:19,440 clean markup, really lean. This 323 00:10:19,440 --> 00:10:21,760 is taking a little longer to do, 324 00:10:21,760 --> 00:10:23,120 right, to do it right, it's 325 00:10:23,120 --> 00:10:24,080 taking longer, but I believe 326 00:10:24,080 --> 00:10:25,520 it's the right long-term 327 00:10:25,520 --> 00:10:27,280 investment in both the future of 328 00:10:27,280 --> 00:10:28,320 WordPress and the future of the 329 00:10:28,320 --> 00:10:31,440 web. In terms of customization, 330 00:10:31,440 --> 00:10:32,560 I believe there will always be 331 00:10:32,560 --> 00:10:34,480 space for not just one plug-in 332 00:10:34,480 --> 00:10:35,840 but many, many, many plug-ins to 333 00:10:35,840 --> 00:10:38,320 extend Gutenberg. And that is 334 00:10:38,320 --> 00:10:40,400 really the idea, that by -- 335 00:10:40,400 --> 00:10:42,720 where before we had, you know, 336 00:10:42,720 --> 00:10:44,560 lots and lots of different page 337 00:10:44,560 --> 00:10:46,080 builders kind of having their 338 00:10:46,080 --> 00:10:47,200 own data structures, their own 339 00:10:47,200 --> 00:10:49,680 way to do essentially the same 340 00:10:49,680 --> 00:10:51,040 thing from a user point of view, 341 00:10:51,040 --> 00:10:52,160 and themes would have to build 342 00:10:52,160 --> 00:10:53,520 to one, SEO plug-ins would have 343 00:10:53,520 --> 00:10:55,200 to build to each one. We're 344 00:10:55,200 --> 00:10:56,880 trying to provide common rails 345 00:10:56,880 --> 00:11:00,160 or framework that every vision 346 00:11:00,160 --> 00:11:01,680 for how page-building could work 347 00:11:01,680 --> 00:11:03,200 on top of WordPress can leverage 348 00:11:03,200 --> 00:11:03,840 these blocks. 349 00:11:03,840 --> 00:11:05,360 In fact, blocks are even built 350 00:11:05,360 --> 00:11:06,800 so that other CMSs can leverage 351 00:11:06,800 --> 00:11:09,040 them, too. So that is the path 352 00:11:09,040 --> 00:11:09,680 we are on. 353 00:11:10,400 --> 00:11:11,680 It's the way WordPress is going. 354 00:11:11,680 --> 00:11:12,960 I believe it's the future. I 355 00:11:12,960 --> 00:11:14,080 hope that as many people get on 356 00:11:14,080 --> 00:11:15,920 that train as possible, but if 357 00:11:15,920 --> 00:11:17,040 not, I do believe it is 358 00:11:17,040 --> 00:11:17,600 inevitable. 359 00:11:17,600 --> 00:11:19,040 >> Hey, Matt, this is Doc from 360 00:11:19,040 --> 00:11:20,480 "Torque" magazine. I'm wondering 361 00:11:20,480 --> 00:11:22,240 what features for core are you 362 00:11:22,240 --> 00:11:23,840 targeting to make WordPress a 363 00:11:23,840 --> 00:11:25,120 better headless experience in 364 00:11:25,120 --> 00:11:25,840 2021? 365 00:11:26,520 --> 00:11:28,640 >> First, I have to say, I don't 366 00:11:28,640 --> 00:11:29,840 love the term "headless." 367 00:11:29,840 --> 00:11:31,040 I like called it "decoupled 368 00:11:31,040 --> 00:11:32,240 WordPress" because who wants to 369 00:11:32,240 --> 00:11:34,400 be headless? But by and far, the 370 00:11:34,400 --> 00:11:35,520 thing that's been driving the 371 00:11:35,520 --> 00:11:36,960 most improvements to our APIs 372 00:11:37,680 --> 00:11:38,640 has been our first-priority 373 00:11:38,640 --> 00:11:40,160 usage of them. So, with 374 00:11:40,160 --> 00:11:41,760 Gutenberg, built on and using 375 00:11:41,760 --> 00:11:43,200 the REST API, and, of course, 376 00:11:43,200 --> 00:11:45,600 our mobile apps, both Android 377 00:11:45,600 --> 00:11:47,680 and iOS, you know, a million 378 00:11:47,680 --> 00:11:50,000 active users, all running 379 00:11:50,000 --> 00:11:52,880 through the APIs. So that has 380 00:11:52,880 --> 00:11:54,800 helped expose a ton of bugs and 381 00:11:54,800 --> 00:11:56,880 a ton of other areas where we 382 00:11:56,880 --> 00:11:58,720 can improve it. I'm keeping my 383 00:11:58,720 --> 00:12:00,560 eye on the GraphQL plug-in. I 384 00:12:00,560 --> 00:12:01,520 think that that is an 385 00:12:01,520 --> 00:12:04,800 interesting possible next step 386 00:12:04,800 --> 00:12:07,600 after REST to support either as 387 00:12:07,600 --> 00:12:09,520 a more official plug-in, or just 388 00:12:09,520 --> 00:12:10,480 something that we point people 389 00:12:10,480 --> 00:12:11,920 to because it seems to be doing 390 00:12:11,920 --> 00:12:15,120 well. You know, I was actually 391 00:12:15,120 --> 00:12:16,400 -- I don't think that a 392 00:12:16,400 --> 00:12:17,600 decoupled architecture or 393 00:12:17,600 --> 00:12:18,960 "headless" sites are right for 394 00:12:18,960 --> 00:12:21,200 everything. I think they're 395 00:12:21,200 --> 00:12:22,960 right in certain situations, but 396 00:12:23,520 --> 00:12:26,320 as I am quoted with saying, they 397 00:12:26,320 --> 00:12:27,840 are probably a regression for 398 00:12:27,840 --> 00:12:29,120 many of the people adopting 399 00:12:29,120 --> 00:12:30,960 them. I actually had a really 400 00:12:30,960 --> 00:12:32,640 good debate about this at the 401 00:12:32,640 --> 00:12:34,960 Netlifly JAMStack Conference 402 00:12:34,960 --> 00:12:37,040 with Matt Billman, but I guess 403 00:12:37,040 --> 00:12:38,000 it was too good because they 404 00:12:38,000 --> 00:12:39,840 elected not to post it, but 405 00:12:39,840 --> 00:12:41,200 perhaps you can track down a 406 00:12:41,200 --> 00:12:43,360 recording or something, and hear 407 00:12:43,360 --> 00:12:44,640 some more of my thoughts about 408 00:12:45,520 --> 00:12:47,120 decoupled architectures and 409 00:12:47,120 --> 00:12:48,280 WordPress there. 410 00:12:48,280 --> 00:12:50,720 >> Hi, Matt. My name is George 411 00:12:50,720 --> 00:12:52,400 Alger. I've been a WordPress 412 00:12:52,400 --> 00:12:55,600 user since 2007, and I've been 413 00:12:55,600 --> 00:12:57,280 watching State of the Word for a 414 00:12:57,280 --> 00:12:59,440 number of years. My question has 415 00:12:59,440 --> 00:13:02,000 to do with Gutenberg versus page 416 00:13:02,000 --> 00:13:04,400 builders, and more specifically 417 00:13:04,400 --> 00:13:07,360 regarding page load speed. I'm 418 00:13:07,360 --> 00:13:10,480 wondering, as Gutenberg in the 419 00:13:10,480 --> 00:13:12,960 future adds more and more 420 00:13:12,960 --> 00:13:15,760 features, do you anticipate that 421 00:13:15,760 --> 00:13:17,440 the page load speeds for 422 00:13:17,440 --> 00:13:21,280 Gutenberg will also slow down to 423 00:13:21,920 --> 00:13:24,960 support the new features? All 424 00:13:24,960 --> 00:13:26,240 right. Thanks for all you do. 425 00:13:26,240 --> 00:13:26,640 Bye-bye. 426 00:13:26,640 --> 00:13:29,120 >> So, George, my name is Riad 427 00:13:29,120 --> 00:13:30,640 Benguella. I am a developer on 428 00:13:30,640 --> 00:13:32,800 the Gutenberg team. It's an 429 00:13:32,800 --> 00:13:34,240 interesting question you bring 430 00:13:34,240 --> 00:13:36,880 here related to performance. As 431 00:13:36,880 --> 00:13:38,160 you can see with the different 432 00:13:38,160 --> 00:13:40,560 WordPress releases since the 433 00:13:40,560 --> 00:13:42,560 initial release of the core -- 434 00:13:42,560 --> 00:13:44,960 the Block Editor in WordPress, 435 00:13:44,960 --> 00:13:46,400 the performance of the editor 436 00:13:46,400 --> 00:13:49,280 have been improving, even if we 437 00:13:49,280 --> 00:13:51,200 were adding features at the same 438 00:13:51,200 --> 00:13:53,760 time. So, it's definitely a big 439 00:13:53,760 --> 00:13:55,440 priority for us, and for the 440 00:13:55,440 --> 00:13:56,720 front end and the page load 441 00:13:56,720 --> 00:13:58,480 speed, we've been approaching 442 00:13:58,480 --> 00:14:00,320 that in a few different ways. 443 00:14:00,320 --> 00:14:01,520 The first one is the block 444 00:14:01,520 --> 00:14:03,360 markup. We are trying to make 445 00:14:03,360 --> 00:14:05,120 sure the block markup is as 446 00:14:05,120 --> 00:14:08,000 clean as possible, and also the 447 00:14:08,000 --> 00:14:09,040 interesting thing is that 448 00:14:09,040 --> 00:14:10,880 Gutenberg brings semantics to 449 00:14:10,880 --> 00:14:12,240 the content that is being 450 00:14:12,240 --> 00:14:14,320 rendered. So WordPress can know 451 00:14:14,320 --> 00:14:16,080 exactly what blocks are being 452 00:14:16,080 --> 00:14:18,000 rendered, what assets they need, 453 00:14:18,000 --> 00:14:19,920 what CSS, what JavaScripts they 454 00:14:19,920 --> 00:14:22,080 need, and, in fact, recently, we 455 00:14:22,080 --> 00:14:23,360 landed the pull request that 456 00:14:23,360 --> 00:14:25,680 allows us to only load the CSS 457 00:14:25,680 --> 00:14:27,120 of the blocks that are actually 458 00:14:27,120 --> 00:14:28,400 in need in the currently 459 00:14:28,400 --> 00:14:31,120 rendered page, and this opens a 460 00:14:31,120 --> 00:14:32,320 lot of possibilities. For 461 00:14:32,320 --> 00:14:33,520 example, in the future, we may 462 00:14:33,520 --> 00:14:35,280 do the same for JavaScript and 463 00:14:35,280 --> 00:14:39,600 lazy-load blocks. When we expand 464 00:14:39,600 --> 00:14:41,600 that to full site editing where 465 00:14:41,600 --> 00:14:44,160 a theme is basically composed 466 00:14:44,160 --> 00:14:46,400 entirely of blocks, you can 467 00:14:46,400 --> 00:14:48,240 imagine that the CSS and the 468 00:14:48,240 --> 00:14:50,240 JavaScript provided by the teams 469 00:14:50,240 --> 00:14:52,320 themselves won't be as necessary 470 00:14:52,320 --> 00:14:52,880 as today. 471 00:14:53,440 --> 00:14:55,680 So I think we have a big 472 00:14:55,680 --> 00:14:57,520 opportunity here to actually 473 00:14:57,520 --> 00:14:59,440 improve the performance of all 474 00:14:59,440 --> 00:15:01,360 the WordPress websites and not 475 00:15:01,360 --> 00:15:03,360 decrease it as we add features. 476 00:15:03,360 --> 00:15:03,860 Thank you. 477 00:15:04,680 --> 00:15:07,120 >> Hi, Matt. I'm Hitha from 478 00:15:07,120 --> 00:15:09,040 India. I'm a project manager, 479 00:15:09,040 --> 00:15:11,600 mainly working with a group of 480 00:15:11,600 --> 00:15:14,640 WordPress developers. My 481 00:15:14,640 --> 00:15:16,320 question for you today is a 482 00:15:16,320 --> 00:15:21,120 simple one. In the recent 483 00:15:21,120 --> 00:15:23,440 releases, we have a lot of new 484 00:15:23,440 --> 00:15:25,360 features and advancement in 485 00:15:25,360 --> 00:15:28,960 WordPress, but as an end user or 486 00:15:28,960 --> 00:15:31,040 maybe a content manager, have 487 00:15:31,040 --> 00:15:33,440 you ever felt like it would be 488 00:15:33,440 --> 00:15:35,280 good to have a more modern 489 00:15:35,280 --> 00:15:37,360 design for the back end, and if 490 00:15:37,360 --> 00:15:38,880 it would have been good if we 491 00:15:38,880 --> 00:15:41,040 had more customization options 492 00:15:41,040 --> 00:15:42,640 just for the back end? Have you 493 00:15:42,640 --> 00:15:44,680 ever felt so? Thanks. 494 00:15:44,680 --> 00:15:47,280 >> Hello, Hitha. I'm Joen from 495 00:15:47,280 --> 00:15:48,960 Denmark. I worked a little bit 496 00:15:48,960 --> 00:15:50,320 on the Block Editor design. 497 00:15:50,320 --> 00:15:51,760 Thank you for your question. 498 00:15:51,760 --> 00:15:53,440 I'll try to answer it as best I 499 00:15:53,440 --> 00:15:58,000 can. As you suggest, WordPress 500 00:15:58,000 --> 00:15:59,440 has landed many features in 501 00:15:59,440 --> 00:16:01,760 recent releases, but very few 502 00:16:01,760 --> 00:16:03,440 changes to the dashboard 503 00:16:03,440 --> 00:16:05,040 visuals. If you're asking 504 00:16:05,040 --> 00:16:06,480 whether that's gonna change, my 505 00:16:06,480 --> 00:16:08,320 answer is I'd like to see that 506 00:16:08,320 --> 00:16:10,880 very much. One of the challenges 507 00:16:10,880 --> 00:16:12,320 to making that happen is that 508 00:16:12,320 --> 00:16:14,160 the dashboard as it exists has 509 00:16:14,160 --> 00:16:17,120 been customized by a great deal 510 00:16:17,120 --> 00:16:20,160 of plug-ins and developers, and 511 00:16:20,160 --> 00:16:21,920 although it is complicated to 512 00:16:21,920 --> 00:16:24,800 new users, the fact that it's 513 00:16:24,800 --> 00:16:26,720 been unchanged for so long means 514 00:16:26,720 --> 00:16:29,200 that it's familiar to existing 515 00:16:29,200 --> 00:16:32,160 users. That means whatever 516 00:16:32,160 --> 00:16:33,840 changes we make have to be 517 00:16:33,840 --> 00:16:35,600 rolled out carefully and in 518 00:16:35,600 --> 00:16:38,240 small iterations. But my hope is 519 00:16:38,240 --> 00:16:40,400 that over time those iterations 520 00:16:40,400 --> 00:16:43,280 can add up. For example, the 521 00:16:43,280 --> 00:16:44,880 Block Editor, we have a new icon 522 00:16:44,880 --> 00:16:47,280 set and a new set of components, 523 00:16:47,280 --> 00:16:48,960 user interface controls. 524 00:16:50,400 --> 00:16:51,360 Although technically 525 00:16:51,360 --> 00:16:52,640 challenging, if we could roll 526 00:16:52,640 --> 00:16:54,000 those out to the rest of the 527 00:16:54,000 --> 00:16:56,000 dashboard, it would bring a 528 00:16:56,000 --> 00:16:57,280 great deal of improvements to 529 00:16:57,280 --> 00:16:59,680 both accessibility and visual 530 00:16:59,680 --> 00:17:01,600 simplicity. So I'd like to see 531 00:17:01,600 --> 00:17:04,240 that happen. You also ask about 532 00:17:04,240 --> 00:17:06,560 customization options, and the 533 00:17:06,560 --> 00:17:08,400 thing is, WordPress is a lot of 534 00:17:08,400 --> 00:17:10,320 things to a lot of people, and 535 00:17:10,880 --> 00:17:12,720 customization options beyond 536 00:17:12,720 --> 00:17:14,800 color schemes might help tailor 537 00:17:14,800 --> 00:17:17,920 the interface to each group. I 538 00:17:17,920 --> 00:17:19,440 would suggest, though, that the 539 00:17:19,440 --> 00:17:20,880 first step to take would be to 540 00:17:20,880 --> 00:17:23,600 make general user interface 541 00:17:23,600 --> 00:17:25,120 enhancement because that would 542 00:17:25,120 --> 00:17:27,360 benefit everyone, but after 543 00:17:27,360 --> 00:17:29,040 that, absolutely, we could look 544 00:17:29,040 --> 00:17:31,920 at customization options. I hope 545 00:17:31,920 --> 00:17:33,920 that answers your question, and 546 00:17:33,920 --> 00:17:36,000 thank you again for your time. 547 00:17:36,840 --> 00:17:39,760 >> Hey, Matt. Jeroen here from 548 00:17:39,760 --> 00:17:41,680 Belgium. Thank you for taking 549 00:17:41,680 --> 00:17:43,440 the State of the Word online 550 00:17:43,440 --> 00:17:45,600 this year. I'm using WordPress 551 00:17:45,600 --> 00:17:46,960 for all of the websites I 552 00:17:46,960 --> 00:17:48,440 develop with my company Site 553 00:17:48,440 --> 00:17:49,760 Fly, and I'm an active 554 00:17:50,320 --> 00:17:52,000 contributor to the WordPress 555 00:17:52,000 --> 00:17:54,320 project. You mentioned before 556 00:17:54,320 --> 00:17:56,480 that in Phase 4 of the Gutenberg 557 00:17:57,840 --> 00:17:59,840 project, that multilingual 558 00:17:59,840 --> 00:18:01,360 features are coming to WordPress 559 00:18:01,360 --> 00:18:04,160 core. I know this is in the 560 00:18:04,160 --> 00:18:06,080 future, but is there any public 561 00:18:06,080 --> 00:18:07,680 roadmap of all the features and 562 00:18:07,680 --> 00:18:10,000 functionalities we want in 563 00:18:10,000 --> 00:18:14,160 WordPress? And is it going to 564 00:18:14,160 --> 00:18:16,880 include a language fallback into 565 00:18:16,880 --> 00:18:18,400 core so we can configure 566 00:18:18,400 --> 00:18:20,160 multiple locales and the 567 00:18:20,160 --> 00:18:21,600 fallback when a translation is 568 00:18:21,600 --> 00:18:23,280 not on wordpress.org? 569 00:18:24,640 --> 00:18:26,560 Currently as a contributor to 570 00:18:26,560 --> 00:18:28,240 the polyglots team, I find it 571 00:18:28,240 --> 00:18:29,760 very difficult to translate 572 00:18:31,120 --> 00:18:32,320 thousands of plug-ins and 573 00:18:32,320 --> 00:18:35,040 themes, and I would love that 574 00:18:35,040 --> 00:18:37,120 fallback to another locale would 575 00:18:37,120 --> 00:18:38,560 be there before it goes to 576 00:18:38,560 --> 00:18:39,060 English. 577 00:18:41,120 --> 00:18:42,400 Currently, I'm using Preferred 578 00:18:42,400 --> 00:18:45,680 Languages as a plug-in for this, 579 00:18:45,680 --> 00:18:47,040 but it would be very cool if 580 00:18:47,040 --> 00:18:48,560 this would be included in 581 00:18:48,560 --> 00:18:50,240 WordPress core. Thank you for 582 00:18:50,240 --> 00:18:51,320 answering my question. 583 00:18:51,320 --> 00:18:53,760 >> Hello, Jeroen. I'm Matias 584 00:18:53,760 --> 00:18:55,440 Ventura helping lead the 585 00:18:55,440 --> 00:18:56,640 Gutenberg project forwards. 586 00:18:57,280 --> 00:18:58,480 Thank you for your question and 587 00:18:58,480 --> 00:18:59,920 for contributing to the project. 588 00:19:01,280 --> 00:19:03,520 Regarding the roadmap, there is 589 00:19:03,520 --> 00:19:05,360 a public roadmap published in 590 00:19:05,360 --> 00:19:09,600 wordpress.org/about/roadmap that 591 00:19:09,600 --> 00:19:11,200 has sort of like an overview of 592 00:19:11,200 --> 00:19:13,840 the next immediate steps, and it 593 00:19:13,840 --> 00:19:15,600 touches upon the four phases of 594 00:19:15,600 --> 00:19:17,200 Gutenberg as well. And what it 595 00:19:17,200 --> 00:19:18,560 doesn't contain, though, is a 596 00:19:18,560 --> 00:19:20,640 detailed plan on Phase 4 597 00:19:20,640 --> 00:19:22,160 specifically, multilingual, 598 00:19:23,200 --> 00:19:25,200 because it's fairly further 599 00:19:25,200 --> 00:19:26,640 ahead for us and we're in the 600 00:19:26,640 --> 00:19:29,920 thick of Phase 2. However, like, 601 00:19:30,800 --> 00:19:31,920 there has been some 602 00:19:31,920 --> 00:19:33,920 conversations around the 603 00:19:33,920 --> 00:19:36,000 implications of localization 604 00:19:36,000 --> 00:19:37,600 and some of the multilingual 605 00:19:37,600 --> 00:19:39,840 aspects, specifically around 606 00:19:40,480 --> 00:19:42,240 patterns and block themes and 607 00:19:42,240 --> 00:19:43,840 how those could be built in the 608 00:19:43,840 --> 00:19:46,160 Gutenberg repository. Nothing 609 00:19:46,160 --> 00:19:47,920 substantial yet, but if you are 610 00:19:47,920 --> 00:19:48,640 interested in those 611 00:19:48,640 --> 00:19:49,840 conversations, that's a good 612 00:19:49,840 --> 00:19:52,080 place to engage with and start 613 00:19:52,080 --> 00:19:54,960 looking at. But, yeah, like as 614 00:19:54,960 --> 00:19:56,400 we approach -- as we get closer 615 00:19:56,400 --> 00:19:58,240 to Phase 4, we will have a more 616 00:19:58,240 --> 00:19:59,600 detailed overview of what's 617 00:19:59,600 --> 00:20:01,440 needed, what requirements and 618 00:20:01,440 --> 00:20:04,240 what we want to do. Regarding 619 00:20:04,240 --> 00:20:06,000 the other topic about fallback 620 00:20:06,000 --> 00:20:07,920 languages, that's a very good 621 00:20:07,920 --> 00:20:10,000 point. For me, I'm very 622 00:20:10,000 --> 00:20:11,120 sympathetic to that, 623 00:20:11,120 --> 00:20:13,429 specifically because I speak variant, 624 00:20:13,429 --> 00:20:16,307 but of the Voseo variant 625 00:20:16,307 --> 00:20:18,228 That means that in most cases 626 00:20:18,228 --> 00:20:20,825 I would benefit from a fallback to 627 00:20:20,825 --> 00:20:22,518 Spain's Spanish 628 00:20:23,280 --> 00:20:24,560 because there is not much 629 00:20:24,560 --> 00:20:26,210 translations going on for you 630 00:20:26,210 --> 00:20:28,920 I'm not even sure if we have a locale, honestly. 631 00:20:29,550 --> 00:20:31,360 so that's something that could 632 00:20:31,360 --> 00:20:33,290 -- personally, I think it could happen 633 00:20:33,290 --> 00:20:34,631 before Phase 4? 634 00:20:34,631 --> 00:20:36,590 I think it could be, like, 635 00:20:36,590 --> 00:20:38,320 a small step towards 636 00:20:38,320 --> 00:20:40,640 a significantly better experience. 637 00:20:40,640 --> 00:20:42,620 So it might be good to discuss it 638 00:20:42,620 --> 00:20:44,410 before Phase 4. 639 00:20:44,410 --> 00:20:47,040 But in any case, if that happens -- if it 640 00:20:47,040 --> 00:20:49,440 doesn't happen before, it would 641 00:20:49,440 --> 00:20:52,048 surely be a part of the phase 4 642 00:20:52,048 --> 00:20:54,178 conversation. Thank you again 643 00:20:54,178 --> 00:20:56,293 and hope you're doing well. Bye-bye. 644 00:20:56,293 --> 00:20:58,000 >> Hello, everyone. 645 00:20:58,000 --> 00:21:00,317 Good moring, Matt. This is Joe Simpson 646 00:21:00,317 --> 00:21:01,840 in Castilla, California 647 00:21:01,840 --> 00:21:03,680 in the Santa Clarita Valley, 648 00:21:03,680 --> 00:21:05,750 just north of Los Angeles. 649 00:21:05,750 --> 00:21:07,840 I'm the lead organizer for WordCamp 650 00:21:07,840 --> 00:21:09,920 Santa Clarita online and I run 651 00:21:09,920 --> 00:21:12,000 two WordPress meetups in the 652 00:21:12,000 --> 00:21:13,920 area as well. As you can tell, 653 00:21:13,920 --> 00:21:16,640 I'm a big WordPress fan. 654 00:21:16,640 --> 00:21:18,880 I'm a big advocate for accessibility 655 00:21:18,880 --> 00:21:20,560 as well, and I've done quite a 656 00:21:20,560 --> 00:21:23,373 few events this year in that space. 657 00:21:23,373 --> 00:21:26,016 What I wanted to reach out to you today 658 00:21:26,016 --> 00:21:28,178 about was a matter 659 00:21:28,178 --> 00:21:30,339 that's pretty important to me. 660 00:21:30,339 --> 00:21:33,541 When we had our event in the spring, 661 00:21:33,541 --> 00:21:37,520 we had volunteers from Bangladesh, we had 662 00:21:37,520 --> 00:21:39,600 attendees from Europe, from 663 00:21:39,600 --> 00:21:41,280 Africa, volunteers from South 664 00:21:41,280 --> 00:21:44,000 America, and it opened up my 665 00:21:44,000 --> 00:21:47,040 eyes to WordPress as a worldwide 666 00:21:47,040 --> 00:21:49,760 entity and a community that's 667 00:21:49,760 --> 00:21:53,600 global in nature, but my concern 668 00:21:53,600 --> 00:21:55,920 was these online presentations, 669 00:21:55,920 --> 00:21:58,320 these online events, Wordcamps, 670 00:21:58,320 --> 00:21:59,400 workshops, et cetera, 671 00:21:59,400 --> 00:22:01,600 I was really really wondering whether they 672 00:22:01,600 --> 00:22:03,312 could be more accessible. 673 00:22:03,312 --> 00:22:06,480 What is WordPress doing to make its 674 00:22:06,480 --> 00:22:09,360 online presence more accessible 675 00:22:09,360 --> 00:22:11,680 to everyone? I'm really big on 676 00:22:11,680 --> 00:22:13,445 inclusion and diversity, and I would 677 00:22:13,445 --> 00:22:15,490 love to hear what WordPress plans to do 678 00:22:15,490 --> 00:22:17,520 moving forward with online events. 679 00:22:17,520 --> 00:22:19,760 Thank you. Have a great holiday 680 00:22:19,760 --> 00:22:21,280 and a good New Year, everyone. 681 00:22:21,280 --> 00:22:22,388 Take care. 682 00:22:22,920 --> 00:22:25,280 >> Well, first of all, Joe, 683 00:22:25,280 --> 00:22:26,960 thank you so much for your 684 00:22:26,960 --> 00:22:28,960 contributions and leading by 685 00:22:28,960 --> 00:22:31,436 example, which is, well, many would say 686 00:22:31,436 --> 00:22:33,825 the only type of leadership 687 00:22:33,825 --> 00:22:36,240 I do believe that as 688 00:22:36,240 --> 00:22:37,920 anxious as I am to get back to 689 00:22:37,920 --> 00:22:39,920 our in-person events, I do 690 00:22:39,920 --> 00:22:41,520 believe that much like your 691 00:22:41,520 --> 00:22:43,120 experience of hosting a, you 692 00:22:43,120 --> 00:22:45,130 know, a more local WordCamp and 693 00:22:45,130 --> 00:22:47,060 people from all over the world joining, 694 00:22:47,060 --> 00:22:49,170 I think if we can move more and more of 695 00:22:49,170 --> 00:22:51,841 our community engagement to be 696 00:22:51,841 --> 00:22:55,350 really rich and interactive online, 697 00:22:55,350 --> 00:22:57,139 we get the benefits of the metaverse, 698 00:22:57,139 --> 00:22:58,800 right? That people can choose to 699 00:22:58,800 --> 00:23:00,480 represent themselves however 700 00:23:00,480 --> 00:23:04,260 they like or not. They can be treated 701 00:23:04,260 --> 00:23:05,930 for their -- and perceived by their 702 00:23:05,930 --> 00:23:07,708 contributions, their words, 703 00:23:07,708 --> 00:23:08,990 how they participate. 704 00:23:08,990 --> 00:23:10,390 Not necessarily who they are, 705 00:23:10,390 --> 00:23:12,373 where they're from or any of that. 706 00:23:12,373 --> 00:23:15,360 You know, when I first got started 707 00:23:15,360 --> 00:23:17,508 contributing to open source, 708 00:23:17,508 --> 00:23:19,280 I didn't have any of the background 709 00:23:19,280 --> 00:23:21,540 or there wasn't really a community 710 00:23:21,540 --> 00:23:22,800 in Houston where I was 711 00:23:22,800 --> 00:23:25,016 or anything like that, to see. 712 00:23:25,016 --> 00:23:26,716 But I appreciated so much 713 00:23:26,716 --> 00:23:29,459 that people would look at, 714 00:23:29,459 --> 00:23:31,680 for me, my code and say, 715 00:23:31,680 --> 00:23:33,930 okay, this isn't just some young kid 716 00:23:33,930 --> 00:23:36,491 in Houston who is not a real engineer, 717 00:23:36,491 --> 00:23:38,694 They were able to look at it for 718 00:23:38,694 --> 00:23:40,527 its own merits. 719 00:23:40,527 --> 00:23:42,816 And I think that, you know, 720 00:23:42,816 --> 00:23:44,450 almost 20 years later, 721 00:23:44,450 --> 00:23:46,930 we can do so much more 722 00:23:46,930 --> 00:23:48,480 than that in terms of 723 00:23:48,480 --> 00:23:50,560 creating a truly, truly 724 00:23:50,560 --> 00:23:51,996 inclusive community. 725 00:23:51,996 --> 00:23:53,513 The other thing that's really, 726 00:23:53,513 --> 00:23:55,316 really important to me there and that 727 00:23:55,316 --> 00:23:57,326 I do see demonstrated throughout WordPress 728 00:23:57,326 --> 00:23:59,133 but I just want to emphasize it again, 729 00:23:59,133 --> 00:24:01,280 is what you mentioned, that idea of 730 00:24:01,280 --> 00:24:03,280 always being welcoming, always being 731 00:24:03,280 --> 00:24:05,120 kind, always being friendly, 732 00:24:05,120 --> 00:24:06,880 particularly as more folks from 733 00:24:06,880 --> 00:24:08,400 around the world get involved, 734 00:24:08,400 --> 00:24:09,910 it's important to remember that 735 00:24:09,910 --> 00:24:11,969 not everyone's first language is English. 736 00:24:11,969 --> 00:24:14,083 and so there might be communication 737 00:24:14,083 --> 00:24:15,712 barriers or misunderstandings. 738 00:24:15,712 --> 00:24:18,880 And so just -- we have a saying within 739 00:24:18,880 --> 00:24:20,757 Automattic that I think is fantastic 740 00:24:20,757 --> 00:24:22,480 for any sort of distributed work or 741 00:24:22,480 --> 00:24:23,840 collaboration, and it's a 742 00:24:23,840 --> 00:24:25,360 different kind of "API" 743 00:24:25,360 --> 00:24:28,507 It stands for Assume Positive Intent. 744 00:24:28,507 --> 00:24:29,914 Find that if you can -- 745 00:24:29,914 --> 00:24:32,061 this isn't something you can ask of anyone else, 746 00:24:32,061 --> 00:24:33,922 but if you can remind yourself of it, 747 00:24:33,922 --> 00:24:35,891 it allows you to see other people's 748 00:24:35,891 --> 00:24:38,720 interactions through a lens which, 749 00:24:38,720 --> 00:24:40,748 allows you to put your best foot forward 750 00:24:40,748 --> 00:24:42,480 and allows them to 751 00:24:42,480 --> 00:24:44,240 regain their best foot, if they 752 00:24:44,240 --> 00:24:46,349 didn't put it forward, 753 00:24:46,349 --> 00:24:48,570 probably on accident with whatever 754 00:24:48,570 --> 00:24:50,929 interaction or communication it was. 755 00:24:50,929 --> 00:24:53,552 So, I keep all those things in mind. 756 00:24:53,552 --> 00:24:56,177 Just to recap, more and more online. 757 00:24:56,177 --> 00:24:58,531 Again, leaning way more into the 758 00:24:58,531 --> 00:25:00,720 online education, online engagement, 759 00:25:00,720 --> 00:25:03,681 online mentorship, online – 760 00:25:03,681 --> 00:25:05,018 you know, everything. 761 00:25:05,018 --> 00:25:06,760 Which is kind of funny because it is 762 00:25:06,760 --> 00:25:08,744 a little bit back to our roots before we 763 00:25:08,744 --> 00:25:09,640 ever had events 764 00:25:09,640 --> 00:25:11,450 Remembering that great ideas, 765 00:25:11,450 --> 00:25:12,822 great contributions can come 766 00:25:12,822 --> 00:25:14,560 from everywhere and anywhere, 767 00:25:14,560 --> 00:25:16,000 and then making sure 768 00:25:16,000 --> 00:25:18,246 that people regardless of where they are, 769 00:25:18,246 --> 00:25:20,286 the background, the language they speak, 770 00:25:20,286 --> 00:25:21,950 their economic ability, anything, 771 00:25:21,950 --> 00:25:23,260 feel fully included 772 00:25:23,260 --> 00:25:24,570 in the WordPress community. 773 00:25:24,570 --> 00:25:26,018 Everyone has a place here. 774 00:25:26,018 --> 00:25:28,000 We are trying to democratize publishing 775 00:25:28,000 --> 00:25:29,840 and commerce. We are -- and 776 00:25:29,840 --> 00:25:31,864 democratize means it's for everyone. 777 00:25:31,864 --> 00:25:34,870 It's not just for the few, or the elite, 778 00:25:34,870 --> 00:25:35,904 or the technical. 779 00:25:35,904 --> 00:25:36,960 That's our mission. 780 00:25:36,960 --> 00:25:38,679 It's a lifelong mission. 781 00:25:38,679 --> 00:25:39,841 We'll never be perfect, 782 00:25:39,841 --> 00:25:41,520 and I plan to keep working on this 783 00:25:41,520 --> 00:25:43,970 the rest of my life, and I hope that -- 784 00:25:43,970 --> 00:25:46,560 to see you and others alongside 785 00:25:46,560 --> 00:25:47,700 in that mission 786 00:25:47,700 --> 00:25:49,960 for many years and decades to come. 787 00:25:49,960 --> 00:25:53,297 >> Hi, Matt. My name's Laura. 788 00:25:53,297 --> 00:25:55,840 I am a member of the WordPress 789 00:25:55,840 --> 00:25:58,307 community in Montclair, New Jersey, 790 00:25:58,307 --> 00:26:01,549 and I have used WordPress 791 00:26:01,549 --> 00:26:03,446 every day of my life 792 00:26:03,446 --> 00:26:06,482 since January of 2006. 793 00:26:06,482 --> 00:26:10,160 So I'm a really early adopter and 794 00:26:10,160 --> 00:26:12,400 a longtime user. I'm also somebody 795 00:26:12,400 --> 00:26:14,800 who doesn't code. I'm a content 796 00:26:14,800 --> 00:26:18,480 creator, and I love doing that 797 00:26:18,480 --> 00:26:20,320 and getting all kinds of 798 00:26:20,320 --> 00:26:22,160 messages out there in the world. 799 00:26:22,800 --> 00:26:24,480 Primarily I've created content 800 00:26:24,480 --> 00:26:26,640 for non-profits, for 801 00:26:26,640 --> 00:26:28,800 entertainment industry websites. 802 00:26:28,800 --> 00:26:31,255 So I guess my question to you, Matt, is, 803 00:26:31,255 --> 00:26:33,760 when I go to WordCamps, 804 00:26:33,760 --> 00:26:36,919 I frequently don't see a lot of tracks 805 00:26:36,919 --> 00:26:39,980 for fellow content creators like me. 806 00:26:39,980 --> 00:26:43,750 What could you say to the folks who are 807 00:26:43,750 --> 00:26:47,280 running WordPress events, specifically 808 00:26:47,280 --> 00:26:50,472 WordPress meetups and WordCamps, 809 00:26:50,472 --> 00:26:52,256 that might encourage them 810 00:26:52,256 --> 00:26:55,120 to embrace content creators 811 00:26:55,120 --> 00:26:57,280 and think about creating more 812 00:26:57,280 --> 00:27:01,129 tracks for users that were less technical? 813 00:27:01,880 --> 00:27:04,800 >> Hey, Laura. I think this is 814 00:27:04,800 --> 00:27:06,400 an excellent question and one 815 00:27:06,400 --> 00:27:08,370 that's really important to me. 816 00:27:08,370 --> 00:27:11,040 I think that content is the thing 817 00:27:11,040 --> 00:27:14,000 that gives your website power 818 00:27:14,000 --> 00:27:15,680 and meaning. It's wonderful to 819 00:27:15,680 --> 00:27:17,818 have a well-built, well-constructed, 820 00:27:17,818 --> 00:27:19,505 well-designed website, 821 00:27:19,505 --> 00:27:21,170 but if you don't have anything for 822 00:27:21,170 --> 00:27:23,095 your users once they arrive, 823 00:27:23,095 --> 00:27:25,440 I'm not certain that your website is 824 00:27:25,440 --> 00:27:27,524 really doing its best job for you. 825 00:27:27,524 --> 00:27:30,960 And so to encourage event organizers 826 00:27:30,960 --> 00:27:33,360 to embrace content creators and 827 00:27:33,360 --> 00:27:35,440 make sure that we have provided 828 00:27:35,440 --> 00:27:39,026 content for them to up-level their skills, 829 00:27:39,026 --> 00:27:41,050 I think the thing that's most important to 830 00:27:41,050 --> 00:27:42,710 remember is that writing for the 831 00:27:42,710 --> 00:27:44,880 internet is a specific and 832 00:27:44,880 --> 00:27:46,380 different skill. 833 00:27:46,380 --> 00:27:49,920 It's not the same as technical writing, 834 00:27:49,920 --> 00:27:52,090 and it's not the same as writing prose. 835 00:27:52,090 --> 00:27:54,880 So when we want to have 836 00:27:54,880 --> 00:27:56,880 very good websites that are 837 00:27:56,880 --> 00:27:58,720 engaging to our audiences but 838 00:27:58,720 --> 00:28:00,316 still get the point across, 839 00:28:00,316 --> 00:28:02,320 I think the only way to do it is 840 00:28:02,320 --> 00:28:04,219 with excellent content, no matter 841 00:28:04,219 --> 00:28:05,440 how that looks for you, 842 00:28:05,440 --> 00:28:07,120 and the best way for us to help 843 00:28:07,120 --> 00:28:08,720 WordPressers do that is to 844 00:28:08,720 --> 00:28:10,960 provide training through our 845 00:28:10,960 --> 00:28:13,952 WordCamps, meetups, et cetera. 846 00:28:13,952 --> 00:28:15,576 >> Hi, Matt. I'm Lax here. 847 00:28:15,576 --> 00:28:19,840 Using WordPress more than ten years. 848 00:28:19,840 --> 00:28:24,010 And congrats for 849 00:28:24,010 --> 00:28:26,790 growing up to 40% of the web. 850 00:28:26,790 --> 00:28:27,680 That's nice. 851 00:28:27,680 --> 00:28:31,139 So my question for you today is, 852 00:28:31,139 --> 00:28:35,040 do you have any plans to optimize 853 00:28:35,040 --> 00:28:37,392 WordPress performance? 854 00:28:37,392 --> 00:28:39,324 I mean the self-hosted WordPress. 855 00:28:39,324 --> 00:28:40,380 it's like, you know, 856 00:28:40,380 --> 00:28:42,857 we have Jetpack, we have caching plugins, 857 00:28:42,857 --> 00:28:45,513 but I found not only me, 858 00:28:45,513 --> 00:28:47,840 my clients, and I see 859 00:28:47,840 --> 00:28:49,520 bloggers and everyone struggle 860 00:28:49,520 --> 00:28:51,310 with the performance, 861 00:28:51,310 --> 00:28:55,440 and also like optimizing the database 862 00:28:55,440 --> 00:28:58,640 queries -- like, to get a simple 863 00:28:58,640 --> 00:29:00,560 tag or category, we are running 864 00:29:00,560 --> 00:29:03,840 too much of subqueries, right? 865 00:29:03,840 --> 00:29:06,720 I'm sure you are a programmer 866 00:29:06,720 --> 00:29:08,960 yourself, so you might have some 867 00:29:08,960 --> 00:29:11,840 plans for the future. And good 868 00:29:11,840 --> 00:29:14,640 luck with our motto, like 869 00:29:14,640 --> 00:29:16,480 democratizing the web. Thank 870 00:29:16,480 --> 00:29:16,980 you. 871 00:29:17,320 --> 00:29:19,920 >> Howdy, Lax. You hit on one of 872 00:29:19,920 --> 00:29:21,040 my favorite topics, which is 873 00:29:21,040 --> 00:29:22,400 performance. I was really 874 00:29:22,400 --> 00:29:23,520 excited that we were able to get 875 00:29:23,520 --> 00:29:24,800 some performance improvements 876 00:29:24,800 --> 00:29:27,040 into WordPress 5.4, as I talked 877 00:29:27,040 --> 00:29:29,520 about in the talk, but there's 878 00:29:29,520 --> 00:29:30,480 always more to do. That's the 879 00:29:30,480 --> 00:29:31,120 beautiful thing about 880 00:29:31,120 --> 00:29:32,320 performance, is it can always be 881 00:29:32,320 --> 00:29:34,800 better. For the issues that you 882 00:29:34,800 --> 00:29:36,720 describe, I would encourage you 883 00:29:36,720 --> 00:29:38,640 to perhaps check out a different 884 00:29:38,640 --> 00:29:40,960 web post. If you're running into 885 00:29:40,960 --> 00:29:42,160 that frequent of performance 886 00:29:42,160 --> 00:29:43,600 issues, there might be something 887 00:29:43,600 --> 00:29:44,960 where, you know, they have you 888 00:29:44,960 --> 00:29:46,080 on a server with too many other 889 00:29:46,080 --> 00:29:49,120 clients or they don't have SSDs 890 00:29:49,120 --> 00:29:50,240 in the servers or whatever it 891 00:29:50,240 --> 00:29:53,120 is. But any modern performant 892 00:29:53,120 --> 00:29:54,720 WordPress web post, primarily 893 00:29:54,720 --> 00:29:56,000 the ones we recommend on 894 00:29:56,000 --> 00:29:59,360 wordpress.org can really handle 895 00:29:59,360 --> 00:30:01,360 a ton of traffic to even an 896 00:30:01,360 --> 00:30:03,440 un-cached, unconfigured site. 897 00:30:04,480 --> 00:30:06,320 That's always great. In terms of 898 00:30:06,320 --> 00:30:07,600 things in core that we could do 899 00:30:07,600 --> 00:30:10,400 to make it better, our queries, 900 00:30:10,400 --> 00:30:11,600 I do believe they're pretty 901 00:30:11,600 --> 00:30:12,960 optimized. They run in a lot of 902 00:30:12,960 --> 00:30:14,640 places, but who knows, maybe a 903 00:30:14,640 --> 00:30:16,000 new future got introduced, maybe 904 00:30:16,000 --> 00:30:17,440 something regressed. So, 905 00:30:17,440 --> 00:30:18,800 please, if there is something 906 00:30:18,800 --> 00:30:20,960 out there that you have noticed, 907 00:30:21,760 --> 00:30:24,320 either open a track ticket or, 908 00:30:24,320 --> 00:30:25,520 you know, share it with someone 909 00:30:25,520 --> 00:30:27,200 or if you, you know, debugging 910 00:30:27,200 --> 00:30:28,160 queries is actually one of the 911 00:30:28,160 --> 00:30:29,840 ways I learned the most about 912 00:30:29,840 --> 00:30:31,200 programming and engineering, 913 00:30:31,200 --> 00:30:32,480 just spending hours and hours 914 00:30:32,480 --> 00:30:34,320 inside the mySQL command line 915 00:30:34,320 --> 00:30:37,520 was -- was actually an amazing 916 00:30:37,520 --> 00:30:38,880 sort of way I developed as a 917 00:30:38,880 --> 00:30:40,160 developer and progressed as a 918 00:30:40,160 --> 00:30:41,760 developer. So it might be 919 00:30:41,760 --> 00:30:43,120 something -- you can discover 920 00:30:43,120 --> 00:30:44,640 something new within WordPress 921 00:30:44,640 --> 00:30:46,960 that then could save millions 922 00:30:46,960 --> 00:30:49,040 and millions of server hours 923 00:30:49,040 --> 00:30:51,680 someplace. So, let me know what 924 00:30:51,680 --> 00:30:54,200 you find or let me know if that 925 00:30:54,200 --> 00:30:55,520 -- if you make a ticket there. 926 00:30:55,520 --> 00:30:56,560 I'll make sure to bump it with 927 00:30:56,560 --> 00:30:58,240 the developers and that it gets 928 00:30:58,240 --> 00:30:59,040 the proper attention. 929 00:31:00,040 --> 00:31:02,480 >> 2020 brought new and 930 00:31:02,480 --> 00:31:04,480 unexpected challenges, and I'm 931 00:31:04,480 --> 00:31:05,680 proud to be a part of a 932 00:31:05,680 --> 00:31:07,200 community like WordPress, 933 00:31:07,200 --> 00:31:09,120 willing to step up, act quickly 934 00:31:09,120 --> 00:31:10,960 and offer solutions in times of 935 00:31:10,960 --> 00:31:12,880 need. Which emerging web 936 00:31:12,880 --> 00:31:14,160 technologies are you most 937 00:31:14,160 --> 00:31:17,120 interested in following in 2021 938 00:31:17,120 --> 00:31:18,480 and how would you like to see 939 00:31:18,480 --> 00:31:20,560 groups like MSP Media within the 940 00:31:20,560 --> 00:31:23,280 WordPress ecosystem innovating 941 00:31:23,280 --> 00:31:25,040 and solution-building using that 942 00:31:25,040 --> 00:31:25,760 technology? 943 00:31:26,600 --> 00:31:29,360 >> Hi, Meg. First of all, 944 00:31:29,360 --> 00:31:30,560 congratulations for getting 945 00:31:30,560 --> 00:31:31,520 SchoolListIt in the Call for 946 00:31:31,520 --> 00:31:33,520 Code Top Five. I believe the 947 00:31:34,240 --> 00:31:35,920 WordPress power tool to make it 948 00:31:35,920 --> 00:31:37,360 the furthest. I know that wasn't 949 00:31:37,360 --> 00:31:38,720 easy, so congratulations on 950 00:31:38,720 --> 00:31:40,960 that. In terms of emerging 951 00:31:40,960 --> 00:31:44,160 technologies, more broadly, I'm 952 00:31:44,160 --> 00:31:45,920 excited that 2020 looks like 953 00:31:45,920 --> 00:31:48,480 it's a year when more mainstream 954 00:31:48,480 --> 00:31:51,680 adoption of cryptocurrencies is 955 00:31:51,680 --> 00:31:53,680 really coming to bear, and that, 956 00:31:53,680 --> 00:31:55,120 to me, you know, as someone who 957 00:31:55,120 --> 00:31:56,480 is a big supporter of open 958 00:31:56,480 --> 00:31:58,640 source and cryptocurrency is 959 00:31:58,640 --> 00:32:00,000 kind of like open source applied 960 00:32:00,000 --> 00:32:01,280 to money, the finance system. 961 00:32:02,480 --> 00:32:04,000 Excited about that. Still very, 962 00:32:04,000 --> 00:32:06,080 very early days. Probably, like, 963 00:32:06,080 --> 00:32:07,360 you know, we're 10 years into 964 00:32:07,360 --> 00:32:08,080 something that's going to take 965 00:32:08,080 --> 00:32:10,640 30 years to happen, but it's 966 00:32:10,640 --> 00:32:13,120 exciting to see steps. Closer to 967 00:32:13,120 --> 00:32:16,240 home in the WordPress world, the 968 00:32:16,240 --> 00:32:17,520 most emerging technologies -- 969 00:32:17,520 --> 00:32:18,560 not new, but they'll be new to 970 00:32:18,560 --> 00:32:20,080 us when we adopt it for Phase 3 971 00:32:20,080 --> 00:32:22,160 of Gutenberg will be Web RTC, 972 00:32:22,160 --> 00:32:23,920 which is essentially like a way 973 00:32:23,920 --> 00:32:25,440 for browsers to connect to each 974 00:32:25,440 --> 00:32:26,960 other in a peer-to-peer fashion 975 00:32:26,960 --> 00:32:28,080 that we can use for real-time 976 00:32:28,080 --> 00:32:29,520 communication, so, for example, 977 00:32:29,520 --> 00:32:31,280 the real-time co-editing that we 978 00:32:31,280 --> 00:32:33,120 want to put into Gutenberg, and 979 00:32:33,120 --> 00:32:33,920 we want to do it without a 980 00:32:33,920 --> 00:32:35,920 centralized server so that, you 981 00:32:35,920 --> 00:32:37,040 know, clients will be able to 982 00:32:37,040 --> 00:32:38,400 connect to each other directly. 983 00:32:40,080 --> 00:32:42,720 A little simpler, and I guess 984 00:32:42,720 --> 00:32:43,440 don't know if you'd call it 985 00:32:43,440 --> 00:32:44,800 emerging, but it's something we 986 00:32:44,800 --> 00:32:46,000 need to do a lot better at, is 987 00:32:46,000 --> 00:32:48,160 native development. So both the 988 00:32:48,160 --> 00:32:50,240 mobile apps on iOS and Android 989 00:32:50,240 --> 00:32:51,600 and native desktop apps for 990 00:32:51,600 --> 00:32:54,240 WordPress, I think have a lot of 991 00:32:54,240 --> 00:32:56,160 potential for just creating a 992 00:32:56,160 --> 00:32:58,720 really slick, highly integrated, 993 00:32:58,720 --> 00:33:01,360 ultra-fast application-like 994 00:33:01,360 --> 00:33:03,120 interface for WordPress. We've 995 00:33:03,120 --> 00:33:05,600 got the APIs for it now. We've 996 00:33:05,600 --> 00:33:08,400 got some good starts, including 997 00:33:08,400 --> 00:33:09,360 some of the code that's based on 998 00:33:09,360 --> 00:33:10,320 Calypso, which is the 999 00:33:10,320 --> 00:33:12,160 open-source React framework that 1000 00:33:12,160 --> 00:33:13,920 runs with WordPress.com. So 1001 00:33:13,920 --> 00:33:14,960 there is some good stuff there, 1002 00:33:14,960 --> 00:33:16,880 but I would like to see a lot 1003 00:33:16,880 --> 00:33:18,160 more, so, thank you for your 1004 00:33:18,160 --> 00:33:18,840 question. 1005 00:33:18,840 --> 00:33:21,040 >> Hi, Matt. I'm Michelle 1006 00:33:21,040 --> 00:33:22,240 Frechette, Head of Customer 1007 00:33:22,240 --> 00:33:24,480 Success at GiveWP, volunteer for 1008 00:33:24,480 --> 00:33:26,080 WordPress and Big Orange Heart, 1009 00:33:26,080 --> 00:33:28,640 and podcaster at WP Coffee Talk. 1010 00:33:28,640 --> 00:33:29,600 We've seen the WordPress 1011 00:33:29,600 --> 00:33:30,720 community grow and morph over 1012 00:33:30,720 --> 00:33:32,400 the years and it's been amazing. 1013 00:33:32,400 --> 00:33:33,840 This year changed a lot of the 1014 00:33:33,840 --> 00:33:35,280 way the community meets and 1015 00:33:35,280 --> 00:33:37,280 interacts due to the pandemic. 1016 00:33:37,280 --> 00:33:38,000 Some of it has been 1017 00:33:38,000 --> 00:33:39,360 heartbreaking, like not meeting 1018 00:33:39,360 --> 00:33:41,040 in person, but so much good has 1019 00:33:41,040 --> 00:33:42,320 come from it, too, like people 1020 00:33:42,320 --> 00:33:43,600 connecting from outside of their 1021 00:33:43,600 --> 00:33:45,120 areas on meet-ups, online 1022 00:33:45,120 --> 00:33:47,280 conferences and more. My 1023 00:33:47,280 --> 00:33:49,040 question is, what do you see for 1024 00:33:49,040 --> 00:33:50,080 the future of the WordPress 1025 00:33:50,080 --> 00:33:51,840 community as we move forward in 1026 00:33:51,840 --> 00:33:53,680 still uncertain times? What 1027 00:33:53,680 --> 00:33:55,040 initiatives should we be looking 1028 00:33:55,040 --> 00:33:56,560 forward to and what kind of 1029 00:33:56,560 --> 00:33:58,160 support can we expect for our 1030 00:33:58,160 --> 00:33:59,680 communities? Thanks for 1031 00:33:59,680 --> 00:34:00,880 providing the online State of 1032 00:34:00,880 --> 00:34:02,320 the Word and an opportunity to 1033 00:34:02,320 --> 00:34:03,520 contribute with questions. 1034 00:34:04,440 --> 00:34:07,280 >> Hi, Michelle. Thanks for 1035 00:34:07,280 --> 00:34:08,880 taking time to send in a 1036 00:34:08,880 --> 00:34:10,960 question. Andrea Middleton here. 1037 00:34:12,720 --> 00:34:14,800 Gosh, the changes that we have 1038 00:34:14,800 --> 00:34:16,320 weathered this year have been 1039 00:34:16,320 --> 00:34:19,680 immense, haven't they? I agree 1040 00:34:19,680 --> 00:34:21,760 with both the heartbreak and the 1041 00:34:21,760 --> 00:34:23,120 unexpected benefits that you 1042 00:34:23,120 --> 00:34:25,520 pointed out. When I think about 1043 00:34:25,520 --> 00:34:26,800 what the future holds for of the 1044 00:34:26,800 --> 00:34:28,640 WordPress community, though, 1045 00:34:28,640 --> 00:34:30,560 especially as we move out of 1046 00:34:30,560 --> 00:34:33,120 2020, but potentially into more 1047 00:34:33,120 --> 00:34:35,200 uncertainty, I'm really 1048 00:34:35,200 --> 00:34:37,680 optimistic. I know that 1049 00:34:37,680 --> 00:34:39,280 WordPress enthusiasts are 1050 00:34:39,280 --> 00:34:41,040 incredibly resourceful and 1051 00:34:41,040 --> 00:34:42,400 resilient in the face of 1052 00:34:42,400 --> 00:34:44,560 adversity, as we've proven this 1053 00:34:44,560 --> 00:34:46,880 year in many ways. The 1054 00:34:46,880 --> 00:34:48,400 initiative I'm most excited 1055 00:34:48,400 --> 00:34:50,800 about moving into 2021 is the 1056 00:34:50,800 --> 00:34:53,680 Learn WordPress platform, which 1057 00:34:53,680 --> 00:34:55,280 formally launched this week. 1058 00:34:56,080 --> 00:34:57,920 This on-demand WordPress 1059 00:34:57,920 --> 00:34:59,520 training platform has the 1060 00:34:59,520 --> 00:35:02,560 potential to build more bridges 1061 00:35:02,560 --> 00:35:04,880 and paths to WordPress and 1062 00:35:04,880 --> 00:35:07,040 success in WordPress than we've 1063 00:35:07,040 --> 00:35:09,680 ever seen at a time when more 1064 00:35:09,680 --> 00:35:12,640 people than ever are looking to 1065 00:35:12,640 --> 00:35:14,560 move their businesses online or 1066 00:35:14,560 --> 00:35:16,320 shift careers and become 1067 00:35:16,320 --> 00:35:18,960 WordPress professionals. I hope 1068 00:35:18,960 --> 00:35:20,800 to see a great deal of support 1069 00:35:20,800 --> 00:35:22,080 for this effort from 1070 00:35:22,080 --> 00:35:23,840 WordPress-based businesses as 1071 00:35:23,840 --> 00:35:26,160 well as individual contributors 1072 00:35:26,160 --> 00:35:28,320 who want to help others to help 1073 00:35:28,320 --> 00:35:30,880 WordPress as they themselves 1074 00:35:30,880 --> 00:35:34,000 have been helped. The support we 1075 00:35:34,000 --> 00:35:36,000 in WordPress provide to each 1076 00:35:36,000 --> 00:35:39,920 other is all about how small 1077 00:35:39,920 --> 00:35:43,680 kindnesses build into great and 1078 00:35:43,680 --> 00:35:45,360 interdependent, powerful 1079 00:35:45,360 --> 00:35:47,280 organizations. And I don't see 1080 00:35:47,280 --> 00:35:48,880 that changing any time soon. 1081 00:35:49,840 --> 00:35:51,120 Thanks so much for asking. 1082 00:35:51,680 --> 00:35:52,400 Talk to you later. 1083 00:35:54,600 --> 00:35:57,520 >> Hello. I'm Milana, a 1084 00:35:57,520 --> 00:35:59,120 freelance WordPress developer 1085 00:35:59,120 --> 00:36:01,840 based in Serbia and also an 1086 00:36:01,840 --> 00:36:03,440 active member of the 1087 00:36:03,440 --> 00:36:05,200 documentation team, and that is 1088 00:36:05,200 --> 00:36:07,120 the subject of my question 1089 00:36:07,120 --> 00:36:11,120 today. So as I see it, there are 1090 00:36:11,120 --> 00:36:13,120 two major problems which are not 1091 00:36:13,120 --> 00:36:14,720 unique only to the documentation 1092 00:36:14,720 --> 00:36:16,240 team. All teams seem to be 1093 00:36:16,240 --> 00:36:18,960 suffering from same conditions. 1094 00:36:18,960 --> 00:36:21,040 So the first one is we are 1095 00:36:21,040 --> 00:36:23,520 heavily understaffed. We don't 1096 00:36:23,520 --> 00:36:26,160 have enough active contributors 1097 00:36:26,160 --> 00:36:28,160 to cover all documentation 1098 00:36:28,160 --> 00:36:31,200 areas, and the second one is we 1099 00:36:31,200 --> 00:36:34,400 don't collaborate enough or at 1100 00:36:34,400 --> 00:36:36,720 all with other teams. And this 1101 00:36:36,720 --> 00:36:38,880 goes that far that sometimes we 1102 00:36:38,880 --> 00:36:40,080 don't even know who is the 1103 00:36:40,080 --> 00:36:42,080 person doing documentation for 1104 00:36:42,080 --> 00:36:44,080 release team, you know, the dev 1105 00:36:44,080 --> 00:36:46,800 notes. Also, there was this huge 1106 00:36:46,800 --> 00:36:49,680 gap between Gutenberg and the 1107 00:36:49,680 --> 00:36:51,280 documentation team and it's 1108 00:36:51,280 --> 00:36:52,960 getting bridged this year, but 1109 00:36:54,080 --> 00:36:55,680 it shouldn't even happen with 1110 00:36:55,680 --> 00:36:58,240 such a project as Gutenberg is. 1111 00:36:58,240 --> 00:37:00,480 And I'm not saying that anyone 1112 00:37:00,480 --> 00:37:02,880 here is doing anything wrong. We 1113 00:37:02,880 --> 00:37:05,360 all do as much as we can. I'm 1114 00:37:05,360 --> 00:37:08,560 just stating how it is. So, my 1115 00:37:08,560 --> 00:37:12,320 question is, how can we, as 1116 00:37:12,320 --> 00:37:15,520 global community, recognize this 1117 00:37:15,520 --> 00:37:18,720 need to connect teams, to work 1118 00:37:18,720 --> 00:37:21,840 more closely with each other? In 1119 00:37:21,840 --> 00:37:23,920 documentation team, we are 1120 00:37:23,920 --> 00:37:26,800 working right now on two big 1121 00:37:26,800 --> 00:37:28,960 projects, external linking 1122 00:37:28,960 --> 00:37:31,120 policy and documentation style 1123 00:37:31,120 --> 00:37:33,520 guide. Now, these will have 1124 00:37:33,520 --> 00:37:36,240 impact beyond documentation 1125 00:37:36,240 --> 00:37:39,280 team, and I'm not even sure how 1126 00:37:39,280 --> 00:37:40,720 many people are aware of the 1127 00:37:40,720 --> 00:37:42,880 fact that we are doing it. So, 1128 00:37:44,800 --> 00:37:46,720 from my perspective, WordPress 1129 00:37:46,720 --> 00:37:48,480 as a project is getting more 1130 00:37:48,480 --> 00:37:51,120 complex, and the way we were 1131 00:37:51,120 --> 00:37:53,040 doing things in the past and the 1132 00:37:53,040 --> 00:37:54,720 way we are doing things right 1133 00:37:54,720 --> 00:37:57,920 now is not sufficient anymore. 1134 00:37:58,800 --> 00:38:01,280 So, I guess it comes down to 1135 00:38:02,000 --> 00:38:04,560 rethinking what is the role of 1136 00:38:05,360 --> 00:38:06,880 making teams in WordPress 1137 00:38:06,880 --> 00:38:07,360 project. 1138 00:38:07,360 --> 00:38:11,600 [ Sound effect ] And how can we improve our 1139 00:38:11,600 --> 00:38:14,720 activities to make our work more 1140 00:38:14,720 --> 00:38:18,000 efficient in this situation that 1141 00:38:18,000 --> 00:38:19,600 we are all in, that we don't 1142 00:38:19,600 --> 00:38:21,680 have enough people and we don't 1143 00:38:21,680 --> 00:38:23,120 communicate. We need to 1144 00:38:23,120 --> 00:38:25,360 communicate more. So what is 1145 00:38:25,360 --> 00:38:28,240 your opinion on that? Thank you. 1146 00:38:29,720 --> 00:38:32,240 >> Hey, Milana, it sounds like 1147 00:38:32,240 --> 00:38:34,400 you have two big questions, and 1148 00:38:34,400 --> 00:38:36,080 I have two big thoughts about 1149 00:38:36,080 --> 00:38:38,320 them. Firstly, on the question 1150 00:38:38,320 --> 00:38:40,960 of recognizing how connected we 1151 00:38:40,960 --> 00:38:43,600 are, I agree. WordPress teams 1152 00:38:43,600 --> 00:38:45,200 frequently don't understand how 1153 00:38:45,200 --> 00:38:47,280 connected they are, a little bit 1154 00:38:47,280 --> 00:38:48,640 because it's hard to know how 1155 00:38:48,640 --> 00:38:50,720 your actions affect others when 1156 00:38:50,720 --> 00:38:52,720 you just barely have enough time 1157 00:38:52,720 --> 00:38:54,160 to focus on the contributions 1158 00:38:54,160 --> 00:38:55,200 that you want to make to the 1159 00:38:55,200 --> 00:38:56,560 teams that you're participating 1160 00:38:56,560 --> 00:38:58,800 with. Myself, I think that 1161 00:38:58,800 --> 00:39:00,160 sharing the internal workings a 1162 00:39:00,160 --> 00:39:02,400 bit better from my side can help 1163 00:39:02,400 --> 00:39:04,160 us all to know who we might need 1164 00:39:04,160 --> 00:39:05,440 to collaborate with during 1165 00:39:05,440 --> 00:39:07,760 projects, and I'm working up a 1166 00:39:07,760 --> 00:39:10,000 podcast for 2021 to share 1167 00:39:10,000 --> 00:39:11,680 bite-sized insight for 1168 00:39:11,680 --> 00:39:13,280 contributors who want to know 1169 00:39:13,280 --> 00:39:14,240 more about how their 1170 00:39:14,800 --> 00:39:16,880 contributions fit into the 1171 00:39:16,880 --> 00:39:19,200 larger picture. But I also 1172 00:39:19,200 --> 00:39:20,320 understand that part of the 1173 00:39:20,320 --> 00:39:22,000 solution is getting more 1174 00:39:22,000 --> 00:39:24,080 contributors into the space, and 1175 00:39:24,080 --> 00:39:25,360 I don't necessarily have a 1176 00:39:25,360 --> 00:39:27,680 solution for that outside of our 1177 00:39:27,680 --> 00:39:28,800 in-person events, which, of 1178 00:39:28,800 --> 00:39:31,040 course, in 2020 we haven't seen 1179 00:39:31,040 --> 00:39:33,120 a lot of. But it does kind of 1180 00:39:33,120 --> 00:39:34,560 lead us into your next question, 1181 00:39:35,440 --> 00:39:37,520 given that WordPress is so 1182 00:39:37,520 --> 00:39:39,520 complex and there aren't enough 1183 00:39:39,520 --> 00:39:40,400 people, not enough 1184 00:39:40,400 --> 00:39:43,600 communication, what can we do? I 1185 00:39:43,600 --> 00:39:44,800 have been on the more- 1186 00:39:44,800 --> 00:39:47,360 communication bandwagon for a 1187 00:39:47,360 --> 00:39:50,640 long time. But I actually think 1188 00:39:50,640 --> 00:39:51,920 that one of our short-term 1189 00:39:51,920 --> 00:39:54,160 problems as a project is how to 1190 00:39:54,160 --> 00:39:56,560 take our efficient communication 1191 00:39:56,560 --> 00:39:59,040 and make it more effective. I'm 1192 00:39:59,040 --> 00:40:01,280 gonna quote for you now the 19th 1193 00:40:01,280 --> 00:40:03,200 lesson from The Cathedral and 1194 00:40:03,200 --> 00:40:04,880 The Bazaar, our kind of source 1195 00:40:04,880 --> 00:40:06,320 material for things that we've 1196 00:40:06,320 --> 00:40:09,840 learned about open source in 1197 00:40:10,400 --> 00:40:13,200 general. To quote it, it says, 1198 00:40:13,200 --> 00:40:14,320 "provided the development 1199 00:40:14,320 --> 00:40:16,160 coordinator has a communications 1200 00:40:16,160 --> 00:40:18,000 medium at least as good as the 1201 00:40:18,000 --> 00:40:20,240 internet and knows how to lead 1202 00:40:20,240 --> 00:40:22,320 without coercion, many heads are 1203 00:40:22,320 --> 00:40:23,840 inevitability better than one." 1204 00:40:25,280 --> 00:40:28,800 And later in the document, later 1205 00:40:28,800 --> 00:40:30,320 in this -- in this piece of 1206 00:40:30,320 --> 00:40:33,920 writing, it's noted that open 1207 00:40:33,920 --> 00:40:35,840 source at scale can't 1208 00:40:35,840 --> 00:40:39,840 necessarily function very 1209 00:40:39,840 --> 00:40:42,640 effectively by constantly having 1210 00:40:42,640 --> 00:40:44,400 chaos all the time. It's hard 1211 00:40:44,400 --> 00:40:46,240 for human beings to work in that 1212 00:40:46,240 --> 00:40:47,680 sort of space, and so I think 1213 00:40:47,680 --> 00:40:49,040 that one of our short-term 1214 00:40:49,040 --> 00:40:51,840 questions for the project as a 1215 00:40:51,840 --> 00:40:54,320 whole is to make sure that when 1216 00:40:54,320 --> 00:40:56,160 we ask people to communicate 1217 00:40:56,160 --> 00:40:57,280 about what they're doing, why 1218 00:40:57,280 --> 00:40:58,560 they're doing it and where they 1219 00:40:58,560 --> 00:41:00,960 are doing it, we have made sure, 1220 00:41:00,960 --> 00:41:03,520 as leaders in WordPress, that 1221 00:41:03,520 --> 00:41:06,480 the plans for the product are 1222 00:41:06,480 --> 00:41:08,160 clear, so that everyone makes 1223 00:41:08,160 --> 00:41:09,200 good use of their time. 1224 00:41:09,960 --> 00:41:14,160 >> Myself, Monika, I'm working 1225 00:41:14,160 --> 00:41:16,720 with WordPress since 2015 and 1226 00:41:16,720 --> 00:41:18,000 regular contributing to the 1227 00:41:18,000 --> 00:41:20,320 WordPress. My question is about 1228 00:41:20,320 --> 00:41:22,080 the automation testing in the 1229 00:41:22,080 --> 00:41:24,880 WordPress ecosystem. As we know, 1230 00:41:24,880 --> 00:41:26,560 people are very much concerned 1231 00:41:26,560 --> 00:41:28,400 about the securities and the 1232 00:41:28,400 --> 00:41:30,160 other issues before upgrading to 1233 00:41:30,160 --> 00:41:33,120 the new version. So what are the 1234 00:41:33,120 --> 00:41:34,800 things we can implement in our 1235 00:41:34,800 --> 00:41:37,200 WordPress ecosystem to deliver 1236 00:41:37,200 --> 00:41:39,920 100% security? So, basically, 1237 00:41:39,920 --> 00:41:41,360 what are the automation things 1238 00:41:41,360 --> 00:41:42,480 we can integrate in our 1239 00:41:42,480 --> 00:41:43,920 WordPress ecosystem? Thank you. 1240 00:41:44,680 --> 00:41:47,200 >> Hi, Monika. I'm Jonathan. 1241 00:41:47,200 --> 00:41:48,080 Thank you for asking this 1242 00:41:48,080 --> 00:41:50,800 question. Security is always 1243 00:41:50,800 --> 00:41:52,240 evolving and changing, and 1244 00:41:52,240 --> 00:41:53,280 moving targets are very 1245 00:41:53,280 --> 00:41:54,960 difficult to reach definitively. 1246 00:41:55,600 --> 00:41:56,800 It's also a process that 1247 00:41:56,800 --> 00:41:58,720 unfortunately cannot be 100% 1248 00:41:58,720 --> 00:42:00,560 automated. Everyone needs to 1249 00:42:00,560 --> 00:42:01,680 learn to practice a 1250 00:42:01,680 --> 00:42:04,480 security-first mindset, but, 1251 00:42:04,480 --> 00:42:06,080 thankfully, there are some tools 1252 00:42:06,080 --> 00:42:07,120 that can help us in our 1253 00:42:07,120 --> 00:42:09,600 projects. For example, the 1254 00:42:09,600 --> 00:42:11,040 WordPress security team has 1255 00:42:11,040 --> 00:42:12,320 several automated testing 1256 00:42:12,320 --> 00:42:13,760 processes behind the scenes. 1257 00:42:14,480 --> 00:42:16,160 Every change to WordPress core 1258 00:42:16,160 --> 00:42:17,760 is run through these processes 1259 00:42:17,760 --> 00:42:19,360 to protect against known 1260 00:42:19,360 --> 00:42:21,760 security vulnerabilities. The 1261 00:42:21,760 --> 00:42:23,120 processes are continually 1262 00:42:23,120 --> 00:42:24,560 changing and expanding as new 1263 00:42:24,560 --> 00:42:25,840 security issues are discovered 1264 00:42:25,840 --> 00:42:28,160 and fixed. I'm being a little 1265 00:42:28,160 --> 00:42:29,360 intentionally vague, because 1266 00:42:29,360 --> 00:42:30,960 often security practiced will be 1267 00:42:30,960 --> 00:42:32,560 tailored to a certain project or 1268 00:42:32,560 --> 00:42:34,720 organization. Being ambiguous 1269 00:42:34,720 --> 00:42:36,080 will help you keep your project 1270 00:42:36,080 --> 00:42:39,040 more secure. There are also some 1271 00:42:39,040 --> 00:42:40,800 code analysis tools like the PHP 1272 00:42:40,800 --> 00:42:42,240 code sniffer that can be used to 1273 00:42:42,240 --> 00:42:44,000 identify potentially insecure 1274 00:42:44,000 --> 00:42:46,080 code in your project. Adding 1275 00:42:46,080 --> 00:42:47,520 these tools to your project and 1276 00:42:47,520 --> 00:42:48,960 requiring them to produce a 1277 00:42:48,960 --> 00:42:50,800 passing scan is a great way to 1278 00:42:50,800 --> 00:42:52,240 ensure the quality of the code 1279 00:42:52,240 --> 00:42:55,360 that you release. In WordPress 1280 00:42:55,360 --> 00:42:57,280 itself, several user-facing 1281 00:42:57,280 --> 00:42:58,560 features have been introduced in 1282 00:42:58,560 --> 00:43:00,480 the last few major versions that 1283 00:43:00,480 --> 00:43:02,240 make it easier for site owners 1284 00:43:02,240 --> 00:43:03,760 to be more aware of their site 1285 00:43:03,760 --> 00:43:06,400 security. The most recent one is 1286 00:43:06,400 --> 00:43:08,480 the ability to opt in to auto- 1287 00:43:08,480 --> 00:43:10,000 updates for plug-ins and themes. 1288 00:43:10,960 --> 00:43:12,560 Turning these on is a great way 1289 00:43:12,560 --> 00:43:13,840 to make sure your sites are 1290 00:43:13,840 --> 00:43:15,120 running the latest and most 1291 00:43:15,120 --> 00:43:17,120 secure code automatically, all 1292 00:43:17,120 --> 00:43:20,000 the time. Site Health is another 1293 00:43:20,000 --> 00:43:21,600 great example of a user-facing 1294 00:43:21,600 --> 00:43:23,680 tool. There are over a dozen 1295 00:43:23,680 --> 00:43:25,360 security-related checks included 1296 00:43:25,360 --> 00:43:27,280 in WordPress core by default, 1297 00:43:27,280 --> 00:43:28,720 and when they don't pass, site 1298 00:43:28,720 --> 00:43:30,480 health educates the user and 1299 00:43:30,480 --> 00:43:32,160 provides them with a recommend 1300 00:43:32,160 --> 00:43:33,760 way forward to fix the issue. 1301 00:43:35,040 --> 00:43:36,560 Any plug-in and theme can add 1302 00:43:36,560 --> 00:43:38,400 their own test to Site Health. 1303 00:43:38,400 --> 00:43:39,120 If there are any 1304 00:43:39,120 --> 00:43:40,880 security-related checks specific 1305 00:43:40,880 --> 00:43:42,720 to your project, adding them at 1306 00:43:42,720 --> 00:43:44,320 Site Health is a great way to 1307 00:43:44,320 --> 00:43:46,080 make a site owner aware of a 1308 00:43:46,080 --> 00:43:48,640 problem automatically. A few of 1309 00:43:48,640 --> 00:43:49,760 the tests check that you are 1310 00:43:49,760 --> 00:43:51,440 running secure versions of tools 1311 00:43:51,440 --> 00:43:52,720 installed at the server level. 1312 00:43:53,600 --> 00:43:55,760 Using PHP as an example, you 1313 00:43:55,760 --> 00:43:57,120 could set up an email alert 1314 00:43:57,120 --> 00:43:58,800 whenever a new version of PHP is 1315 00:43:58,800 --> 00:44:00,720 released. This would help you 1316 00:44:00,720 --> 00:44:02,400 automatically become aware of 1317 00:44:02,400 --> 00:44:03,840 security releases so you could 1318 00:44:03,840 --> 00:44:05,280 reach out to your host and 1319 00:44:05,280 --> 00:44:06,800 request that they update you to 1320 00:44:06,800 --> 00:44:09,680 this new version. Because of our 1321 00:44:09,680 --> 00:44:11,280 strong community, we have the 1322 00:44:11,280 --> 00:44:12,960 opportunity to work together to 1323 00:44:12,960 --> 00:44:15,200 continue educating site owners, 1324 00:44:15,200 --> 00:44:16,960 users and developers about 1325 00:44:16,960 --> 00:44:18,800 security best practices. If 1326 00:44:18,800 --> 00:44:20,000 everyone is more aware of 1327 00:44:20,000 --> 00:44:21,920 insecure practices, the entire 1328 00:44:21,920 --> 00:44:23,920 ecosystem will be elevated as a 1329 00:44:23,920 --> 00:44:25,760 result. I hope that that's 1330 00:44:25,760 --> 00:44:26,640 helpful and answers your 1331 00:44:26,640 --> 00:44:27,840 questions, and thank you for 1332 00:44:27,840 --> 00:44:28,720 choosing WordPress. 1333 00:44:30,200 --> 00:44:33,280 >> Hey. My name is Robert 1334 00:44:33,280 --> 00:44:35,680 Anderson. I am a WordPress 1335 00:44:35,680 --> 00:44:37,360 co-contributor living in Sydney, 1336 00:44:37,360 --> 00:44:40,320 Australia. Seth Miller wrote in 1337 00:44:40,320 --> 00:44:42,720 with this question: As Gutenberg 1338 00:44:42,720 --> 00:44:44,480 becomes more modern and feature- 1339 00:44:44,480 --> 00:44:46,240 driven, how do you approach 1340 00:44:46,240 --> 00:44:47,920 onboarding of new contributors 1341 00:44:47,920 --> 00:44:49,760 and other curious types - think 1342 00:44:49,760 --> 00:44:51,760 novice theme developer - to look 1343 00:44:51,760 --> 00:44:52,960 into block building with the 1344 00:44:52,960 --> 00:44:54,880 existing complexity of WebPack 1345 00:44:54,880 --> 00:44:57,600 and other build tools? Great 1346 00:44:57,600 --> 00:44:59,040 question, Seth. Thank you for 1347 00:44:59,040 --> 00:45:02,160 asking it. So, before I get into 1348 00:45:02,160 --> 00:45:04,160 the meat of Seth's question, 1349 00:45:04,160 --> 00:45:05,600 there's two quick things that I 1350 00:45:05,600 --> 00:45:08,160 want to note. Firstly, one of 1351 00:45:08,160 --> 00:45:09,600 the aims of the Block Editor is 1352 00:45:09,600 --> 00:45:11,280 to make it so that users can 1353 00:45:11,280 --> 00:45:13,040 create really ambitious websites 1354 00:45:13,040 --> 00:45:14,400 without having to be a theme 1355 00:45:14,400 --> 00:45:16,880 developer. So as an example, if 1356 00:45:16,880 --> 00:45:19,120 you insert a custom HTML block 1357 00:45:19,120 --> 00:45:20,240 and then save that as a 1358 00:45:20,240 --> 00:45:22,320 reusable block, you've more or 1359 00:45:22,320 --> 00:45:23,840 less created a new block without 1360 00:45:23,840 --> 00:45:25,040 having to write a single line of 1361 00:45:25,040 --> 00:45:26,000 code, which is really cool. 1362 00:45:27,600 --> 00:45:29,920 Secondly, tools like WebPack are 1363 00:45:29,920 --> 00:45:32,480 totally optional. Developers can 1364 00:45:32,480 --> 00:45:34,960 write a block using plain old 1365 00:45:34,960 --> 00:45:37,040 JavaScript that all web browsers 1366 00:45:37,040 --> 00:45:39,440 will understand, and, in fact, 1367 00:45:39,440 --> 00:45:40,880 if you load up the Gutenberg 1368 00:45:40,880 --> 00:45:42,720 handbook, you'll see that all of 1369 00:45:42,720 --> 00:45:44,160 our code examples there come in 1370 00:45:44,160 --> 00:45:46,720 two flavors, ESNext, which has 1371 00:45:46,720 --> 00:45:47,920 all the bells whistles, 1372 00:45:47,920 --> 00:45:51,680 including React's JSX, and ES5, 1373 00:45:51,680 --> 00:45:57,440 which doesn't. But, yes building 1374 00:45:57,440 --> 00:45:59,040 blocks and working with React, 1375 00:45:59,040 --> 00:46:01,520 is a lot easier if you are able 1376 00:46:01,520 --> 00:46:04,400 to use React's JSX syntax, so 1377 00:46:04,400 --> 00:46:05,840 setting up some kind of build 1378 00:46:05,840 --> 00:46:07,120 tooling is often worth the 1379 00:46:07,120 --> 00:46:09,440 up-front effort, and, yes, I 1380 00:46:09,440 --> 00:46:12,000 100% agree that this is very 1381 00:46:12,000 --> 00:46:13,280 challenging and can be pretty 1382 00:46:13,280 --> 00:46:15,040 off-putting to new developers. 1383 00:46:16,400 --> 00:46:18,560 Broadly speaking, I think that 1384 00:46:18,560 --> 00:46:20,400 there's two things that we can 1385 00:46:20,400 --> 00:46:22,720 do to make this easier: Tooling 1386 00:46:22,720 --> 00:46:25,120 and education. On the tooling 1387 00:46:25,120 --> 00:46:27,120 front, we now have some really 1388 00:46:27,120 --> 00:46:28,560 neat tools that make getting set 1389 00:46:28,560 --> 00:46:29,840 up with block development a lot 1390 00:46:29,840 --> 00:46:32,000 easier. The first, which is 1391 00:46:32,000 --> 00:46:33,520 developed by the core team at 1392 00:46:33,520 --> 00:46:36,320 WordPress, is WordPress/scripts. 1393 00:46:37,120 --> 00:46:39,680 This is a npm package that hides 1394 00:46:39,680 --> 00:46:41,200 away all of the complexity of 1395 00:46:41,200 --> 00:46:43,280 webpack and gives you a single 1396 00:46:43,280 --> 00:46:45,040 command that turns a source 1397 00:46:45,040 --> 00:46:47,520 directory of JavaScript, which 1398 00:46:47,520 --> 00:46:49,760 has all the fancy syntax, into a 1399 00:46:49,760 --> 00:46:51,920 build directory of compiled 1400 00:46:51,920 --> 00:46:55,840 JavaScript. The second, 1401 00:46:56,720 --> 00:46:58,240 developed by the WordPress 1402 00:46:58,240 --> 00:47:01,159 community is "create-guten-block." 1403 00:47:01,159 --> 00:47:02,880 This one gives you a 1404 00:47:02,880 --> 00:47:04,320 single command that instantly 1405 00:47:04,320 --> 00:47:06,320 creates an entire block plugin 1406 00:47:06,320 --> 00:47:08,160 for you. It does all the work of 1407 00:47:08,160 --> 00:47:09,200 configuring the build 1408 00:47:09,200 --> 00:47:11,440 environment and generates, like, 1409 00:47:11,440 --> 00:47:13,440 the necessary PHP to load things 1410 00:47:13,440 --> 00:47:14,880 into WordPress. It's really 1411 00:47:14,880 --> 00:47:18,480 quite straightforward. On the 1412 00:47:18,480 --> 00:47:20,480 education front, we have some 1413 00:47:20,480 --> 00:47:22,080 really great tutorials in the 1414 00:47:22,080 --> 00:47:23,520 Gutenberg handbook which cover 1415 00:47:23,520 --> 00:47:25,040 how to get set up with block 1416 00:47:25,040 --> 00:47:26,480 development using WordPress 1417 00:47:27,280 --> 00:47:29,680 script and you can see them at 1418 00:47:29,680 --> 00:47:30,720 wordpress.org/gutenberg/handbook 1419 00:47:34,800 --> 00:47:36,240 and, lastly, the WordPress 1420 00:47:36,240 --> 00:47:38,720 training team has just recently 1421 00:47:38,720 --> 00:47:41,280 learned learn.wordpress.org 1422 00:47:41,840 --> 00:47:43,440 which is a new home for video 1423 00:47:43,440 --> 00:47:45,600 workshops about WordPress. And 1424 00:47:45,600 --> 00:47:47,120 one of the video workshops there 1425 00:47:47,120 --> 00:47:49,920 by Jonathan Bossenger is all 1426 00:47:49,920 --> 00:47:52,480 about how to develop a block, so 1427 00:47:52,480 --> 00:47:53,600 definitely check that out and 1428 00:47:53,600 --> 00:47:57,680 definitely watch that space. I 1429 00:47:57,680 --> 00:47:58,880 hope that was helpful. I hope I 1430 00:47:58,880 --> 00:48:00,880 answered your question. And 1431 00:48:00,880 --> 00:48:01,680 thank you for choosing 1432 00:48:01,680 --> 00:48:02,240 WordPress. 1433 00:48:02,240 --> 00:48:04,960 >> Hi. My name is Sudar Muthu. 1434 00:48:04,960 --> 00:48:06,400 I'm from a city called Chennai 1435 00:48:06,400 --> 00:48:07,680 in the southern part of India. 1436 00:48:08,320 --> 00:48:09,280 I've been involved with 1437 00:48:09,280 --> 00:48:10,880 WordPress for about 15 years 1438 00:48:10,880 --> 00:48:12,800 now, and for the past six years, 1439 00:48:12,800 --> 00:48:14,080 I've been working as a full-time 1440 00:48:14,080 --> 00:48:16,160 WordPress developer. In short, 1441 00:48:16,160 --> 00:48:17,840 WordPress is what puts food on 1442 00:48:17,840 --> 00:48:20,560 my table. So here's my question. 1443 00:48:20,560 --> 00:48:22,400 So, it's been about 17 years 1444 00:48:22,400 --> 00:48:23,520 since the first version of 1445 00:48:23,520 --> 00:48:25,040 WordPress has been released, and 1446 00:48:25,040 --> 00:48:27,200 all of us know where WordPress 1447 00:48:27,200 --> 00:48:28,880 is there right now. So my 1448 00:48:28,880 --> 00:48:31,120 question is, where do you see 1449 00:48:31,120 --> 00:48:33,840 WordPress in the next 17 years? 1450 00:48:34,880 --> 00:48:35,280 Thank you. 1451 00:48:35,280 --> 00:48:38,160 >> Sudar, 17 years is such a 1452 00:48:38,160 --> 00:48:40,800 long time! Sometimes I feel 1453 00:48:40,800 --> 00:48:42,160 amazed that I've been doing 1454 00:48:42,160 --> 00:48:44,960 WordPress for this long. I think 1455 00:48:44,960 --> 00:48:46,880 my hope is the same as many 1456 00:48:46,880 --> 00:48:47,840 others in the WordPress 1457 00:48:47,840 --> 00:48:51,920 community, that by 2037 we've 1458 00:48:51,920 --> 00:48:54,400 gotten the vast majority, maybe 1459 00:48:54,400 --> 00:48:56,160 as close to 100% as we can get 1460 00:48:56,160 --> 00:48:57,360 of the web on open source 1461 00:48:57,360 --> 00:48:59,600 software. I'd love to see 1462 00:48:59,600 --> 00:49:02,160 Gutenberg used not just by 1463 00:49:02,160 --> 00:49:04,000 WordPress, but by all of its 1464 00:49:04,000 --> 00:49:05,760 competitors as well, by everyone 1465 00:49:05,760 --> 00:49:08,000 who is accepting text in a box 1466 00:49:08,000 --> 00:49:09,600 on the internet or on native. 1467 00:49:10,320 --> 00:49:11,840 I'd love them to build on 1468 00:49:11,840 --> 00:49:13,680 Gutenberg Blocks, because then 1469 00:49:13,680 --> 00:49:14,960 that allows us to work together 1470 00:49:14,960 --> 00:49:15,920 on something that we all used to 1471 00:49:15,920 --> 00:49:17,520 have to rewrite and recreate a 1472 00:49:17,520 --> 00:49:19,440 million, million times, and I 1473 00:49:19,440 --> 00:49:20,720 believe that's how humanity 1474 00:49:20,720 --> 00:49:22,080 moves forward, is when we 1475 00:49:22,080 --> 00:49:23,200 collaborate, not when we 1476 00:49:23,200 --> 00:49:26,960 compete. In terms of, you know, 1477 00:49:26,960 --> 00:49:29,200 freedom and the open web, it's 1478 00:49:29,200 --> 00:49:30,160 hard to imagine what 1479 00:49:30,160 --> 00:49:31,600 technologies will be relevant. 1480 00:49:32,480 --> 00:49:35,680 One thing I always say within my 1481 00:49:35,680 --> 00:49:37,680 company at Automattic is that 1482 00:49:38,960 --> 00:49:40,400 the particular change will be 1483 00:49:40,400 --> 00:49:41,840 impossible to predict, but the 1484 00:49:41,840 --> 00:49:43,520 fact that change is going to 1485 00:49:43,520 --> 00:49:47,040 happen is inevitable. It is 100% 1486 00:49:47,040 --> 00:49:49,360 certain. And so as long as we 1487 00:49:49,360 --> 00:49:52,160 can stay adaptable, flexible, 1488 00:49:52,160 --> 00:49:53,600 not become too ossified in our 1489 00:49:53,600 --> 00:49:55,280 beliefs and always keep that 1490 00:49:55,280 --> 00:49:57,360 beginner's mind, the ability to 1491 00:49:57,360 --> 00:49:59,360 learn new technology. I've been 1492 00:49:59,360 --> 00:50:00,480 really, really impressed, 1493 00:50:00,480 --> 00:50:01,600 particularly in the past year or 1494 00:50:01,600 --> 00:50:03,600 two, post-Gutenberg, how so many 1495 00:50:03,600 --> 00:50:04,720 folks across WordPress have been 1496 00:50:04,720 --> 00:50:06,960 picking up JavaScript. You know, 1497 00:50:06,960 --> 00:50:08,800 taking where they were probably 1498 00:50:08,800 --> 00:50:12,320 PHP pros and JavaScript novices, 1499 00:50:12,320 --> 00:50:13,760 they've really invested the time 1500 00:50:13,760 --> 00:50:15,440 to become incredible JavaScript 1501 00:50:15,440 --> 00:50:16,960 developers, and now the entire 1502 00:50:16,960 --> 00:50:17,760 WordPress community is 1503 00:50:17,760 --> 00:50:19,360 benefitting from that. There 1504 00:50:19,360 --> 00:50:20,560 will be new generations of 1505 00:50:20,560 --> 00:50:22,960 technology. I imagine 17 years 1506 00:50:22,960 --> 00:50:24,320 from now, there will be 1507 00:50:24,320 --> 00:50:25,520 something after JavaScript that 1508 00:50:25,520 --> 00:50:26,480 will be the most important thing 1509 00:50:26,480 --> 00:50:27,760 to WordPress. I don't know what 1510 00:50:27,760 --> 00:50:28,800 that will be yet, but I'm 1511 00:50:28,800 --> 00:50:30,560 looking forward to finding it 1512 00:50:30,560 --> 00:50:32,080 out, and I hope that you're a 1513 00:50:32,080 --> 00:50:33,440 part of the journey as well, so 1514 00:50:34,240 --> 00:50:34,880 see you around. 1515 00:50:35,480 --> 00:50:38,960 >> Hi, my name is Tobi or Tobi 1516 00:50:38,960 --> 00:50:40,880 Ffjellner, as my handle is here 1517 00:50:40,880 --> 00:50:44,400 for WordPress. I'm one of the 1518 00:50:45,840 --> 00:50:47,040 people in the biggest 1519 00:50:47,600 --> 00:50:49,760 contributor team, polyglots. We 1520 00:50:49,760 --> 00:50:51,840 have almost 60,000 people who 1521 00:50:51,840 --> 00:50:54,000 have contributed at least some 1522 00:50:54,000 --> 00:50:56,080 translations to WordPress to 1523 00:50:57,040 --> 00:50:59,600 around 200 different language 1524 00:50:59,600 --> 00:51:01,600 versions, and out of those, 1525 00:51:02,160 --> 00:51:04,720 between 40 and 60 are actively 1526 00:51:04,720 --> 00:51:06,480 maintained, so that you can use 1527 00:51:06,480 --> 00:51:09,040 them right now if you want. And 1528 00:51:09,040 --> 00:51:12,160 a lot of people do that. 55% of 1529 00:51:12,160 --> 00:51:14,640 all WordPress sites around the 1530 00:51:14,640 --> 00:51:16,400 world that we know about use 1531 00:51:16,400 --> 00:51:18,400 some other language than U.S. 1532 00:51:18,400 --> 00:51:21,760 English. My question is about 1533 00:51:21,760 --> 00:51:24,240 multilingual WordPress. It has 1534 00:51:24,240 --> 00:51:26,240 been mentioned a couple of times 1535 00:51:26,240 --> 00:51:28,400 that in a future phase, 1536 00:51:28,400 --> 00:51:30,720 Gutenberg will cater for 1537 00:51:30,720 --> 00:51:33,120 multilingual content. I would 1538 00:51:33,120 --> 00:51:34,960 like to suggest that we already 1539 00:51:34,960 --> 00:51:36,960 now make decisions on what 1540 00:51:37,520 --> 00:51:39,520 storage structures we are going 1541 00:51:39,520 --> 00:51:41,680 to use and procedures, and 1542 00:51:41,680 --> 00:51:45,360 perhaps even already now go 1543 00:51:45,360 --> 00:51:47,680 forward to make WordPress 1544 00:51:47,680 --> 00:51:49,200 multilingual. There are already 1545 00:51:49,200 --> 00:51:51,200 solutions, and we could probably 1546 00:51:51,200 --> 00:51:53,520 reuse some of those, and by 1547 00:51:53,520 --> 00:51:54,800 doing this we open the 1548 00:51:54,800 --> 00:51:57,360 possibility for a lot of new 1549 00:51:58,480 --> 00:52:00,400 solutions to come up that could 1550 00:52:00,400 --> 00:52:02,800 support procedures around 1551 00:52:02,800 --> 00:52:04,160 translation, handling the 1552 00:52:04,160 --> 00:52:06,320 multilingual content, and so on. 1553 00:52:06,320 --> 00:52:09,120 And that part is where Gutenberg 1554 00:52:09,120 --> 00:52:10,160 actually would need to develop 1555 00:52:10,160 --> 00:52:12,320 something, but for the storage 1556 00:52:12,320 --> 00:52:14,160 procedures and so on, I think 1557 00:52:14,160 --> 00:52:15,840 we're talking more about PHP 1558 00:52:15,840 --> 00:52:17,520 development, where we could 1559 00:52:17,520 --> 00:52:20,160 reuse already existing plug-ins 1560 00:52:20,160 --> 00:52:22,800 to a large extent. Thank you. 1561 00:52:23,880 --> 00:52:26,160 >> Tobi, thank you so much for 1562 00:52:26,160 --> 00:52:27,680 your question, and, of course, 1563 00:52:27,680 --> 00:52:29,120 thank you for your contributions 1564 00:52:30,160 --> 00:52:31,360 for -- with translations and 1565 00:52:31,360 --> 00:52:33,120 that entire polyglots team. Much 1566 00:52:33,120 --> 00:52:35,840 love to the polyglots team. I, 1567 00:52:35,840 --> 00:52:37,920 like you, am very anxious to get 1568 00:52:37,920 --> 00:52:41,520 multilingual into Gutenberg, 1569 00:52:41,520 --> 00:52:42,720 whether we do it as part of 1570 00:52:42,720 --> 00:52:44,240 core, as part of an official 1571 00:52:44,240 --> 00:52:47,840 plug-in, TBD, but part of the 1572 00:52:47,840 --> 00:52:50,160 reason we made it Phase 4 is I 1573 00:52:50,160 --> 00:52:51,760 know that we can only do so many 1574 00:52:51,760 --> 00:52:54,960 things well at a time. And it is 1575 00:52:54,960 --> 00:52:57,200 supremely important that we 1576 00:52:57,200 --> 00:52:59,520 really execute super well on 1577 00:52:59,520 --> 00:53:01,440 these first phases of Gutenberg 1578 00:53:01,440 --> 00:53:03,200 Blocks. That's why also, even 1579 00:53:03,200 --> 00:53:04,400 though I'm super excited about 1580 00:53:04,400 --> 00:53:05,280 it, we haven't officially 1581 00:53:05,280 --> 00:53:06,560 started anything with the 1582 00:53:06,560 --> 00:53:07,840 real-time co-editing yet, for 1583 00:53:07,840 --> 00:53:11,520 Phase 3. If we don't get Phase 1 1584 00:53:11,520 --> 00:53:13,680 and Phase 2 to be the best 1585 00:53:13,680 --> 00:53:15,200 experiences in the world for 1586 00:53:15,200 --> 00:53:17,120 editing, bar none, of any open 1587 00:53:17,120 --> 00:53:18,240 source, any proprietary 1588 00:53:18,240 --> 00:53:21,520 competitors, any builders, Phase 1589 00:53:21,520 --> 00:53:23,200 3 and Phase 4 just won't matter, 1590 00:53:23,200 --> 00:53:26,240 right? Because it just -- 1591 00:53:26,240 --> 00:53:27,760 WordPress won't be relevant a 1592 00:53:27,760 --> 00:53:30,720 decade from now. So I do believe 1593 00:53:30,720 --> 00:53:32,400 that that is the most important 1594 00:53:32,400 --> 00:53:34,640 problem that we're facing. And 1595 00:53:34,640 --> 00:53:36,400 part of why, even though we do 1596 00:53:36,400 --> 00:53:37,520 have a wide breadth of 1597 00:53:37,520 --> 00:53:38,560 contributors, and like you 1598 00:53:38,560 --> 00:53:40,160 mentioned, some plug-ins that do 1599 00:53:40,160 --> 00:53:44,000 solve multilingual already, I 1600 00:53:44,000 --> 00:53:46,000 don't want to dilute sort of the 1601 00:53:46,000 --> 00:53:48,720 core contributors' focus away 1602 00:53:48,720 --> 00:53:50,240 from the initial phases of 1603 00:53:50,240 --> 00:53:52,320 Gutenberg, because that's just 1604 00:53:52,320 --> 00:53:53,840 how important I think they are. 1605 00:53:54,400 --> 00:53:56,000 Now, that said, much like 1606 00:53:56,000 --> 00:53:57,440 Gutenberg has innovated in 1607 00:53:57,440 --> 00:53:59,200 plug-ins and then it gets later 1608 00:53:59,200 --> 00:54:00,480 adopted and merged into core, 1609 00:54:01,280 --> 00:54:02,640 there is nothing stopping, I 1610 00:54:02,640 --> 00:54:04,640 think, you know, more innovation 1611 00:54:04,640 --> 00:54:05,840 or more investments happening in 1612 00:54:05,840 --> 00:54:07,280 the plug-ins. In fact, I think 1613 00:54:07,280 --> 00:54:08,640 it's interesting that the 1614 00:54:08,640 --> 00:54:10,160 plug-ins can take various 1615 00:54:10,160 --> 00:54:11,520 different approaches with 1616 00:54:11,520 --> 00:54:13,600 regards to data storage and we 1617 00:54:13,600 --> 00:54:14,960 can see which works the best and 1618 00:54:14,960 --> 00:54:16,640 what scales, and the pluses and 1619 00:54:16,640 --> 00:54:19,200 minuses of each. My hope is that 1620 00:54:19,200 --> 00:54:20,720 down the line, much like the 1621 00:54:20,720 --> 00:54:22,320 page builders are coalescing 1622 00:54:22,320 --> 00:54:24,320 around sort of Gutenberg as -- 1623 00:54:24,320 --> 00:54:26,160 and Blocks as page building, 1624 00:54:26,720 --> 00:54:27,840 kind of primitive that they all 1625 00:54:27,840 --> 00:54:30,320 build on top of. My hope is that 1626 00:54:30,320 --> 00:54:31,600 using learnings and hopefully 1627 00:54:31,600 --> 00:54:32,640 contributions from all of the 1628 00:54:32,640 --> 00:54:33,760 folks currently during 1629 00:54:33,760 --> 00:54:35,840 multilingual plug-ins right now, 1630 00:54:35,840 --> 00:54:37,840 we can figure out what is the 1631 00:54:37,840 --> 00:54:40,480 sort of 20% that gets us 80% of 1632 00:54:40,480 --> 00:54:41,680 the way there and create a 1633 00:54:41,680 --> 00:54:42,800 common framework that all of 1634 00:54:42,800 --> 00:54:44,960 them build on and then, you 1635 00:54:44,960 --> 00:54:46,000 know, much like we are with 1636 00:54:46,000 --> 00:54:48,320 Gutenberg Blocks, that Rails 1637 00:54:48,320 --> 00:54:49,760 will, you know, work well with 1638 00:54:49,760 --> 00:54:51,200 every other plug-in and theme. 1639 00:54:51,200 --> 00:54:52,880 So that is the hope, that is the 1640 00:54:52,880 --> 00:54:56,080 plan. 2022 is what I am 1641 00:54:56,080 --> 00:54:58,480 personally hoping to begin 1642 00:54:59,040 --> 00:55:00,720 working and focusing on this. 1643 00:55:00,720 --> 00:55:02,640 That also gives me a few years 1644 00:55:02,640 --> 00:55:05,520 to learn another language. Thank 1645 00:55:05,520 --> 00:55:06,480 you for your question. I'll see 1646 00:55:06,480 --> 00:55:07,280 you around WordPress. 1647 00:55:09,080 --> 00:55:12,640 >> Hi, Tom. I'm Otto. You wrote 1648 00:55:12,640 --> 00:55:15,120 in with this question. It reads, 1649 00:55:15,120 --> 00:55:16,160 sorry I can't make a video to 1650 00:55:16,160 --> 00:55:17,520 ask my question, but what I 1651 00:55:17,520 --> 00:55:18,720 would like to ask is what you 1652 00:55:18,720 --> 00:55:19,920 think about plug-ins like 1653 00:55:19,920 --> 00:55:21,680 Wordfence and Security Ninja 1654 00:55:21,680 --> 00:55:23,120 which recommend removing version 1655 00:55:23,120 --> 00:55:24,320 information from WordPress 1656 00:55:24,320 --> 00:55:25,760 headers and changing file 1657 00:55:25,760 --> 00:55:27,760 operations for certain files. If 1658 00:55:27,760 --> 00:55:28,560 you agree with these 1659 00:55:28,560 --> 00:55:30,000 permissions, then I wonder why 1660 00:55:30,000 --> 00:55:30,960 they aren't implemented in the 1661 00:55:30,960 --> 00:55:32,640 WordPress core. Or if you 1662 00:55:32,640 --> 00:55:34,400 disagree, then why are these 1663 00:55:34,400 --> 00:55:36,560 plug-ins allowed to remain in 1664 00:55:36,560 --> 00:55:38,240 the plug-in libraries and 1665 00:55:38,240 --> 00:55:40,160 charged for making changes that 1666 00:55:40,160 --> 00:55:41,040 are not recommended by 1667 00:55:41,040 --> 00:55:44,080 WordPress. That's a good 1668 00:55:44,080 --> 00:55:49,040 question, Tom. Well, removing 1669 00:55:49,040 --> 00:55:50,320 version information is often 1670 00:55:50,320 --> 00:55:51,600 referred to as a security 1671 00:55:51,600 --> 00:55:54,240 measure, but on the whole, it is 1672 00:55:54,240 --> 00:55:56,240 kind of an ineffective one. You 1673 00:55:56,240 --> 00:55:57,120 see, the thinking is that 1674 00:55:57,120 --> 00:55:58,960 hackers search for versions in 1675 00:55:58,960 --> 00:56:00,320 things like the HTML of the site 1676 00:56:00,320 --> 00:56:01,840 before they run scripts on it, 1677 00:56:02,640 --> 00:56:04,160 but history has shown that to be 1678 00:56:04,160 --> 00:56:07,040 rarely the case. The most common 1679 00:56:07,040 --> 00:56:08,640 problem faced by sites is 1680 00:56:08,640 --> 00:56:10,640 essentially bots and scripting 1681 00:56:10,640 --> 00:56:12,160 attacks. From these kind of 1682 00:56:12,160 --> 00:56:14,080 automated attempts, the failed 1683 00:56:14,080 --> 00:56:16,560 cases don't really matter, so it 1684 00:56:16,560 --> 00:56:18,720 doesn't save a hacker any time 1685 00:56:18,720 --> 00:56:20,160 or effort to have sophisticated 1686 00:56:20,160 --> 00:56:21,440 code to check versioning first. 1687 00:56:22,480 --> 00:56:24,000 So, by and large, this kind of 1688 00:56:24,000 --> 00:56:25,920 thing is the same as hiding the 1689 00:56:25,920 --> 00:56:27,760 login screen. It's not for 1690 00:56:27,760 --> 00:56:29,200 security, it's mostly for 1691 00:56:29,200 --> 00:56:31,680 vanity. The problem really with 1692 00:56:31,680 --> 00:56:32,560 calling these kind of things 1693 00:56:32,560 --> 00:56:34,720 security measures is that users 1694 00:56:34,720 --> 00:56:36,320 who don't understand security in 1695 00:56:36,320 --> 00:56:37,760 the form of layers of protection 1696 00:56:38,480 --> 00:56:39,600 will think that doing these is 1697 00:56:39,600 --> 00:56:40,960 the only security they have to 1698 00:56:40,960 --> 00:56:43,360 have. I've seen people use bad 1699 00:56:43,360 --> 00:56:45,280 passwords simply because they 1700 00:56:45,280 --> 00:56:46,640 assume the login screen couldn't 1701 00:56:46,640 --> 00:56:47,680 be found in the first place. 1702 00:56:49,200 --> 00:56:50,720 Doing such things like removing 1703 00:56:50,720 --> 00:56:52,240 versions or hiding logins or 1704 00:56:53,120 --> 00:56:54,480 anything like that isn't 1705 00:56:54,480 --> 00:56:55,840 actively dangerous or harmful, 1706 00:56:56,400 --> 00:56:57,520 it's just not the first thing 1707 00:56:57,520 --> 00:56:58,720 you should be doing to improve 1708 00:56:58,720 --> 00:56:59,760 the security of a website in 1709 00:56:59,760 --> 00:57:02,240 general. So in that respect 1710 00:57:02,240 --> 00:57:03,040 they're allowed in the plug-in 1711 00:57:03,040 --> 00:57:05,040 directory the same as anything 1712 00:57:05,040 --> 00:57:06,640 else is. I mean, plug-ins are 1713 00:57:06,640 --> 00:57:07,840 allowed for people who want to 1714 00:57:08,400 --> 00:57:10,240 do such things, even if that 1715 00:57:10,240 --> 00:57:12,880 isn't the majority of users. I 1716 00:57:12,880 --> 00:57:13,760 mean, that's what plug-ins are 1717 00:57:13,760 --> 00:57:14,880 for, after all, it's to 1718 00:57:14,880 --> 00:57:15,920 customize your site the way you 1719 00:57:15,920 --> 00:57:17,920 want it. As for whether they can 1720 00:57:18,560 --> 00:57:20,320 charge for making changes, all 1721 00:57:20,320 --> 00:57:21,760 plug-ins on wordpress.org are 1722 00:57:21,760 --> 00:57:26,080 free. Any charges made by 1723 00:57:26,080 --> 00:57:28,160 plug-ins such as pro versions 1724 00:57:28,160 --> 00:57:30,000 that are sold elsewhere is sort 1725 00:57:30,000 --> 00:57:32,160 of outside of our purview. So in 1726 00:57:32,160 --> 00:57:34,880 that respect, I would say I only 1727 00:57:34,880 --> 00:57:37,040 use free plug-ins, so there's 1728 00:57:37,040 --> 00:57:38,160 probably a free plug-in that 1729 00:57:38,160 --> 00:57:40,080 will make the changes you want. 1730 00:57:40,080 --> 00:57:41,120 Thanks for your question, Tom. 1731 00:57:41,680 --> 00:57:42,880 Appreciate it. Hope that helps. 1732 00:57:44,600 --> 00:57:47,600 >> Hi, Matt. I'm Winstina. In 1733 00:57:47,600 --> 00:57:49,680 2017, I presented at Wordcamp 1734 00:57:49,680 --> 00:57:52,320 U.S. on how cities and towns can 1735 00:57:52,320 --> 00:57:53,680 work with their residents to 1736 00:57:53,680 --> 00:57:58,560 sell locally online. My question 1737 00:57:58,560 --> 00:58:01,760 for you is this: What more can 1738 00:58:01,760 --> 00:58:04,400 Woo achieve beyond the freedom 1739 00:58:04,400 --> 00:58:06,400 of empowerment and expression 1740 00:58:06,400 --> 00:58:08,160 for all to sell digitally? 1741 00:58:09,120 --> 00:58:11,200 Essentially, what's your vision 1742 00:58:11,200 --> 00:58:15,280 for Woo democratizing commerce 1743 00:58:15,280 --> 00:58:17,840 during this pandemic and beyond? 1744 00:58:20,000 --> 00:58:20,440 Thanks. 1745 00:58:20,440 --> 00:58:22,800 >> Hi, Winstina. My name is Paul 1746 00:58:22,800 --> 00:58:24,080 Maiorana. I'm the CEO here at 1747 00:58:24,080 --> 00:58:25,520 WooCommerce. Thank you for your 1748 00:58:25,520 --> 00:58:27,120 question and thank you for 1749 00:58:27,120 --> 00:58:28,160 everything you do to support 1750 00:58:28,160 --> 00:58:31,360 local businesses. We share that 1751 00:58:31,360 --> 00:58:33,280 mission, ultimately. So your 1752 00:58:33,280 --> 00:58:34,160 question couldn't be more 1753 00:58:34,160 --> 00:58:35,840 pertinent in a year like 2020 1754 00:58:35,840 --> 00:58:37,120 that has brought such hardship 1755 00:58:37,120 --> 00:58:38,320 to small businesses. 1756 00:58:38,880 --> 00:58:40,560 WooCommerce powers over 2 1757 00:58:40,560 --> 00:58:42,480 million stores on our platform, 1758 00:58:42,480 --> 00:58:43,600 and we take that role really 1759 00:58:43,600 --> 00:58:44,160 seriously. 1760 00:58:45,520 --> 00:58:47,440 One of the things that we've 1761 00:58:47,440 --> 00:58:49,520 been focused on this year, we 1762 00:58:49,520 --> 00:58:50,400 know that WordPress and 1763 00:58:50,400 --> 00:58:52,880 WooCommerce can often be - or 1764 00:58:52,880 --> 00:58:53,760 require a little bit of 1765 00:58:53,760 --> 00:58:55,360 technical knowledge, or even 1766 00:58:55,360 --> 00:58:56,560 just some courage to kind of get 1767 00:58:56,560 --> 00:58:57,840 up and running with if you're 1768 00:58:57,840 --> 00:58:58,880 less experienced with the 1769 00:58:58,880 --> 00:58:59,440 platforms. 1770 00:59:00,240 --> 00:59:02,080 And this year, especially this 1771 00:59:02,080 --> 00:59:04,640 year, stores may not necessarily 1772 00:59:04,640 --> 00:59:06,000 have the budget to go out and 1773 00:59:06,000 --> 00:59:08,320 hire that additional help. So, 1774 00:59:09,120 --> 00:59:11,120 we've been focused this year on 1775 00:59:11,120 --> 00:59:12,320 empowering merchants to be more 1776 00:59:12,320 --> 00:59:13,600 self-sufficient and removing 1777 00:59:13,600 --> 00:59:15,120 many of the obstacles that a 1778 00:59:15,120 --> 00:59:16,320 merchant might hit in getting 1779 00:59:16,320 --> 00:59:18,080 their store online and then 1780 00:59:18,080 --> 00:59:19,360 running and growing that store. 1781 00:59:21,440 --> 00:59:22,320 We've been focused on our 1782 00:59:22,320 --> 00:59:23,760 on-boarding for one, 1783 00:59:24,560 --> 00:59:26,240 streamlining the setup process 1784 00:59:26,240 --> 00:59:27,920 in configuration for Woo, such 1785 00:59:27,920 --> 00:59:29,200 that you can get to that first 1786 00:59:29,200 --> 00:59:30,400 sale that much more quickly. 1787 00:59:31,360 --> 00:59:32,960 We're redesigning the navigation 1788 00:59:32,960 --> 00:59:34,320 around WooCommerce to make it 1789 00:59:34,320 --> 00:59:35,600 that much more intuitive, again, 1790 00:59:35,600 --> 00:59:36,640 for folks who are maybe less 1791 00:59:36,640 --> 00:59:38,080 experienced with WooCommerce and 1792 00:59:38,080 --> 00:59:38,640 WordPress. 1793 00:59:40,480 --> 00:59:41,600 We've been investing big in the 1794 00:59:41,600 --> 00:59:43,600 Block Editor and bringing new 1795 00:59:43,600 --> 00:59:45,520 product blocks into WooCommerce 1796 00:59:45,520 --> 00:59:46,960 to enable our merchants to be, 1797 00:59:48,000 --> 00:59:49,360 again, more self-sufficient in 1798 00:59:49,360 --> 00:59:50,400 the way that they merchandise 1799 00:59:50,400 --> 00:59:51,440 their products and not have to 1800 00:59:51,440 --> 00:59:52,880 be reliant on a developer to 1801 00:59:52,880 --> 00:59:57,040 implement those promotions. And 1802 00:59:57,040 --> 00:59:58,000 we also know that it's not 1803 00:59:58,000 --> 00:59:59,040 enough to just get a store 1804 00:59:59,040 --> 01:00:00,720 online and kind of, you know, 1805 01:00:00,720 --> 01:00:02,720 operate the store. Our merchants 1806 01:00:02,720 --> 01:00:04,640 want to grow, so we need to help 1807 01:00:04,640 --> 01:00:06,080 them reach their customers, so 1808 01:00:06,080 --> 01:00:08,080 we've also been investing a lot 1809 01:00:08,080 --> 01:00:09,120 in improving the marketing 1810 01:00:09,120 --> 01:00:10,400 solutions that are available for 1811 01:00:10,400 --> 01:00:11,840 WooCommerce to help our 1812 01:00:11,840 --> 01:00:13,840 merchants grow their stores. So, 1813 01:00:13,840 --> 01:00:15,600 I hope that's helpful. Thank you 1814 01:00:15,600 --> 01:00:16,800 for contributing to WordPress. 1815 01:00:17,480 --> 01:00:20,480 >> Wow, that was a lot of 1816 01:00:20,480 --> 01:00:23,120 questions and answers. I really 1817 01:00:23,120 --> 01:00:24,800 appreciate everyone from the 1818 01:00:24,800 --> 01:00:26,000 community who helped answer the 1819 01:00:26,000 --> 01:00:28,560 questions. As always with 1820 01:00:28,560 --> 01:00:30,080 WordPress, these things are so 1821 01:00:30,080 --> 01:00:31,120 much better when we work 1822 01:00:31,120 --> 01:00:33,600 together, and it was exciting to 1823 01:00:33,600 --> 01:00:35,200 me to be able to do a 1824 01:00:35,200 --> 01:00:37,120 distributed and virtual version 1825 01:00:37,120 --> 01:00:38,320 of what happens sometimes at 1826 01:00:38,320 --> 01:00:40,320 Wordcamps when I'll pass the mic 1827 01:00:40,320 --> 01:00:41,600 to someone, usually in the front 1828 01:00:41,600 --> 01:00:42,880 row from the WordPress 1829 01:00:42,880 --> 01:00:44,240 community, who knows so much 1830 01:00:44,240 --> 01:00:45,520 more than I can and can answer 1831 01:00:45,520 --> 01:00:47,520 the question so much better. So 1832 01:00:47,520 --> 01:00:48,480 keep an eye out for these 1833 01:00:48,480 --> 01:00:50,400 recordings and captions and 1834 01:00:50,400 --> 01:00:51,600 more, which will be on 1835 01:00:51,600 --> 01:00:55,840 wordpress.tv and the WordPress 1836 01:00:55,840 --> 01:00:59,120 YouTube channel. With that, I 1837 01:00:59,120 --> 01:01:00,800 bid you adieu. Thank you so much 1838 01:01:00,800 --> 01:01:03,280 for tuning in. I am so 1839 01:01:03,280 --> 01:01:04,960 appreciative to the WordPress 1840 01:01:04,960 --> 01:01:06,800 community this year for being 1841 01:01:06,800 --> 01:01:09,920 just a place of stability and 1842 01:01:09,920 --> 01:01:11,680 strength. I really love and 1843 01:01:11,680 --> 01:01:13,840 appreciate you all. Thank you so 1844 01:01:13,840 --> 01:01:17,040 much and see you again online.