0:00:04.400,0:00:06.800
Hello. How do you see

0:00:06.800,0:00:09.760
WordPress integrating with voice

0:00:09.760,0:00:12.880
AI and 3D publishing on the web

0:00:12.880,0:00:15.920
in the future?

0:00:15.920,0:00:17.600
>> Abha, thank you very much for

0:00:17.600,0:00:20.320
that question. I haven't thought

0:00:20.320,0:00:22.160
too much about voice AI or 3D

0:00:22.160,0:00:24.240
publishing, but the good news is

0:00:24.240,0:00:25.600
that I don't need to for it to

0:00:25.600,0:00:27.360
be possible. WordPress has so

0:00:27.360,0:00:29.440
many great APIs. I have seen

0:00:29.440,0:00:31.440
demos before of people using

0:00:31.440,0:00:32.880
WordPress to power content

0:00:32.880,0:00:34.240
embedded in sort of virtual

0:00:34.240,0:00:36.480
worlds or things like Oculus,

0:00:37.040,0:00:39.360
and I have seen people use

0:00:39.360,0:00:41.000
WordPress to build kind of like

0:00:41.000,0:00:43.600
-- kind of like a voice menu

0:00:43.600,0:00:45.040
system for I believe it was

0:00:45.040,0:00:47.200
Alexa. So I know it's possible,

0:00:48.480,0:00:50.640
but we're probably a few years

0:00:50.640,0:00:52.320
away from that being in core.

0:00:52.320,0:00:53.600
And if there's anything that

0:00:53.600,0:00:54.880
I've missed that I should check

0:00:54.880,0:00:57.840
out, please send it my way.

0:00:57.840,0:00:59.600
>> I'm Christina Workman from

0:00:59.600,0:01:01.600
Calgary, Canada. I'm a designer,

0:01:01.600,0:01:03.440
developer, enduser and

0:01:03.440,0:01:05.360
contributor. We saw with the

0:01:05.360,0:01:07.680
release of WordPress 5.6 that

0:01:07.680,0:01:09.520
over 600 people contributed to

0:01:09.520,0:01:11.280
track tickets and GitHub pull

0:01:11.280,0:01:12.960
requests, all mentioned by name.

0:01:13.520,0:01:14.960
As well as numerous volunteers

0:01:14.960,0:01:16.160
contributing in the support

0:01:16.160,0:01:18.080
forums and translating to make

0:01:18.080,0:01:20.800
5.6 available in 38 languages,

0:01:20.800,0:01:22.880
although unnamed. There's no

0:01:22.880,0:01:24.320
doubt these volunteers are doing

0:01:24.320,0:01:26.800
great work which is supported by

0:01:26.800,0:01:28.320
thousands of other contributors

0:01:28.320,0:01:30.080
volunteering their time outside

0:01:30.080,0:01:31.520
of core releases throughout the

0:01:31.520,0:01:33.840
year every year who don't get

0:01:33.840,0:01:35.600
any recognition outside of their

0:01:35.600,0:01:37.520
inner circles. Publicly

0:01:37.520,0:01:38.880
acknowledging the variety of

0:01:38.880,0:01:40.880
contributor roles available goes

0:01:40.880,0:01:42.560
a long way to increasing our

0:01:42.560,0:01:44.080
community's awareness that these

0:01:44.080,0:01:45.440
roles exist for them to

0:01:45.440,0:01:47.760
participate in. What plans are

0:01:47.760,0:01:49.040
there for recognizing

0:01:49.040,0:01:50.800
contributions made by those who

0:01:50.800,0:01:52.640
contribute to any team

0:01:52.640,0:01:54.640
throughout the year, even those

0:01:54.640,0:01:56.240
not involved in a core release?

0:01:56.880,0:01:57.380
Thank you.

0:01:59.240,0:02:01.840
>> Christina, this was an

0:02:01.840,0:02:03.520
excellent question, and I do

0:02:03.520,0:02:05.680
agree that recognition is a

0:02:05.680,0:02:07.200
fantastic way to get more people

0:02:07.200,0:02:08.560
contributing to the things that

0:02:08.560,0:02:10.880
we're doing. The WordPress

0:02:10.880,0:02:12.800
release post and of course the

0:02:13.360,0:02:15.280
core itself is probably better

0:02:15.280,0:02:17.520
at recognizing core itself and

0:02:17.520,0:02:18.800
contributors there than anything

0:02:18.800,0:02:22.080
else. One thing we did build to

0:02:22.080,0:02:23.600
improve this was the badge

0:02:23.600,0:02:25.600
system on profiles. So if you go

0:02:25.600,0:02:27.040
to profiles.wordpress.org/Matt,

0:02:27.920,0:02:28.800
you'll see there are a number of

0:02:28.800,0:02:30.800
badges there at the very top

0:02:30.800,0:02:31.840
that show all the different

0:02:31.840,0:02:33.680
things that I've done and

0:02:33.680,0:02:34.720
contributed to the WordPress

0:02:34.720,0:02:36.320
community. I think there might

0:02:36.320,0:02:38.720
be a bug there, because it shows

0:02:38.720,0:02:40.320
that I am a translation editor

0:02:40.320,0:02:42.160
and I am unable to speak any

0:02:42.160,0:02:44.800
language besides English. And

0:02:44.800,0:02:46.000
even English I struggle with

0:02:46.000,0:02:48.560
sometimes, so -- but I noticed

0:02:48.560,0:02:49.840
that on these badges, there's no

0:02:49.840,0:02:50.960
way to click on them and see all

0:02:50.960,0:02:52.000
the other people that have the

0:02:52.000,0:02:53.680
same badges. So that could be a

0:02:53.680,0:02:56.000
really nice start to having

0:02:56.000,0:02:58.000
pages that recognize folks,

0:02:58.000,0:02:59.360
particularly folks whose work

0:03:00.240,0:03:01.440
isn't just tied to a single

0:03:01.440,0:03:05.200
release within WordPress.org and

0:03:05.200,0:03:06.080
it could have some sort of

0:03:06.080,0:03:08.000
natural decay function so, you

0:03:08.000,0:03:08.720
know, if you haven't done

0:03:08.720,0:03:10.240
anything for an amount of time,

0:03:10.240,0:03:11.440
maybe you drop off the list.

0:03:12.160,0:03:13.040
That would be, I think, a very

0:03:13.040,0:03:14.640
natural place to start to add it

0:03:14.640,0:03:15.520
and we'll look into it.

0:03:15.520,0:03:17.040
Excellent suggestion and thank

0:03:17.040,0:03:17.840
you very much.

0:03:17.840,0:03:19.840
>> Hi, Matt. I'm Courtney

0:03:19.840,0:03:20.880
Robertson with the training

0:03:20.880,0:03:22.720
team. You recently shared an

0:03:22.720,0:03:24.160
article from ZDNet that

0:03:24.160,0:03:27.600
indicates an 834% rise in PHP

0:03:27.600,0:03:29.840
developer jobs since January of

0:03:29.840,0:03:32.560
2020. It's fair to assume that

0:03:32.560,0:03:33.840
some of that would be WordPress

0:03:33.840,0:03:36.560
developer-related jobs. W3Techs

0:03:37.360,0:03:39.200
indicates that WordPress powers

0:03:39.200,0:03:41.760
over 39.3% of all websites

0:03:41.760,0:03:44.560
online, surpassing 38.5% of

0:03:44.560,0:03:46.080
websites that have no content

0:03:46.080,0:03:48.560
management system at all. Given

0:03:48.560,0:03:50.000
those stats, what role do you

0:03:50.000,0:03:51.520
see for employers in the

0:03:51.520,0:03:53.840
WordPress.org ecosystem as it

0:03:53.840,0:03:54.560
relates to the

0:03:54.560,0:03:57.840
learn.wordpress.org website? How

0:03:57.840,0:03:59.520
do you think that the learned

0:03:59.520,0:04:01.920
platform can address hiring,

0:04:01.920,0:04:04.000
skills and ongoing professional

0:04:04.000,0:04:04.880
development needs?

0:04:06.360,0:04:08.240
>> Thank you, Courtney, for

0:04:08.240,0:04:09.760
highlighting those stats, and

0:04:09.760,0:04:10.960
also thank you for the awesome

0:04:10.960,0:04:12.320
WordPress swag you have in your

0:04:12.320,0:04:13.680
background. One cool thing about

0:04:13.680,0:04:15.040
this format is it's really neat

0:04:15.040,0:04:17.040
to see people where they are,

0:04:17.040,0:04:18.080
not just us all being in the

0:04:18.080,0:04:20.400
same auditorium. You know, for

0:04:20.400,0:04:22.640
Learn, I think the first step is

0:04:22.640,0:04:24.480
really just organizing and

0:04:24.480,0:04:26.160
getting really high-quality

0:04:26.160,0:04:27.840
educational material up there.

0:04:28.560,0:04:29.680
The equivalent -- like if you

0:04:29.680,0:04:30.960
were going to take a university

0:04:30.960,0:04:32.640
course on WordPress. How do we

0:04:32.640,0:04:34.880
walk you from just learning the

0:04:34.880,0:04:36.480
basics all the way up to being

0:04:36.480,0:04:38.400
able to be able to customize and

0:04:38.400,0:04:40.080
basically be a WordPress pro, so

0:04:40.080,0:04:41.120
you could build sites for other

0:04:41.120,0:04:43.360
people and be kind of like an

0:04:43.360,0:04:45.840
expert. Down the line, it would

0:04:45.840,0:04:48.400
be great if this platform could

0:04:48.400,0:04:49.280
have some sort of

0:04:49.920,0:04:51.600
self-certification or perhaps

0:04:51.600,0:04:53.040
even some sort of administered

0:04:53.680,0:04:55.520
certification that could show

0:04:55.520,0:04:56.480
people that, you know, you

0:04:56.480,0:04:58.480
mastered a certain skill. That

0:04:58.480,0:05:00.320
you, you know, went through --

0:05:00.320,0:05:01.760
either you went through lessons

0:05:01.760,0:05:02.640
or you didn't need to, but you

0:05:02.640,0:05:03.680
were able to, like, take a test

0:05:03.680,0:05:05.200
at the end and show that you

0:05:05.200,0:05:06.320
were competent in this. It

0:05:06.320,0:05:07.600
wouldn't be a perfect system,

0:05:07.600,0:05:09.680
but it could be a nice way for

0:05:09.680,0:05:11.840
people to learn more about

0:05:11.840,0:05:13.600
WordPress and hopefully as they

0:05:13.600,0:05:14.720
go through, since WordPress is

0:05:14.720,0:05:16.000
open source, improve the

0:05:16.000,0:05:18.160
materials as we go through it,

0:05:18.160,0:05:19.360
both from the point of view of

0:05:19.360,0:05:20.560
making it more intuitive or

0:05:20.560,0:05:21.840
easier to understand, and then

0:05:21.840,0:05:23.280
also translating, as well.

0:05:23.280,0:05:24.640
Because there is huge demand for

0:05:24.640,0:05:25.840
WordPress really all over the

0:05:25.840,0:05:26.320
world now.

0:05:26.320,0:05:28.480
>> Hey, Matt. Dan Maby here from

0:05:28.480,0:05:30.640
Big Orange Hearts, a charity

0:05:30.640,0:05:31.680
providing well-being and mental

0:05:31.680,0:05:32.880
health support for remote

0:05:32.880,0:05:34.960
workers. To support our mission,

0:05:34.960,0:05:36.400
we deliver events to help reduce

0:05:36.400,0:05:38.320
social isolation for those

0:05:38.320,0:05:40.720
working remotely. With more than

0:05:40.720,0:05:41.840
12,000 attendees through our

0:05:41.840,0:05:43.840
virtual event platform built on

0:05:43.840,0:05:45.040
open source technologies this

0:05:45.040,0:05:47.200
year, I wanted to ask about your

0:05:47.200,0:05:48.640
vision for events within the

0:05:48.640,0:05:50.080
WordPress community through

0:05:50.080,0:05:52.800
2021. As a regular WordCamp and

0:05:52.800,0:05:54.880
meetup organizer myself, I also

0:05:54.880,0:05:56.480
wanted to ask your thoughts on

0:05:56.480,0:05:58.480
responsibility towards safety of

0:05:58.480,0:06:01.040
attendees and fellow organizers

0:06:01.040,0:06:02.160
as we start to take steps

0:06:02.160,0:06:05.040
towards a vaccinated era. And,

0:06:05.040,0:06:06.720
finally, with virtual events

0:06:06.720,0:06:07.920
offering a great level of

0:06:07.920,0:06:10.240
accessibility for attendees, do

0:06:10.240,0:06:11.760
you see the potential for a

0:06:11.760,0:06:13.200
hybrid approach towards

0:06:13.200,0:06:15.600
WordCamps in the future? Thanks

0:06:15.600,0:06:16.100
for your time.

0:06:18.520,0:06:21.760
>> Hi, Dan. Andrea here. Thanks

0:06:21.760,0:06:24.480
for asking this question. It's

0:06:24.480,0:06:26.000
been inspirational to watch

0:06:26.000,0:06:28.000
WordPress community organizers

0:06:28.000,0:06:30.160
rise to the challenges that this

0:06:30.160,0:06:31.840
horrible pandemic has brought,

0:06:31.840,0:06:34.080
especially since so many of us

0:06:34.080,0:06:37.120
love this work because we love

0:06:37.120,0:06:39.840
seeing each other in person and

0:06:39.840,0:06:42.160
we know how powerful those

0:06:42.160,0:06:44.160
face-to-face, in-person

0:06:44.160,0:06:46.640
interactions can really be. And

0:06:46.640,0:06:48.480
like other WordPressers, I am

0:06:48.480,0:06:50.160
really eager to get back to

0:06:50.160,0:06:52.160
those in-person events, just as

0:06:52.160,0:06:55.120
soon as it's safe. All that

0:06:55.120,0:06:56.640
said, and as you point out,

0:06:58.000,0:07:00.800
moving all of our events online

0:07:00.800,0:07:02.240
has made them much more

0:07:02.240,0:07:04.880
accessible, especially to those

0:07:04.880,0:07:07.280
who either can't travel or don't

0:07:07.280,0:07:09.360
wish to travel to our in-person

0:07:09.360,0:07:12.880
events. When I think about our

0:07:12.880,0:07:16.880
return to in-person events, I

0:07:16.880,0:07:19.200
think that some sort of hybrid

0:07:19.200,0:07:21.680
element will be necessary,

0:07:21.680,0:07:22.800
especially in those first

0:07:22.800,0:07:25.280
stages. But I also know that

0:07:25.280,0:07:26.800
hybrid events are much more

0:07:26.800,0:07:29.840
expensive, and so yet again

0:07:30.480,0:07:31.760
we're gonna be hoping and

0:07:31.760,0:07:33.360
looking for WordPressers who

0:07:34.480,0:07:36.240
want to take the opportunity to

0:07:36.240,0:07:39.440
really look for innovative ways

0:07:39.440,0:07:40.880
to make our community events

0:07:40.880,0:07:44.800
accessible at scale. I don't

0:07:44.800,0:07:47.600
know all the answers here, but I

0:07:47.600,0:07:49.120
know that some of the smartest

0:07:49.120,0:07:51.280
people -- that I know, at least

0:07:51.280,0:07:52.080
--

0:07:52.080,0:07:53.920
are in WordPress, and I'm really

0:07:53.920,0:07:57.280
looking forward to work on this

0:07:57.280,0:07:58.320
together with the global

0:07:58.320,0:08:01.040
community team. I hope that's

0:08:01.040,0:08:02.640
helpful. Thanks for all that you

0:08:02.640,0:08:03.680
do for WordPress and the

0:08:03.680,0:08:05.520
WordPress community. I hope to

0:08:05.520,0:08:06.080
see you soon.

0:08:06.760,0:08:08.960
>> Hi, Matt. I'm Dave from

0:08:08.960,0:08:10.400
Belgium. Almost 15 years

0:08:10.400,0:08:11.920
building sites professionally

0:08:11.920,0:08:13.520
with ten years on WordPress

0:08:13.520,0:08:15.360
websites. Hope you're okay and

0:08:15.360,0:08:16.960
Happy Christmas in advance for

0:08:16.960,0:08:19.280
everyone listening. Well,

0:08:19.280,0:08:20.560
WordPress is in its nature a

0:08:20.560,0:08:22.240
very clean, no-overkill-on-

0:08:22.240,0:08:24.000
options kind of software, and

0:08:24.000,0:08:25.200
thankfully this created our

0:08:25.200,0:08:27.360
beloved WordPress ecosystem. It

0:08:27.360,0:08:29.040
also created momentum for page

0:08:29.040,0:08:30.720
builders like Elementer to arise

0:08:30.720,0:08:32.880
with enormous success. And the

0:08:32.880,0:08:34.880
reason for that is simple: The

0:08:34.880,0:08:36.720
user got all the options. Just

0:08:36.720,0:08:38.160
to mention a few to make my

0:08:38.160,0:08:39.840
question more specific, I'm

0:08:39.840,0:08:41.920
talking about layout, padding,

0:08:41.920,0:08:44.160
margin, desktop versus mobile,

0:08:44.160,0:08:47.040
and tablet and so on. Now, the

0:08:47.040,0:08:48.960
Block Editor is right now also

0:08:48.960,0:08:50.640
that kind of no-overkill-on-

0:08:50.640,0:08:52.720
options kind of software. Some

0:08:52.720,0:08:54.400
like that. I totally understand

0:08:54.400,0:08:56.640
that, but some don't. The

0:08:56.640,0:08:58.400
question is, how far do you

0:08:58.400,0:09:00.880
think the core blocks must go in

0:09:00.880,0:09:02.960
those kinds of customization to

0:09:02.960,0:09:04.880
please the mass non-tech

0:09:04.880,0:09:06.720
audience because if you look

0:09:06.720,0:09:08.480
back, honestly, that's what they

0:09:08.480,0:09:10.160
want, that's what they choose.

0:09:10.160,0:09:11.680
Or would you rather keep that

0:09:11.680,0:09:14.080
WordPress simplicity again to

0:09:14.080,0:09:15.760
leave the door open for the next

0:09:15.760,0:09:17.520
block page builder plug-in to

0:09:17.520,0:09:18.020
arise.

0:09:18.720,0:09:20.480
So how dependent on a

0:09:20.480,0:09:22.720
third-party layout plug-in do

0:09:22.720,0:09:24.160
you want the WordPress block

0:09:24.160,0:09:26.080
user to be? Thank you.

0:09:27.560,0:09:30.320
>> Hello, Dave. You bring up an

0:09:30.320,0:09:31.760
interesting point, which is that

0:09:31.760,0:09:33.840
we're trying to walk a very fine

0:09:33.840,0:09:35.840
line between creating something

0:09:35.840,0:09:37.360
which is intuitive and easy to

0:09:37.360,0:09:40.320
use, and also providing the

0:09:40.320,0:09:41.440
customization that people

0:09:41.440,0:09:43.360
clearly want in WordPress. While

0:09:43.360,0:09:44.560
also trying to do something

0:09:44.560,0:09:46.080
which has never really been done

0:09:46.080,0:09:49.120
before, which is provide a "what

0:09:49.120,0:09:50.160
you see is what you get"

0:09:50.160,0:09:51.840
WYSIWYG-style interface that,

0:09:51.840,0:09:53.280
again, is intuitive and easy to

0:09:53.280,0:09:55.760
use in lay out, but that also

0:09:55.760,0:09:57.520
creates really semantic markup,

0:09:58.560,0:10:01.040
structured data, and is fast and

0:10:01.040,0:10:01.600
performant.

0:10:03.200,0:10:04.080
I don't know if you've seen any

0:10:04.080,0:10:05.360
of the comparisons on the web

0:10:05.360,0:10:08.320
between WordPress with Gutenberg

0:10:08.320,0:10:09.680
versus other page filters or

0:10:09.680,0:10:11.600
other proprietary CMSs. That

0:10:11.600,0:10:13.280
page building and functionality.

0:10:13.280,0:10:14.320
Gutenberg blows them out of the

0:10:14.320,0:10:16.160
water. It is really fast, really

0:10:16.160,0:10:19.440
clean markup, really lean. This

0:10:19.440,0:10:21.760
is taking a little longer to do,

0:10:21.760,0:10:23.120
right, to do it right, it's

0:10:23.120,0:10:24.080
taking longer, but I believe

0:10:24.080,0:10:25.520
it's the right long-term

0:10:25.520,0:10:27.280
investment in both the future of

0:10:27.280,0:10:28.320
WordPress and the future of the

0:10:28.320,0:10:31.440
web. In terms of customization,

0:10:31.440,0:10:32.560
I believe there will always be

0:10:32.560,0:10:34.480
space for not just one plug-in

0:10:34.480,0:10:35.840
but many, many, many plug-ins to

0:10:35.840,0:10:38.320
extend Gutenberg. And that is

0:10:38.320,0:10:40.400
really the idea, that by --

0:10:40.400,0:10:42.720
where before we had, you know,

0:10:42.720,0:10:44.560
lots and lots of different page

0:10:44.560,0:10:46.080
builders kind of having their

0:10:46.080,0:10:47.200
own data structures, their own

0:10:47.200,0:10:49.680
way to do essentially the same

0:10:49.680,0:10:51.040
thing from a user point of view,

0:10:51.040,0:10:52.160
and themes would have to build

0:10:52.160,0:10:53.520
to one, SEO plug-ins would have

0:10:53.520,0:10:55.200
to build to each one. We're

0:10:55.200,0:10:56.880
trying to provide common rails

0:10:56.880,0:11:00.160
or framework that every vision

0:11:00.160,0:11:01.680
for how page-building could work

0:11:01.680,0:11:03.200
on top of WordPress can leverage

0:11:03.200,0:11:03.840
these blocks.

0:11:03.840,0:11:05.360
In fact, blocks are even built

0:11:05.360,0:11:06.800
so that other CMSs can leverage

0:11:06.800,0:11:09.040
them, too. So that is the path

0:11:09.040,0:11:09.680
we are on.

0:11:10.400,0:11:11.680
It's the way WordPress is going.

0:11:11.680,0:11:12.960
I believe it's the future. I

0:11:12.960,0:11:14.080
hope that as many people get on

0:11:14.080,0:11:15.920
that train as possible, but if

0:11:15.920,0:11:17.040
not, I do believe it is

0:11:17.040,0:11:17.600
inevitable.

0:11:17.600,0:11:19.040
>> Hey, Matt, this is Doc from

0:11:19.040,0:11:20.480
"Torque" magazine. I'm wondering

0:11:20.480,0:11:22.240
what features for core are you

0:11:22.240,0:11:23.840
targeting to make WordPress a

0:11:23.840,0:11:25.120
better headless experience in

0:11:25.120,0:11:25.840
2021?

0:11:26.520,0:11:28.640
>> First, I have to say, I don't

0:11:28.640,0:11:29.840
love the term "headless."

0:11:29.840,0:11:31.040
I like called it "decoupled

0:11:31.040,0:11:32.240
WordPress" because who wants to

0:11:32.240,0:11:34.400
be headless? But by and far, the

0:11:34.400,0:11:35.520
thing that's been driving the

0:11:35.520,0:11:36.960
most improvements to our APIs

0:11:37.680,0:11:38.640
has been our first-priority

0:11:38.640,0:11:40.160
usage of them. So, with

0:11:40.160,0:11:41.760
Gutenberg, built on and using

0:11:41.760,0:11:43.200
the REST API, and, of course,

0:11:43.200,0:11:45.600
our mobile apps, both Android

0:11:45.600,0:11:47.680
and iOS, you know, a million

0:11:47.680,0:11:50.000
active users, all running

0:11:50.000,0:11:52.880
through the APIs. So that has

0:11:52.880,0:11:54.800
helped expose a ton of bugs and

0:11:54.800,0:11:56.880
a ton of other areas where we

0:11:56.880,0:11:58.720
can improve it. I'm keeping my

0:11:58.720,0:12:00.560
eye on the GraphQL plug-in. I

0:12:00.560,0:12:01.520
think that that is an

0:12:01.520,0:12:04.800
interesting possible next step

0:12:04.800,0:12:07.600
after REST to support either as

0:12:07.600,0:12:09.520
a more official plug-in, or just

0:12:09.520,0:12:10.480
something that we point people

0:12:10.480,0:12:11.920
to because it seems to be doing

0:12:11.920,0:12:15.120
well. You know, I was actually

0:12:15.120,0:12:16.400
-- I don't think that a

0:12:16.400,0:12:17.600
decoupled architecture or

0:12:17.600,0:12:18.960
"headless" sites are right for

0:12:18.960,0:12:21.200
everything. I think they're

0:12:21.200,0:12:22.960
right in certain situations, but

0:12:23.520,0:12:26.320
as I am quoted with saying, they

0:12:26.320,0:12:27.840
are probably a regression for

0:12:27.840,0:12:29.120
many of the people adopting

0:12:29.120,0:12:30.960
them. I actually had a really

0:12:30.960,0:12:32.640
good debate about this at the

0:12:32.640,0:12:34.960
Netlifly JAMStack Conference

0:12:34.960,0:12:37.040
with Matt Billman, but I guess

0:12:37.040,0:12:38.000
it was too good because they

0:12:38.000,0:12:39.840
elected not to post it, but

0:12:39.840,0:12:41.200
perhaps you can track down a

0:12:41.200,0:12:43.360
recording or something, and hear

0:12:43.360,0:12:44.640
some more of my thoughts about

0:12:45.520,0:12:47.120
decoupled architectures and

0:12:47.120,0:12:48.280
WordPress there.

0:12:48.280,0:12:50.720
>> Hi, Matt. My name is George

0:12:50.720,0:12:52.400
Alger. I've been a WordPress

0:12:52.400,0:12:55.600
user since 2007, and I've been

0:12:55.600,0:12:57.280
watching State of the Word for a

0:12:57.280,0:12:59.440
number of years. My question has

0:12:59.440,0:13:02.000
to do with Gutenberg versus page

0:13:02.000,0:13:04.400
builders, and more specifically

0:13:04.400,0:13:07.360
regarding page load speed. I'm

0:13:07.360,0:13:10.480
wondering, as Gutenberg in the

0:13:10.480,0:13:12.960
future adds more and more

0:13:12.960,0:13:15.760
features, do you anticipate that

0:13:15.760,0:13:17.440
the page load speeds for

0:13:17.440,0:13:21.280
Gutenberg will also slow down to

0:13:21.920,0:13:24.960
support the new features? All

0:13:24.960,0:13:26.240
right. Thanks for all you do.

0:13:26.240,0:13:26.640
Bye-bye.

0:13:26.640,0:13:29.120
>> So, George, my name is Riad

0:13:29.120,0:13:30.640
Benguella. I am a developer on

0:13:30.640,0:13:32.800
the Gutenberg team. It's an

0:13:32.800,0:13:34.240
interesting question you bring

0:13:34.240,0:13:36.880
here related to performance. As

0:13:36.880,0:13:38.160
you can see with the different

0:13:38.160,0:13:40.560
WordPress releases since the

0:13:40.560,0:13:42.560
initial release of the core --

0:13:42.560,0:13:44.960
the Block Editor in WordPress,

0:13:44.960,0:13:46.400
the performance of the editor

0:13:46.400,0:13:49.280
have been improving, even if we

0:13:49.280,0:13:51.200
were adding features at the same

0:13:51.200,0:13:53.760
time. So, it's definitely a big

0:13:53.760,0:13:55.440
priority for us, and for the

0:13:55.440,0:13:56.720
front end and the page load

0:13:56.720,0:13:58.480
speed, we've been approaching

0:13:58.480,0:14:00.320
that in a few different ways.

0:14:00.320,0:14:01.520
The first one is the block

0:14:01.520,0:14:03.360
markup. We are trying to make

0:14:03.360,0:14:05.120
sure the block markup is as

0:14:05.120,0:14:08.000
clean as possible, and also the

0:14:08.000,0:14:09.040
interesting thing is that

0:14:09.040,0:14:10.880
Gutenberg brings semantics to

0:14:10.880,0:14:12.240
the content that is being

0:14:12.240,0:14:14.320
rendered. So WordPress can know

0:14:14.320,0:14:16.080
exactly what blocks are being

0:14:16.080,0:14:18.000
rendered, what assets they need,

0:14:18.000,0:14:19.920
what CSS, what JavaScripts they

0:14:19.920,0:14:22.080
need, and, in fact, recently, we

0:14:22.080,0:14:23.360
landed the pull request that

0:14:23.360,0:14:25.680
allows us to only load the CSS

0:14:25.680,0:14:27.120
of the blocks that are actually

0:14:27.120,0:14:28.400
in need in the currently

0:14:28.400,0:14:31.120
rendered page, and this opens a

0:14:31.120,0:14:32.320
lot of possibilities. For

0:14:32.320,0:14:33.520
example, in the future, we may

0:14:33.520,0:14:35.280
do the same for JavaScript and

0:14:35.280,0:14:39.600
lazy-load blocks. When we expand

0:14:39.600,0:14:41.600
that to full site editing where

0:14:41.600,0:14:44.160
a theme is basically composed

0:14:44.160,0:14:46.400
entirely of blocks, you can

0:14:46.400,0:14:48.240
imagine that the CSS and the

0:14:48.240,0:14:50.240
JavaScript provided by the teams

0:14:50.240,0:14:52.320
themselves won't be as necessary

0:14:52.320,0:14:52.880
as today.

0:14:53.440,0:14:55.680
So I think we have a big

0:14:55.680,0:14:57.520
opportunity here to actually

0:14:57.520,0:14:59.440
improve the performance of all

0:14:59.440,0:15:01.360
the WordPress websites and not

0:15:01.360,0:15:03.360
decrease it as we add features.

0:15:03.360,0:15:03.860
Thank you.

0:15:04.680,0:15:07.120
>> Hi, Matt. I'm Hitha from

0:15:07.120,0:15:09.040
India. I'm a project manager,

0:15:09.040,0:15:11.600
mainly working with a group of

0:15:11.600,0:15:14.640
WordPress developers. My

0:15:14.640,0:15:16.320
question for you today is a

0:15:16.320,0:15:21.120
simple one. In the recent

0:15:21.120,0:15:23.440
releases, we have a lot of new

0:15:23.440,0:15:25.360
features and advancement in

0:15:25.360,0:15:28.960
WordPress, but as an end user or

0:15:28.960,0:15:31.040
maybe a content manager, have

0:15:31.040,0:15:33.440
you ever felt like it would be

0:15:33.440,0:15:35.280
good to have a more modern

0:15:35.280,0:15:37.360
design for the back end, and if

0:15:37.360,0:15:38.880
it would have been good if we

0:15:38.880,0:15:41.040
had more customization options

0:15:41.040,0:15:42.640
just for the back end? Have you

0:15:42.640,0:15:44.680
ever felt so? Thanks.

0:15:44.680,0:15:47.280
>> Hello, Hitha. I'm Joen from

0:15:47.280,0:15:48.960
Denmark. I worked a little bit

0:15:48.960,0:15:50.320
on the Block Editor design.

0:15:50.320,0:15:51.760
Thank you for your question.

0:15:51.760,0:15:53.440
I'll try to answer it as best I

0:15:53.440,0:15:58.000
can. As you suggest, WordPress

0:15:58.000,0:15:59.440
has landed many features in

0:15:59.440,0:16:01.760
recent releases, but very few

0:16:01.760,0:16:03.440
changes to the dashboard

0:16:03.440,0:16:05.040
visuals. If you're asking

0:16:05.040,0:16:06.480
whether that's gonna change, my

0:16:06.480,0:16:08.320
answer is I'd like to see that

0:16:08.320,0:16:10.880
very much. One of the challenges

0:16:10.880,0:16:12.320
to making that happen is that

0:16:12.320,0:16:14.160
the dashboard as it exists has

0:16:14.160,0:16:17.120
been customized by a great deal

0:16:17.120,0:16:20.160
of plug-ins and developers, and

0:16:20.160,0:16:21.920
although it is complicated to

0:16:21.920,0:16:24.800
new users, the fact that it's

0:16:24.800,0:16:26.720
been unchanged for so long means

0:16:26.720,0:16:29.200
that it's familiar to existing

0:16:29.200,0:16:32.160
users. That means whatever

0:16:32.160,0:16:33.840
changes we make have to be

0:16:33.840,0:16:35.600
rolled out carefully and in

0:16:35.600,0:16:38.240
small iterations. But my hope is

0:16:38.240,0:16:40.400
that over time those iterations

0:16:40.400,0:16:43.280
can add up. For example, the

0:16:43.280,0:16:44.880
Block Editor, we have a new icon

0:16:44.880,0:16:47.280
set and a new set of components,

0:16:47.280,0:16:48.960
user interface controls.

0:16:50.400,0:16:51.360
Although technically

0:16:51.360,0:16:52.640
challenging, if we could roll

0:16:52.640,0:16:54.000
those out to the rest of the

0:16:54.000,0:16:56.000
dashboard, it would bring a

0:16:56.000,0:16:57.280
great deal of improvements to

0:16:57.280,0:16:59.680
both accessibility and visual

0:16:59.680,0:17:01.600
simplicity. So I'd like to see

0:17:01.600,0:17:04.240
that happen. You also ask about

0:17:04.240,0:17:06.560
customization options, and the

0:17:06.560,0:17:08.400
thing is, WordPress is a lot of

0:17:08.400,0:17:10.320
things to a lot of people, and

0:17:10.880,0:17:12.720
customization options beyond

0:17:12.720,0:17:14.800
color schemes might help tailor

0:17:14.800,0:17:17.920
the interface to each group. I

0:17:17.920,0:17:19.440
would suggest, though, that the

0:17:19.440,0:17:20.880
first step to take would be to

0:17:20.880,0:17:23.600
make general user interface

0:17:23.600,0:17:25.120
enhancement because that would

0:17:25.120,0:17:27.360
benefit everyone, but after

0:17:27.360,0:17:29.040
that, absolutely, we could look

0:17:29.040,0:17:31.920
at customization options. I hope

0:17:31.920,0:17:33.920
that answers your question, and

0:17:33.920,0:17:36.000
thank you again for your time.

0:17:36.840,0:17:39.760
>> Hey, Matt. Jeroen here from

0:17:39.760,0:17:41.680
Belgium. Thank you for taking

0:17:41.680,0:17:43.440
the State of the Word online

0:17:43.440,0:17:45.600
this year. I'm using WordPress

0:17:45.600,0:17:46.960
for all of the websites I

0:17:46.960,0:17:48.440
develop with my company Site

0:17:48.440,0:17:49.760
Fly, and I'm an active

0:17:50.320,0:17:52.000
contributor to the WordPress

0:17:52.000,0:17:54.320
project. You mentioned before

0:17:54.320,0:17:56.480
that in Phase 4 of the Gutenberg

0:17:57.840,0:17:59.840
project, that multilingual

0:17:59.840,0:18:01.360
features are coming to WordPress

0:18:01.360,0:18:04.160
core. I know this is in the

0:18:04.160,0:18:06.080
future, but is there any public

0:18:06.080,0:18:07.680
roadmap of all the features and

0:18:07.680,0:18:10.000
functionalities we want in

0:18:10.000,0:18:14.160
WordPress? And is it going to

0:18:14.160,0:18:16.880
include a language fallback into

0:18:16.880,0:18:18.400
core so we can configure

0:18:18.400,0:18:20.160
multiple locales and the

0:18:20.160,0:18:21.600
fallback when a translation is

0:18:21.600,0:18:23.280
not on wordpress.org?

0:18:24.640,0:18:26.560
Currently as a contributor to

0:18:26.560,0:18:28.240
the polyglots team, I find it

0:18:28.240,0:18:29.760
very difficult to translate

0:18:31.120,0:18:32.320
thousands of plug-ins and

0:18:32.320,0:18:35.040
themes, and I would love that

0:18:35.040,0:18:37.120
fallback to another locale would

0:18:37.120,0:18:38.560
be there before it goes to

0:18:38.560,0:18:39.060
English.

0:18:41.120,0:18:42.400
Currently, I'm using Preferred

0:18:42.400,0:18:45.680
Languages as a plug-in for this,

0:18:45.680,0:18:47.040
but it would be very cool if

0:18:47.040,0:18:48.560
this would be included in

0:18:48.560,0:18:50.240
WordPress core. Thank you for

0:18:50.240,0:18:51.320
answering my question.

0:18:51.320,0:18:53.760
>> Hello, Jeroen. I'm Matias

0:18:53.760,0:18:55.440
Ventura helping lead the

0:18:55.440,0:18:56.640
Gutenberg project forwards.

0:18:57.280,0:18:58.480
Thank you for your question and

0:18:58.480,0:18:59.920
for contributing to the project.

0:19:01.280,0:19:03.520
Regarding the roadmap, there is

0:19:03.520,0:19:05.360
a public roadmap published in

0:19:05.360,0:19:09.600
wordpress.org/about/roadmap that

0:19:09.600,0:19:11.200
has sort of like an overview of

0:19:11.200,0:19:13.840
the next immediate steps, and it

0:19:13.840,0:19:15.600
touches upon the four phases of

0:19:15.600,0:19:17.200
Gutenberg as well. And what it

0:19:17.200,0:19:18.560
doesn't contain, though, is a

0:19:18.560,0:19:20.640
detailed plan on Phase 4

0:19:20.640,0:19:22.160
specifically, multilingual,

0:19:23.200,0:19:25.200
because it's fairly further

0:19:25.200,0:19:26.640
ahead for us and we're in the

0:19:26.640,0:19:29.920
thick of Phase 2. However, like,

0:19:30.800,0:19:31.920
there has been some

0:19:31.920,0:19:33.920
conversations around the

0:19:33.920,0:19:36.000
implications of localization

0:19:36.000,0:19:37.600
and some of the multilingual

0:19:37.600,0:19:39.840
aspects, specifically around

0:19:40.480,0:19:42.240
patterns and block themes and

0:19:42.240,0:19:43.840
how those could be built in the

0:19:43.840,0:19:46.160
Gutenberg repository. Nothing

0:19:46.160,0:19:47.920
substantial yet, but if you are

0:19:47.920,0:19:48.640
interested in those

0:19:48.640,0:19:49.840
conversations, that's a good

0:19:49.840,0:19:52.080
place to engage with and start

0:19:52.080,0:19:54.960
looking at. But, yeah, like as

0:19:54.960,0:19:56.400
we approach -- as we get closer

0:19:56.400,0:19:58.240
to Phase 4, we will have a more

0:19:58.240,0:19:59.600
detailed overview of what's

0:19:59.600,0:20:01.440
needed, what requirements and

0:20:01.440,0:20:04.240
what we want to do. Regarding

0:20:04.240,0:20:06.000
the other topic about fallback

0:20:06.000,0:20:07.920
languages, that's a very good

0:20:07.920,0:20:10.000
point. For me, I'm very

0:20:10.000,0:20:11.120
sympathetic to that,

0:20:11.120,0:20:13.429
specifically because I speak variant,

0:20:13.429,0:20:16.307
but of the Voseo variant

0:20:16.307,0:20:18.228
That means that in most cases

0:20:18.228,0:20:20.825
I would benefit from a fallback to

0:20:20.825,0:20:22.518
Spain's Spanish

0:20:23.280,0:20:24.560
because there is not much

0:20:24.560,0:20:26.210
translations going on for you

0:20:26.210,0:20:28.920
I'm not even sure if we[br]have a locale, honestly.

0:20:29.550,0:20:31.360
so that's something that could

0:20:31.360,0:20:33.290
-- personally, I think it could happen

0:20:33.290,0:20:34.631
before Phase 4?

0:20:34.631,0:20:36.590
I think it could be, like,

0:20:36.590,0:20:38.320
a small step towards

0:20:38.320,0:20:40.640
a significantly better experience.

0:20:40.640,0:20:42.620
So it might be good to discuss it

0:20:42.620,0:20:44.410
before Phase 4.

0:20:44.410,0:20:47.040
But in any case, if that happens -- if it

0:20:47.040,0:20:49.440
doesn't happen before, it would

0:20:49.440,0:20:52.048
surely be a part of the phase 4

0:20:52.048,0:20:54.178
conversation. Thank you again

0:20:54.178,0:20:56.293
and hope you're doing well. Bye-bye.

0:20:56.293,0:20:58.000
>> Hello, everyone.

0:20:58.000,0:21:00.317
Good moring, Matt. This is Joe Simpson

0:21:00.317,0:21:01.840
in Castilla, California

0:21:01.840,0:21:03.680
in the Santa Clarita Valley,

0:21:03.680,0:21:05.750
just north of Los Angeles.

0:21:05.750,0:21:07.840
I'm the lead organizer for WordCamp

0:21:07.840,0:21:09.920
Santa Clarita online and I run

0:21:09.920,0:21:12.000
two WordPress meetups in the

0:21:12.000,0:21:13.920
area as well. As you can tell,

0:21:13.920,0:21:16.640
I'm a big WordPress fan.

0:21:16.640,0:21:18.880
I'm a big advocate for accessibility

0:21:18.880,0:21:20.560
as well, and I've done quite a

0:21:20.560,0:21:23.373
few events this year in that space.

0:21:23.373,0:21:26.016
What I wanted to reach out to you today

0:21:26.016,0:21:28.178
about was a matter

0:21:28.178,0:21:30.339
that's pretty important to me.

0:21:30.339,0:21:33.541
When we had our event in the spring,

0:21:33.541,0:21:37.520
we had volunteers from Bangladesh, we had

0:21:37.520,0:21:39.600
attendees from Europe, from

0:21:39.600,0:21:41.280
Africa, volunteers from South

0:21:41.280,0:21:44.000
America, and it opened up my

0:21:44.000,0:21:47.040
eyes to WordPress as a worldwide

0:21:47.040,0:21:49.760
entity and a community that's

0:21:49.760,0:21:53.600
global in nature, but my concern

0:21:53.600,0:21:55.920
was these online presentations,

0:21:55.920,0:21:58.320
these online events, Wordcamps,

0:21:58.320,0:21:59.400
workshops, et cetera,

0:21:59.400,0:22:01.600
I was really really wondering whether they

0:22:01.600,0:22:03.312
could be more accessible.

0:22:03.312,0:22:06.480
What is WordPress doing to make its

0:22:06.480,0:22:09.360
online presence more accessible

0:22:09.360,0:22:11.680
to everyone? I'm really big on

0:22:11.680,0:22:13.445
inclusion and diversity, and I would

0:22:13.445,0:22:15.490
love to hear what WordPress plans to do

0:22:15.490,0:22:17.520
moving forward with online events.

0:22:17.520,0:22:19.760
Thank you. Have a great holiday

0:22:19.760,0:22:21.280
and a good New Year, everyone.

0:22:21.280,0:22:22.388
Take care.

0:22:22.920,0:22:25.280
>> Well, first of all, Joe,

0:22:25.280,0:22:26.960
thank you so much for your

0:22:26.960,0:22:28.960
contributions and leading by

0:22:28.960,0:22:31.436
example, which is, well, many would say

0:22:31.436,0:22:33.825
the only type of leadership

0:22:33.825,0:22:36.240
I do believe that as

0:22:36.240,0:22:37.920
anxious as I am to get back to

0:22:37.920,0:22:39.920
our in-person events, I do

0:22:39.920,0:22:41.520
believe that much like your

0:22:41.520,0:22:43.120
experience of hosting a, you

0:22:43.120,0:22:45.130
know, a more local WordCamp and

0:22:45.130,0:22:47.060
people from all over the world joining,

0:22:47.060,0:22:49.170
I think if we can move more and more of

0:22:49.170,0:22:51.841
our community engagement to be

0:22:51.841,0:22:55.350
really rich and interactive online,

0:22:55.350,0:22:57.139
we get the benefits of the metaverse,

0:22:57.139,0:22:58.800
right? That people can choose to

0:22:58.800,0:23:00.480
represent themselves however

0:23:00.480,0:23:04.260
they like or not. They can be treated

0:23:04.260,0:23:05.930
for their -- and perceived by their

0:23:05.930,0:23:07.708
contributions, their words,

0:23:07.708,0:23:08.990
how they participate.

0:23:08.990,0:23:10.390
Not necessarily who they are,

0:23:10.390,0:23:12.373
where they're from or any of that.

0:23:12.373,0:23:15.360
You know, when I first got started

0:23:15.360,0:23:17.508
contributing to open source,

0:23:17.508,0:23:19.280
I didn't have any of the background

0:23:19.280,0:23:21.540
or there wasn't really a community

0:23:21.540,0:23:22.800
in Houston where I was

0:23:22.800,0:23:25.016
or anything like that, to see.

0:23:25.016,0:23:26.716
But I appreciated so much

0:23:26.716,0:23:29.459
that people would look at,

0:23:29.459,0:23:31.680
for me, my code and say,

0:23:31.680,0:23:33.930
okay, this isn't just some young kid

0:23:33.930,0:23:36.491
in Houston who is not a real engineer,

0:23:36.491,0:23:38.694
They were able to look at it for

0:23:38.694,0:23:40.527
its own merits.

0:23:40.527,0:23:42.816
And I think that, you know,

0:23:42.816,0:23:44.450
almost 20 years later,

0:23:44.450,0:23:46.930
we can do so much more

0:23:46.930,0:23:48.480
than that in terms of

0:23:48.480,0:23:50.560
creating a truly, truly

0:23:50.560,0:23:51.996
inclusive community.

0:23:51.996,0:23:53.513
The other thing that's really,

0:23:53.513,0:23:55.316
really important to me there and that

0:23:55.316,0:23:57.326
I do see demonstrated throughout WordPress

0:23:57.326,0:23:59.133
but I just want to emphasize it again,

0:23:59.133,0:24:01.280
is what you mentioned, that idea of

0:24:01.280,0:24:03.280
always being welcoming, always being

0:24:03.280,0:24:05.120
kind, always being friendly,

0:24:05.120,0:24:06.880
particularly as more folks from

0:24:06.880,0:24:08.400
around the world get involved,

0:24:08.400,0:24:09.910
it's important to remember that

0:24:09.910,0:24:11.969
not everyone's first language is English.

0:24:11.969,0:24:14.083
and so there might be communication

0:24:14.083,0:24:15.712
barriers or misunderstandings.

0:24:15.712,0:24:18.880
And so just -- we have a saying within

0:24:18.880,0:24:20.757
Automattic that I think is fantastic

0:24:20.757,0:24:22.480
for any sort of distributed work or

0:24:22.480,0:24:23.840
collaboration, and it's a

0:24:23.840,0:24:25.360
different kind of "API"

0:24:25.360,0:24:28.507
It stands for Assume Positive Intent.

0:24:28.507,0:24:29.914
Find that if you can --

0:24:29.914,0:24:32.061
this isn't something you can ask of anyone else,

0:24:32.061,0:24:33.922
but if you can remind yourself of it,

0:24:33.922,0:24:35.891
it allows you to see other people's

0:24:35.891,0:24:38.720
interactions through a lens which,

0:24:38.720,0:24:40.748
allows you to put your best foot forward

0:24:40.748,0:24:42.480
and allows them to

0:24:42.480,0:24:44.240
regain their best foot, if they

0:24:44.240,0:24:46.349
didn't put it forward,

0:24:46.349,0:24:48.570
probably on accident with whatever

0:24:48.570,0:24:50.929
interaction or communication it was.

0:24:50.929,0:24:53.552
So, I keep all those things in mind.

0:24:53.552,0:24:56.177
Just to recap, more and more online.

0:24:56.177,0:24:58.531
Again, leaning way more into the

0:24:58.531,0:25:00.720
online education, online engagement,

0:25:00.720,0:25:03.681
online mentorship, online –

0:25:03.681,0:25:05.018
you know, everything.

0:25:05.018,0:25:06.760
Which is kind of funny because it is

0:25:06.760,0:25:08.744
a little bit back to our roots before we

0:25:08.744,0:25:09.640
ever had events

0:25:09.640,0:25:11.450
Remembering that great ideas,

0:25:11.450,0:25:12.822
great contributions can come

0:25:12.822,0:25:14.560
from everywhere and anywhere,

0:25:14.560,0:25:16.000
and then making sure

0:25:16.000,0:25:18.246
that people regardless of where they are,

0:25:18.246,0:25:20.286
the background, the language they speak,

0:25:20.286,0:25:21.950
their economic ability, anything,

0:25:21.950,0:25:23.260
feel fully included

0:25:23.260,0:25:24.570
in the WordPress community.

0:25:24.570,0:25:26.018
Everyone has a place here.

0:25:26.018,0:25:28.000
We are trying to democratize publishing

0:25:28.000,0:25:29.840
and commerce. We are -- and

0:25:29.840,0:25:31.864
democratize means it's for everyone.

0:25:31.864,0:25:34.870
It's not just for the few, or the elite,

0:25:34.870,0:25:35.904
or the technical.

0:25:35.904,0:25:36.960
That's our mission.

0:25:36.960,0:25:38.679
It's a lifelong mission.

0:25:38.679,0:25:39.841
We'll never be perfect,

0:25:39.841,0:25:41.520
and I plan to keep working on this

0:25:41.520,0:25:43.970
the rest of my life, and I hope that --

0:25:43.970,0:25:46.560
to see you and others alongside

0:25:46.560,0:25:47.700
in that mission

0:25:47.700,0:25:49.960
for many years and decades to come.

0:25:49.960,0:25:53.297
>> Hi, Matt. My name's Laura.

0:25:53.297,0:25:55.840
I am a member of the WordPress

0:25:55.840,0:25:58.307
community in Montclair, New Jersey,

0:25:58.307,0:26:01.549
and I have used WordPress

0:26:01.549,0:26:03.446
every day of my life

0:26:03.446,0:26:06.482
since January of 2006.

0:26:06.482,0:26:10.160
So I'm a really early adopter and

0:26:10.160,0:26:12.400
a longtime user. I'm also somebody

0:26:12.400,0:26:14.800
who doesn't code. I'm a content

0:26:14.800,0:26:18.480
creator, and I love doing that

0:26:18.480,0:26:20.320
and getting all kinds of

0:26:20.320,0:26:22.160
messages out there in the world.

0:26:22.800,0:26:24.480
Primarily I've created content

0:26:24.480,0:26:26.640
for non-profits, for

0:26:26.640,0:26:28.800
entertainment industry websites.

0:26:28.800,0:26:31.255
So I guess my question to you, Matt, is,

0:26:31.255,0:26:33.760
when I go to WordCamps,

0:26:33.760,0:26:36.919
I frequently don't see a lot of tracks

0:26:36.919,0:26:39.980
for fellow content creators like me.

0:26:39.980,0:26:43.750
What could you say to the folks who are

0:26:43.750,0:26:47.280
running WordPress events, specifically

0:26:47.280,0:26:50.472
WordPress meetups and WordCamps,

0:26:50.472,0:26:52.256
that might encourage them

0:26:52.256,0:26:55.120
to embrace content creators

0:26:55.120,0:26:57.280
and think about creating more

0:26:57.280,0:27:01.129
tracks for users that were less technical?

0:27:01.880,0:27:04.800
>> Hey, Laura. I think this is

0:27:04.800,0:27:06.400
an excellent question and one

0:27:06.400,0:27:08.370
that's really important to me.

0:27:08.370,0:27:11.040
I think that content is the thing

0:27:11.040,0:27:14.000
that gives your website power

0:27:14.000,0:27:15.680
and meaning. It's wonderful to

0:27:15.680,0:27:17.818
have a well-built, well-constructed,

0:27:17.818,0:27:19.505
well-designed website,

0:27:19.505,0:27:21.170
but if you don't have anything for

0:27:21.170,0:27:23.095
your users once they arrive,

0:27:23.095,0:27:25.440
I'm not certain that your website is

0:27:25.440,0:27:27.524
really doing its best job for you.

0:27:27.524,0:27:30.960
And so to encourage event organizers

0:27:30.960,0:27:33.360
to embrace content creators and

0:27:33.360,0:27:35.440
make sure that we have provided

0:27:35.440,0:27:39.026
content for them to up-level their skills,

0:27:39.026,0:27:41.050
I think the thing that's most important to

0:27:41.050,0:27:42.710
remember is that writing for the

0:27:42.710,0:27:44.880
internet is a specific and

0:27:44.880,0:27:46.380
different skill.

0:27:46.380,0:27:49.920
It's not the same as technical writing,

0:27:49.920,0:27:52.090
and it's not the same as writing prose.

0:27:52.090,0:27:54.880
So when we want to have

0:27:54.880,0:27:56.880
very good websites that are

0:27:56.880,0:27:58.720
engaging to our audiences but

0:27:58.720,0:28:00.316
still get the point across,

0:28:00.316,0:28:02.320
I think the only way to do it is

0:28:02.320,0:28:04.219
with excellent content, no matter

0:28:04.219,0:28:05.440
how that looks for you,

0:28:05.440,0:28:07.120
and the best way for us to help

0:28:07.120,0:28:08.720
WordPressers do that is to

0:28:08.720,0:28:10.960
provide training through our

0:28:10.960,0:28:13.952
WordCamps, meetups, et cetera.

0:28:13.952,0:28:15.576
>> Hi, Matt. I'm Lax here.

0:28:15.576,0:28:19.840
Using WordPress more than ten years.

0:28:19.840,0:28:24.010
And congrats for

0:28:24.010,0:28:26.790
growing up to 40% of the web.

0:28:26.790,0:28:27.680
That's nice.

0:28:27.680,0:28:31.139
So my question for you today is,

0:28:31.139,0:28:35.040
do you have any plans to optimize

0:28:35.040,0:28:37.392
WordPress performance?

0:28:37.392,0:28:39.324
I mean the self-hosted WordPress.

0:28:39.324,0:28:40.380
it's like, you know,

0:28:40.380,0:28:42.857
we have Jetpack, we have caching plugins,

0:28:42.857,0:28:45.513
but I found not only me,

0:28:45.513,0:28:47.840
my clients, and I see

0:28:47.840,0:28:49.520
bloggers and everyone struggle

0:28:49.520,0:28:51.310
with the performance,

0:28:51.310,0:28:55.440
and also like optimizing the database

0:28:55.440,0:28:58.640
queries -- like, to get a simple

0:28:58.640,0:29:00.560
tag or category, we are running

0:29:00.560,0:29:03.840
too much of subqueries, right?

0:29:03.840,0:29:06.720
I'm sure you are a programmer

0:29:06.720,0:29:08.960
yourself, so you might have some

0:29:08.960,0:29:11.840
plans for the future. And good

0:29:11.840,0:29:14.640
luck with our motto, like

0:29:14.640,0:29:16.480
democratizing the web. Thank

0:29:16.480,0:29:16.980
you.

0:29:17.320,0:29:19.920
>> Howdy, Lax. You hit on one of

0:29:19.920,0:29:21.040
my favorite topics, which is

0:29:21.040,0:29:22.400
performance. I was really

0:29:22.400,0:29:23.520
excited that we were able to get

0:29:23.520,0:29:24.800
some performance improvements

0:29:24.800,0:29:27.040
into WordPress 5.4, as I talked

0:29:27.040,0:29:29.520
about in the talk, but there's

0:29:29.520,0:29:30.480
always more to do. That's the

0:29:30.480,0:29:31.120
beautiful thing about

0:29:31.120,0:29:32.320
performance, is it can always be

0:29:32.320,0:29:34.800
better. For the issues that you

0:29:34.800,0:29:36.720
describe, I would encourage you

0:29:36.720,0:29:38.640
to perhaps check out a different

0:29:38.640,0:29:40.960
web post. If you're running into

0:29:40.960,0:29:42.160
that frequent of performance

0:29:42.160,0:29:43.600
issues, there might be something

0:29:43.600,0:29:44.960
where, you know, they have you

0:29:44.960,0:29:46.080
on a server with too many other

0:29:46.080,0:29:49.120
clients or they don't have SSDs

0:29:49.120,0:29:50.240
in the servers or whatever it

0:29:50.240,0:29:53.120
is. But any modern performant

0:29:53.120,0:29:54.720
WordPress web post, primarily

0:29:54.720,0:29:56.000
the ones we recommend on

0:29:56.000,0:29:59.360
wordpress.org can really handle

0:29:59.360,0:30:01.360
a ton of traffic to even an

0:30:01.360,0:30:03.440
un-cached, unconfigured site.

0:30:04.480,0:30:06.320
That's always great. In terms of

0:30:06.320,0:30:07.600
things in core that we could do

0:30:07.600,0:30:10.400
to make it better, our queries,

0:30:10.400,0:30:11.600
I do believe they're pretty

0:30:11.600,0:30:12.960
optimized. They run in a lot of

0:30:12.960,0:30:14.640
places, but who knows, maybe a

0:30:14.640,0:30:16.000
new future got introduced, maybe

0:30:16.000,0:30:17.440
something regressed. So,

0:30:17.440,0:30:18.800
please, if there is something

0:30:18.800,0:30:20.960
out there that you have noticed,

0:30:21.760,0:30:24.320
either open a track ticket or,

0:30:24.320,0:30:25.520
you know, share it with someone

0:30:25.520,0:30:27.200
or if you, you know, debugging

0:30:27.200,0:30:28.160
queries is actually one of the

0:30:28.160,0:30:29.840
ways I learned the most about

0:30:29.840,0:30:31.200
programming and engineering,

0:30:31.200,0:30:32.480
just spending hours and hours

0:30:32.480,0:30:34.320
inside the mySQL command line

0:30:34.320,0:30:37.520
was -- was actually an amazing

0:30:37.520,0:30:38.880
sort of way I developed as a

0:30:38.880,0:30:40.160
developer and progressed as a

0:30:40.160,0:30:41.760
developer. So it might be

0:30:41.760,0:30:43.120
something -- you can discover

0:30:43.120,0:30:44.640
something new within WordPress

0:30:44.640,0:30:46.960
that then could save millions

0:30:46.960,0:30:49.040
and millions of server hours

0:30:49.040,0:30:51.680
someplace. So, let me know what

0:30:51.680,0:30:54.200
you find or let me know if that

0:30:54.200,0:30:55.520
-- if you make a ticket there.

0:30:55.520,0:30:56.560
I'll make sure to bump it with

0:30:56.560,0:30:58.240
the developers and that it gets

0:30:58.240,0:30:59.040
the proper attention.

0:31:00.040,0:31:02.480
>> 2020 brought new and

0:31:02.480,0:31:04.480
unexpected challenges, and I'm

0:31:04.480,0:31:05.680
proud to be a part of a

0:31:05.680,0:31:07.200
community like WordPress,

0:31:07.200,0:31:09.120
willing to step up, act quickly

0:31:09.120,0:31:10.960
and offer solutions in times of

0:31:10.960,0:31:12.880
need. Which emerging web

0:31:12.880,0:31:14.160
technologies are you most

0:31:14.160,0:31:17.120
interested in following in 2021

0:31:17.120,0:31:18.480
and how would you like to see

0:31:18.480,0:31:20.560
groups like MSP Media within the

0:31:20.560,0:31:23.280
WordPress ecosystem innovating

0:31:23.280,0:31:25.040
and solution-building using that

0:31:25.040,0:31:25.760
technology?

0:31:26.600,0:31:29.360
>> Hi, Meg. First of all,

0:31:29.360,0:31:30.560
congratulations for getting

0:31:30.560,0:31:31.520
SchoolListIt in the Call for

0:31:31.520,0:31:33.520
Code Top Five. I believe the

0:31:34.240,0:31:35.920
WordPress power tool to make it

0:31:35.920,0:31:37.360
the furthest. I know that wasn't

0:31:37.360,0:31:38.720
easy, so congratulations on

0:31:38.720,0:31:40.960
that. In terms of emerging

0:31:40.960,0:31:44.160
technologies, more broadly, I'm

0:31:44.160,0:31:45.920
excited that 2020 looks like

0:31:45.920,0:31:48.480
it's a year when more mainstream

0:31:48.480,0:31:51.680
adoption of cryptocurrencies is

0:31:51.680,0:31:53.680
really coming to bear, and that,

0:31:53.680,0:31:55.120
to me, you know, as someone who

0:31:55.120,0:31:56.480
is a big supporter of open

0:31:56.480,0:31:58.640
source and cryptocurrency is

0:31:58.640,0:32:00.000
kind of like open source applied

0:32:00.000,0:32:01.280
to money, the finance system.

0:32:02.480,0:32:04.000
Excited about that. Still very,

0:32:04.000,0:32:06.080
very early days. Probably, like,

0:32:06.080,0:32:07.360
you know, we're 10 years into

0:32:07.360,0:32:08.080
something that's going to take

0:32:08.080,0:32:10.640
30 years to happen, but it's

0:32:10.640,0:32:13.120
exciting to see steps. Closer to

0:32:13.120,0:32:16.240
home in the WordPress world, the

0:32:16.240,0:32:17.520
most emerging technologies --

0:32:17.520,0:32:18.560
not new, but they'll be new to

0:32:18.560,0:32:20.080
us when we adopt it for Phase 3

0:32:20.080,0:32:22.160
of Gutenberg will be Web RTC,

0:32:22.160,0:32:23.920
which is essentially like a way

0:32:23.920,0:32:25.440
for browsers to connect to each

0:32:25.440,0:32:26.960
other in a peer-to-peer fashion

0:32:26.960,0:32:28.080
that we can use for real-time

0:32:28.080,0:32:29.520
communication, so, for example,

0:32:29.520,0:32:31.280
the real-time co-editing that we

0:32:31.280,0:32:33.120
want to put into Gutenberg, and

0:32:33.120,0:32:33.920
we want to do it without a

0:32:33.920,0:32:35.920
centralized server so that, you

0:32:35.920,0:32:37.040
know, clients will be able to

0:32:37.040,0:32:38.400
connect to each other directly.

0:32:40.080,0:32:42.720
A little simpler, and I guess

0:32:42.720,0:32:43.440
don't know if you'd call it

0:32:43.440,0:32:44.800
emerging, but it's something we

0:32:44.800,0:32:46.000
need to do a lot better at, is

0:32:46.000,0:32:48.160
native development. So both the

0:32:48.160,0:32:50.240
mobile apps on iOS and Android

0:32:50.240,0:32:51.600
and native desktop apps for

0:32:51.600,0:32:54.240
WordPress, I think have a lot of

0:32:54.240,0:32:56.160
potential for just creating a

0:32:56.160,0:32:58.720
really slick, highly integrated,

0:32:58.720,0:33:01.360
ultra-fast application-like

0:33:01.360,0:33:03.120
interface for WordPress. We've

0:33:03.120,0:33:05.600
got the APIs for it now. We've

0:33:05.600,0:33:08.400
got some good starts, including

0:33:08.400,0:33:09.360
some of the code that's based on

0:33:09.360,0:33:10.320
Calypso, which is the

0:33:10.320,0:33:12.160
open-source React framework that

0:33:12.160,0:33:13.920
runs with WordPress.com. So

0:33:13.920,0:33:14.960
there is some good stuff there,

0:33:14.960,0:33:16.880
but I would like to see a lot

0:33:16.880,0:33:18.160
more, so, thank you for your

0:33:18.160,0:33:18.840
question.

0:33:18.840,0:33:21.040
>> Hi, Matt. I'm Michelle

0:33:21.040,0:33:22.240
Frechette, Head of Customer

0:33:22.240,0:33:24.480
Success at GiveWP, volunteer for

0:33:24.480,0:33:26.080
WordPress and Big Orange Heart,

0:33:26.080,0:33:28.640
and podcaster at WP Coffee Talk.

0:33:28.640,0:33:29.600
We've seen the WordPress

0:33:29.600,0:33:30.720
community grow and morph over

0:33:30.720,0:33:32.400
the years and it's been amazing.

0:33:32.400,0:33:33.840
This year changed a lot of the

0:33:33.840,0:33:35.280
way the community meets and

0:33:35.280,0:33:37.280
interacts due to the pandemic.

0:33:37.280,0:33:38.000
Some of it has been

0:33:38.000,0:33:39.360
heartbreaking, like not meeting

0:33:39.360,0:33:41.040
in person, but so much good has

0:33:41.040,0:33:42.320
come from it, too, like people

0:33:42.320,0:33:43.600
connecting from outside of their

0:33:43.600,0:33:45.120
areas on meet-ups, online

0:33:45.120,0:33:47.280
conferences and more. My

0:33:47.280,0:33:49.040
question is, what do you see for

0:33:49.040,0:33:50.080
the future of the WordPress

0:33:50.080,0:33:51.840
community as we move forward in

0:33:51.840,0:33:53.680
still uncertain times? What

0:33:53.680,0:33:55.040
initiatives should we be looking

0:33:55.040,0:33:56.560
forward to and what kind of

0:33:56.560,0:33:58.160
support can we expect for our

0:33:58.160,0:33:59.680
communities? Thanks for

0:33:59.680,0:34:00.880
providing the online State of

0:34:00.880,0:34:02.320
the Word and an opportunity to

0:34:02.320,0:34:03.520
contribute with questions.

0:34:04.440,0:34:07.280
>> Hi, Michelle. Thanks for

0:34:07.280,0:34:08.880
taking time to send in a

0:34:08.880,0:34:10.960
question. Andrea Middleton here.

0:34:12.720,0:34:14.800
Gosh, the changes that we have

0:34:14.800,0:34:16.320
weathered this year have been

0:34:16.320,0:34:19.680
immense, haven't they? I agree

0:34:19.680,0:34:21.760
with both the heartbreak and the

0:34:21.760,0:34:23.120
unexpected benefits that you

0:34:23.120,0:34:25.520
pointed out. When I think about

0:34:25.520,0:34:26.800
what the future holds for of the

0:34:26.800,0:34:28.640
WordPress community, though,

0:34:28.640,0:34:30.560
especially as we move out of

0:34:30.560,0:34:33.120
2020, but potentially into more

0:34:33.120,0:34:35.200
uncertainty, I'm really

0:34:35.200,0:34:37.680
optimistic. I know that

0:34:37.680,0:34:39.280
WordPress enthusiasts are

0:34:39.280,0:34:41.040
incredibly resourceful and

0:34:41.040,0:34:42.400
resilient in the face of

0:34:42.400,0:34:44.560
adversity, as we've proven this

0:34:44.560,0:34:46.880
year in many ways. The

0:34:46.880,0:34:48.400
initiative I'm most excited

0:34:48.400,0:34:50.800
about moving into 2021 is the

0:34:50.800,0:34:53.680
Learn WordPress platform, which

0:34:53.680,0:34:55.280
formally launched this week.

0:34:56.080,0:34:57.920
This on-demand WordPress

0:34:57.920,0:34:59.520
training platform has the

0:34:59.520,0:35:02.560
potential to build more bridges

0:35:02.560,0:35:04.880
and paths to WordPress and

0:35:04.880,0:35:07.040
success in WordPress than we've

0:35:07.040,0:35:09.680
ever seen at a time when more

0:35:09.680,0:35:12.640
people than ever are looking to

0:35:12.640,0:35:14.560
move their businesses online or

0:35:14.560,0:35:16.320
shift careers and become

0:35:16.320,0:35:18.960
WordPress professionals. I hope

0:35:18.960,0:35:20.800
to see a great deal of support

0:35:20.800,0:35:22.080
for this effort from

0:35:22.080,0:35:23.840
WordPress-based businesses as

0:35:23.840,0:35:26.160
well as individual contributors

0:35:26.160,0:35:28.320
who want to help others to help

0:35:28.320,0:35:30.880
WordPress as they themselves

0:35:30.880,0:35:34.000
have been helped. The support we

0:35:34.000,0:35:36.000
in WordPress provide to each

0:35:36.000,0:35:39.920
other is all about how small

0:35:39.920,0:35:43.680
kindnesses build into great and

0:35:43.680,0:35:45.360
interdependent, powerful

0:35:45.360,0:35:47.280
organizations. And I don't see

0:35:47.280,0:35:48.880
that changing any time soon.

0:35:49.840,0:35:51.120
Thanks so much for asking.

0:35:51.680,0:35:52.400
Talk to you later.

0:35:54.600,0:35:57.520
>> Hello. I'm Milana, a

0:35:57.520,0:35:59.120
freelance WordPress developer

0:35:59.120,0:36:01.840
based in Serbia and also an

0:36:01.840,0:36:03.440
active member of the

0:36:03.440,0:36:05.200
documentation team, and that is

0:36:05.200,0:36:07.120
the subject of my question

0:36:07.120,0:36:11.120
today. So as I see it, there are

0:36:11.120,0:36:13.120
two major problems which are not

0:36:13.120,0:36:14.720
unique only to the documentation

0:36:14.720,0:36:16.240
team. All teams seem to be

0:36:16.240,0:36:18.960
suffering from same conditions.

0:36:18.960,0:36:21.040
So the first one is we are

0:36:21.040,0:36:23.520
heavily understaffed. We don't

0:36:23.520,0:36:26.160
have enough active contributors

0:36:26.160,0:36:28.160
to cover all documentation

0:36:28.160,0:36:31.200
areas, and the second one is we

0:36:31.200,0:36:34.400
don't collaborate enough or at

0:36:34.400,0:36:36.720
all with other teams. And this

0:36:36.720,0:36:38.880
goes that far that sometimes we

0:36:38.880,0:36:40.080
don't even know who is the

0:36:40.080,0:36:42.080
person doing documentation for

0:36:42.080,0:36:44.080
release team, you know, the dev

0:36:44.080,0:36:46.800
notes. Also, there was this huge

0:36:46.800,0:36:49.680
gap between Gutenberg and the

0:36:49.680,0:36:51.280
documentation team and it's

0:36:51.280,0:36:52.960
getting bridged this year, but

0:36:54.080,0:36:55.680
it shouldn't even happen with

0:36:55.680,0:36:58.240
such a project as Gutenberg is.

0:36:58.240,0:37:00.480
And I'm not saying that anyone

0:37:00.480,0:37:02.880
here is doing anything wrong. We

0:37:02.880,0:37:05.360
all do as much as we can. I'm

0:37:05.360,0:37:08.560
just stating how it is. So, my

0:37:08.560,0:37:12.320
question is, how can we, as

0:37:12.320,0:37:15.520
global community, recognize this

0:37:15.520,0:37:18.720
need to connect teams, to work

0:37:18.720,0:37:21.840
more closely with each other? In

0:37:21.840,0:37:23.920
documentation team, we are

0:37:23.920,0:37:26.800
working right now on two big

0:37:26.800,0:37:28.960
projects, external linking

0:37:28.960,0:37:31.120
policy and documentation style

0:37:31.120,0:37:33.520
guide. Now, these will have

0:37:33.520,0:37:36.240
impact beyond documentation

0:37:36.240,0:37:39.280
team, and I'm not even sure how

0:37:39.280,0:37:40.720
many people are aware of the

0:37:40.720,0:37:42.880
fact that we are doing it. So,

0:37:44.800,0:37:46.720
from my perspective, WordPress

0:37:46.720,0:37:48.480
as a project is getting more

0:37:48.480,0:37:51.120
complex, and the way we were

0:37:51.120,0:37:53.040
doing things in the past and the

0:37:53.040,0:37:54.720
way we are doing things right

0:37:54.720,0:37:57.920
now is not sufficient anymore.

0:37:58.800,0:38:01.280
So, I guess it comes down to

0:38:02.000,0:38:04.560
rethinking what is the role of

0:38:05.360,0:38:06.880
making teams in WordPress

0:38:06.880,0:38:07.360
project.

0:38:07.360,0:38:11.600
[ Sound effect ][br]And how can we improve our

0:38:11.600,0:38:14.720
activities to make our work more

0:38:14.720,0:38:18.000
efficient in this situation that

0:38:18.000,0:38:19.600
we are all in, that we don't

0:38:19.600,0:38:21.680
have enough people and we don't

0:38:21.680,0:38:23.120
communicate. We need to

0:38:23.120,0:38:25.360
communicate more. So what is

0:38:25.360,0:38:28.240
your opinion on that? Thank you.

0:38:29.720,0:38:32.240
>> Hey, Milana, it sounds like

0:38:32.240,0:38:34.400
you have two big questions, and

0:38:34.400,0:38:36.080
I have two big thoughts about

0:38:36.080,0:38:38.320
them. Firstly, on the question

0:38:38.320,0:38:40.960
of recognizing how connected we

0:38:40.960,0:38:43.600
are, I agree. WordPress teams

0:38:43.600,0:38:45.200
frequently don't understand how

0:38:45.200,0:38:47.280
connected they are, a little bit

0:38:47.280,0:38:48.640
because it's hard to know how

0:38:48.640,0:38:50.720
your actions affect others when

0:38:50.720,0:38:52.720
you just barely have enough time

0:38:52.720,0:38:54.160
to focus on the contributions

0:38:54.160,0:38:55.200
that you want to make to the

0:38:55.200,0:38:56.560
teams that you're participating

0:38:56.560,0:38:58.800
with. Myself, I think that

0:38:58.800,0:39:00.160
sharing the internal workings a

0:39:00.160,0:39:02.400
bit better from my side can help

0:39:02.400,0:39:04.160
us all to know who we might need

0:39:04.160,0:39:05.440
to collaborate with during

0:39:05.440,0:39:07.760
projects, and I'm working up a

0:39:07.760,0:39:10.000
podcast for 2021 to share

0:39:10.000,0:39:11.680
bite-sized insight for

0:39:11.680,0:39:13.280
contributors who want to know

0:39:13.280,0:39:14.240
more about how their

0:39:14.800,0:39:16.880
contributions fit into the

0:39:16.880,0:39:19.200
larger picture. But I also

0:39:19.200,0:39:20.320
understand that part of the

0:39:20.320,0:39:22.000
solution is getting more

0:39:22.000,0:39:24.080
contributors into the space, and

0:39:24.080,0:39:25.360
I don't necessarily have a

0:39:25.360,0:39:27.680
solution for that outside of our

0:39:27.680,0:39:28.800
in-person events, which, of

0:39:28.800,0:39:31.040
course, in 2020 we haven't seen

0:39:31.040,0:39:33.120
a lot of. But it does kind of

0:39:33.120,0:39:34.560
lead us into your next question,

0:39:35.440,0:39:37.520
given that WordPress is so

0:39:37.520,0:39:39.520
complex and there aren't enough

0:39:39.520,0:39:40.400
people, not enough

0:39:40.400,0:39:43.600
communication, what can we do? I

0:39:43.600,0:39:44.800
have been on the more-

0:39:44.800,0:39:47.360
communication bandwagon for a

0:39:47.360,0:39:50.640
long time. But I actually think

0:39:50.640,0:39:51.920
that one of our short-term

0:39:51.920,0:39:54.160
problems as a project is how to

0:39:54.160,0:39:56.560
take our efficient communication

0:39:56.560,0:39:59.040
and make it more effective. I'm

0:39:59.040,0:40:01.280
gonna quote for you now the 19th

0:40:01.280,0:40:03.200
lesson from The Cathedral and

0:40:03.200,0:40:04.880
The Bazaar, our kind of source

0:40:04.880,0:40:06.320
material for things that we've

0:40:06.320,0:40:09.840
learned about open source in

0:40:10.400,0:40:13.200
general. To quote it, it says,

0:40:13.200,0:40:14.320
"provided the development

0:40:14.320,0:40:16.160
coordinator has a communications

0:40:16.160,0:40:18.000
medium at least as good as the

0:40:18.000,0:40:20.240
internet and knows how to lead

0:40:20.240,0:40:22.320
without coercion, many heads are

0:40:22.320,0:40:23.840
inevitability better than one."

0:40:25.280,0:40:28.800
And later in the document, later

0:40:28.800,0:40:30.320
in this -- in this piece of

0:40:30.320,0:40:33.920
writing, it's noted that open

0:40:33.920,0:40:35.840
source at scale can't

0:40:35.840,0:40:39.840
necessarily function very

0:40:39.840,0:40:42.640
effectively by constantly having

0:40:42.640,0:40:44.400
chaos all the time. It's hard

0:40:44.400,0:40:46.240
for human beings to work in that

0:40:46.240,0:40:47.680
sort of space, and so I think

0:40:47.680,0:40:49.040
that one of our short-term

0:40:49.040,0:40:51.840
questions for the project as a

0:40:51.840,0:40:54.320
whole is to make sure that when

0:40:54.320,0:40:56.160
we ask people to communicate

0:40:56.160,0:40:57.280
about what they're doing, why

0:40:57.280,0:40:58.560
they're doing it and where they

0:40:58.560,0:41:00.960
are doing it, we have made sure,

0:41:00.960,0:41:03.520
as leaders in WordPress, that

0:41:03.520,0:41:06.480
the plans for the product are

0:41:06.480,0:41:08.160
clear, so that everyone makes

0:41:08.160,0:41:09.200
good use of their time.

0:41:09.960,0:41:14.160
>> Myself, Monika, I'm working

0:41:14.160,0:41:16.720
with WordPress since 2015 and

0:41:16.720,0:41:18.000
regular contributing to the

0:41:18.000,0:41:20.320
WordPress. My question is about

0:41:20.320,0:41:22.080
the automation testing in the

0:41:22.080,0:41:24.880
WordPress ecosystem. As we know,

0:41:24.880,0:41:26.560
people are very much concerned

0:41:26.560,0:41:28.400
about the securities and the

0:41:28.400,0:41:30.160
other issues before upgrading to

0:41:30.160,0:41:33.120
the new version. So what are the

0:41:33.120,0:41:34.800
things we can implement in our

0:41:34.800,0:41:37.200
WordPress ecosystem to deliver

0:41:37.200,0:41:39.920
100% security? So, basically,

0:41:39.920,0:41:41.360
what are the automation things

0:41:41.360,0:41:42.480
we can integrate in our

0:41:42.480,0:41:43.920
WordPress ecosystem? Thank you.

0:41:44.680,0:41:47.200
>> Hi, Monika. I'm Jonathan.

0:41:47.200,0:41:48.080
Thank you for asking this

0:41:48.080,0:41:50.800
question. Security is always

0:41:50.800,0:41:52.240
evolving and changing, and

0:41:52.240,0:41:53.280
moving targets are very

0:41:53.280,0:41:54.960
difficult to reach definitively.

0:41:55.600,0:41:56.800
It's also a process that

0:41:56.800,0:41:58.720
unfortunately cannot be 100%

0:41:58.720,0:42:00.560
automated. Everyone needs to

0:42:00.560,0:42:01.680
learn to practice a

0:42:01.680,0:42:04.480
security-first mindset, but,

0:42:04.480,0:42:06.080
thankfully, there are some tools

0:42:06.080,0:42:07.120
that can help us in our

0:42:07.120,0:42:09.600
projects. For example, the

0:42:09.600,0:42:11.040
WordPress security team has

0:42:11.040,0:42:12.320
several automated testing

0:42:12.320,0:42:13.760
processes behind the scenes.

0:42:14.480,0:42:16.160
Every change to WordPress core

0:42:16.160,0:42:17.760
is run through these processes

0:42:17.760,0:42:19.360
to protect against known

0:42:19.360,0:42:21.760
security vulnerabilities. The

0:42:21.760,0:42:23.120
processes are continually

0:42:23.120,0:42:24.560
changing and expanding as new

0:42:24.560,0:42:25.840
security issues are discovered

0:42:25.840,0:42:28.160
and fixed. I'm being a little

0:42:28.160,0:42:29.360
intentionally vague, because

0:42:29.360,0:42:30.960
often security practiced will be

0:42:30.960,0:42:32.560
tailored to a certain project or

0:42:32.560,0:42:34.720
organization. Being ambiguous

0:42:34.720,0:42:36.080
will help you keep your project

0:42:36.080,0:42:39.040
more secure. There are also some

0:42:39.040,0:42:40.800
code analysis tools like the PHP

0:42:40.800,0:42:42.240
code sniffer that can be used to

0:42:42.240,0:42:44.000
identify potentially insecure

0:42:44.000,0:42:46.080
code in your project. Adding

0:42:46.080,0:42:47.520
these tools to your project and

0:42:47.520,0:42:48.960
requiring them to produce a

0:42:48.960,0:42:50.800
passing scan is a great way to

0:42:50.800,0:42:52.240
ensure the quality of the code

0:42:52.240,0:42:55.360
that you release. In WordPress

0:42:55.360,0:42:57.280
itself, several user-facing

0:42:57.280,0:42:58.560
features have been introduced in

0:42:58.560,0:43:00.480
the last few major versions that

0:43:00.480,0:43:02.240
make it easier for site owners

0:43:02.240,0:43:03.760
to be more aware of their site

0:43:03.760,0:43:06.400
security. The most recent one is

0:43:06.400,0:43:08.480
the ability to opt in to auto-

0:43:08.480,0:43:10.000
updates for plug-ins and themes.

0:43:10.960,0:43:12.560
Turning these on is a great way

0:43:12.560,0:43:13.840
to make sure your sites are

0:43:13.840,0:43:15.120
running the latest and most

0:43:15.120,0:43:17.120
secure code automatically, all

0:43:17.120,0:43:20.000
the time. Site Health is another

0:43:20.000,0:43:21.600
great example of a user-facing

0:43:21.600,0:43:23.680
tool. There are over a dozen

0:43:23.680,0:43:25.360
security-related checks included

0:43:25.360,0:43:27.280
in WordPress core by default,

0:43:27.280,0:43:28.720
and when they don't pass, site

0:43:28.720,0:43:30.480
health educates the user and

0:43:30.480,0:43:32.160
provides them with a recommend

0:43:32.160,0:43:33.760
way forward to fix the issue.

0:43:35.040,0:43:36.560
Any plug-in and theme can add

0:43:36.560,0:43:38.400
their own test to Site Health.

0:43:38.400,0:43:39.120
If there are any

0:43:39.120,0:43:40.880
security-related checks specific

0:43:40.880,0:43:42.720
to your project, adding them at

0:43:42.720,0:43:44.320
Site Health is a great way to

0:43:44.320,0:43:46.080
make a site owner aware of a

0:43:46.080,0:43:48.640
problem automatically. A few of

0:43:48.640,0:43:49.760
the tests check that you are

0:43:49.760,0:43:51.440
running secure versions of tools

0:43:51.440,0:43:52.720
installed at the server level.

0:43:53.600,0:43:55.760
Using PHP as an example, you

0:43:55.760,0:43:57.120
could set up an email alert

0:43:57.120,0:43:58.800
whenever a new version of PHP is

0:43:58.800,0:44:00.720
released. This would help you

0:44:00.720,0:44:02.400
automatically become aware of

0:44:02.400,0:44:03.840
security releases so you could

0:44:03.840,0:44:05.280
reach out to your host and

0:44:05.280,0:44:06.800
request that they update you to

0:44:06.800,0:44:09.680
this new version. Because of our

0:44:09.680,0:44:11.280
strong community, we have the

0:44:11.280,0:44:12.960
opportunity to work together to

0:44:12.960,0:44:15.200
continue educating site owners,

0:44:15.200,0:44:16.960
users and developers about

0:44:16.960,0:44:18.800
security best practices. If

0:44:18.800,0:44:20.000
everyone is more aware of

0:44:20.000,0:44:21.920
insecure practices, the entire

0:44:21.920,0:44:23.920
ecosystem will be elevated as a

0:44:23.920,0:44:25.760
result. I hope that that's

0:44:25.760,0:44:26.640
helpful and answers your

0:44:26.640,0:44:27.840
questions, and thank you for

0:44:27.840,0:44:28.720
choosing WordPress.

0:44:30.200,0:44:33.280
>> Hey. My name is Robert

0:44:33.280,0:44:35.680
Anderson. I am a WordPress

0:44:35.680,0:44:37.360
co-contributor living in Sydney,

0:44:37.360,0:44:40.320
Australia. Seth Miller wrote in

0:44:40.320,0:44:42.720
with this question: As Gutenberg

0:44:42.720,0:44:44.480
becomes more modern and feature-

0:44:44.480,0:44:46.240
driven, how do you approach

0:44:46.240,0:44:47.920
onboarding of new contributors

0:44:47.920,0:44:49.760
and other curious types - think

0:44:49.760,0:44:51.760
novice theme developer - to look

0:44:51.760,0:44:52.960
into block building with the

0:44:52.960,0:44:54.880
existing complexity of WebPack

0:44:54.880,0:44:57.600
and other build tools? Great

0:44:57.600,0:44:59.040
question, Seth. Thank you for

0:44:59.040,0:45:02.160
asking it. So, before I get into

0:45:02.160,0:45:04.160
the meat of Seth's question,

0:45:04.160,0:45:05.600
there's two quick things that I

0:45:05.600,0:45:08.160
want to note. Firstly, one of

0:45:08.160,0:45:09.600
the aims of the Block Editor is

0:45:09.600,0:45:11.280
to make it so that users can

0:45:11.280,0:45:13.040
create really ambitious websites

0:45:13.040,0:45:14.400
without having to be a theme

0:45:14.400,0:45:16.880
developer. So as an example, if

0:45:16.880,0:45:19.120
you insert a custom HTML block

0:45:19.120,0:45:20.240
and then save that as a

0:45:20.240,0:45:22.320
reusable block, you've more or

0:45:22.320,0:45:23.840
less created a new block without

0:45:23.840,0:45:25.040
having to write a single line of

0:45:25.040,0:45:26.000
code, which is really cool.

0:45:27.600,0:45:29.920
Secondly, tools like WebPack are

0:45:29.920,0:45:32.480
totally optional. Developers can

0:45:32.480,0:45:34.960
write a block using plain old

0:45:34.960,0:45:37.040
JavaScript that all web browsers

0:45:37.040,0:45:39.440
will understand, and, in fact,

0:45:39.440,0:45:40.880
if you load up the Gutenberg

0:45:40.880,0:45:42.720
handbook, you'll see that all of

0:45:42.720,0:45:44.160
our code examples there come in

0:45:44.160,0:45:46.720
two flavors, ESNext, which has

0:45:46.720,0:45:47.920
all the bells whistles,

0:45:47.920,0:45:51.680
including React's JSX, and ES5,

0:45:51.680,0:45:57.440
which doesn't. But, yes building

0:45:57.440,0:45:59.040
blocks and working with React,

0:45:59.040,0:46:01.520
is a lot easier if you are able

0:46:01.520,0:46:04.400
to use React's JSX syntax, so

0:46:04.400,0:46:05.840
setting up some kind of build

0:46:05.840,0:46:07.120
tooling is often worth the

0:46:07.120,0:46:09.440
up-front effort, and, yes, I

0:46:09.440,0:46:12.000
100% agree that this is very

0:46:12.000,0:46:13.280
challenging and can be pretty

0:46:13.280,0:46:15.040
off-putting to new developers.

0:46:16.400,0:46:18.560
Broadly speaking, I think that

0:46:18.560,0:46:20.400
there's two things that we can

0:46:20.400,0:46:22.720
do to make this easier: Tooling

0:46:22.720,0:46:25.120
and education. On the tooling

0:46:25.120,0:46:27.120
front, we now have some really

0:46:27.120,0:46:28.560
neat tools that make getting set

0:46:28.560,0:46:29.840
up with block development a lot

0:46:29.840,0:46:32.000
easier. The first, which is

0:46:32.000,0:46:33.520
developed by the core team at

0:46:33.520,0:46:36.320
WordPress, is WordPress/scripts.

0:46:37.120,0:46:39.680
This is a npm package that hides

0:46:39.680,0:46:41.200
away all of the complexity of

0:46:41.200,0:46:43.280
webpack and gives you a single

0:46:43.280,0:46:45.040
command that turns a source

0:46:45.040,0:46:47.520
directory of JavaScript, which

0:46:47.520,0:46:49.760
has all the fancy syntax, into a

0:46:49.760,0:46:51.920
build directory of compiled

0:46:51.920,0:46:55.840
JavaScript. The second,

0:46:56.720,0:46:58.240
developed by the WordPress

0:46:58.240,0:47:01.159
community is "create-guten-block."

0:47:01.159,0:47:02.880
This one gives you a

0:47:02.880,0:47:04.320
single command that instantly

0:47:04.320,0:47:06.320
creates an entire block plugin

0:47:06.320,0:47:08.160
for you. It does all the work of

0:47:08.160,0:47:09.200
configuring the build

0:47:09.200,0:47:11.440
environment and generates, like,

0:47:11.440,0:47:13.440
the necessary PHP to load things

0:47:13.440,0:47:14.880
into WordPress. It's really

0:47:14.880,0:47:18.480
quite straightforward. On the

0:47:18.480,0:47:20.480
education front, we have some

0:47:20.480,0:47:22.080
really great tutorials in the

0:47:22.080,0:47:23.520
Gutenberg handbook which cover

0:47:23.520,0:47:25.040
how to get set up with block

0:47:25.040,0:47:26.480
development using WordPress

0:47:27.280,0:47:29.680
script and you can see them at

0:47:29.680,0:47:30.720
wordpress.org/gutenberg/handbook

0:47:34.800,0:47:36.240
and, lastly, the WordPress

0:47:36.240,0:47:38.720
training team has just recently

0:47:38.720,0:47:41.280
learned learn.wordpress.org

0:47:41.840,0:47:43.440
which is a new home for video

0:47:43.440,0:47:45.600
workshops about WordPress. And

0:47:45.600,0:47:47.120
one of the video workshops there

0:47:47.120,0:47:49.920
by Jonathan Bossenger is all

0:47:49.920,0:47:52.480
about how to develop a block, so

0:47:52.480,0:47:53.600
definitely check that out and

0:47:53.600,0:47:57.680
definitely watch that space. I

0:47:57.680,0:47:58.880
hope that was helpful. I hope I

0:47:58.880,0:48:00.880
answered your question. And

0:48:00.880,0:48:01.680
thank you for choosing

0:48:01.680,0:48:02.240
WordPress.

0:48:02.240,0:48:04.960
>> Hi. My name is Sudar Muthu.

0:48:04.960,0:48:06.400
I'm from a city called Chennai

0:48:06.400,0:48:07.680
in the southern part of India.

0:48:08.320,0:48:09.280
I've been involved with

0:48:09.280,0:48:10.880
WordPress for about 15 years

0:48:10.880,0:48:12.800
now, and for the past six years,

0:48:12.800,0:48:14.080
I've been working as a full-time

0:48:14.080,0:48:16.160
WordPress developer. In short,

0:48:16.160,0:48:17.840
WordPress is what puts food on

0:48:17.840,0:48:20.560
my table. So here's my question.

0:48:20.560,0:48:22.400
So, it's been about 17 years

0:48:22.400,0:48:23.520
since the first version of

0:48:23.520,0:48:25.040
WordPress has been released, and

0:48:25.040,0:48:27.200
all of us know where WordPress

0:48:27.200,0:48:28.880
is there right now. So my

0:48:28.880,0:48:31.120
question is, where do you see

0:48:31.120,0:48:33.840
WordPress in the next 17 years?

0:48:34.880,0:48:35.280
Thank you.

0:48:35.280,0:48:38.160
>> Sudar, 17 years is such a

0:48:38.160,0:48:40.800
long time! Sometimes I feel

0:48:40.800,0:48:42.160
amazed that I've been doing

0:48:42.160,0:48:44.960
WordPress for this long. I think

0:48:44.960,0:48:46.880
my hope is the same as many

0:48:46.880,0:48:47.840
others in the WordPress

0:48:47.840,0:48:51.920
community, that by 2037 we've

0:48:51.920,0:48:54.400
gotten the vast majority, maybe

0:48:54.400,0:48:56.160
as close to 100% as we can get

0:48:56.160,0:48:57.360
of the web on open source

0:48:57.360,0:48:59.600
software. I'd love to see

0:48:59.600,0:49:02.160
Gutenberg used not just by

0:49:02.160,0:49:04.000
WordPress, but by all of its

0:49:04.000,0:49:05.760
competitors as well, by everyone

0:49:05.760,0:49:08.000
who is accepting text in a box

0:49:08.000,0:49:09.600
on the internet or on native.

0:49:10.320,0:49:11.840
I'd love them to build on

0:49:11.840,0:49:13.680
Gutenberg Blocks, because then

0:49:13.680,0:49:14.960
that allows us to work together

0:49:14.960,0:49:15.920
on something that we all used to

0:49:15.920,0:49:17.520
have to rewrite and recreate a

0:49:17.520,0:49:19.440
million, million times, and I

0:49:19.440,0:49:20.720
believe that's how humanity

0:49:20.720,0:49:22.080
moves forward, is when we

0:49:22.080,0:49:23.200
collaborate, not when we

0:49:23.200,0:49:26.960
compete. In terms of, you know,

0:49:26.960,0:49:29.200
freedom and the open web, it's

0:49:29.200,0:49:30.160
hard to imagine what

0:49:30.160,0:49:31.600
technologies will be relevant.

0:49:32.480,0:49:35.680
One thing I always say within my

0:49:35.680,0:49:37.680
company at Automattic is that

0:49:38.960,0:49:40.400
the particular change will be

0:49:40.400,0:49:41.840
impossible to predict, but the

0:49:41.840,0:49:43.520
fact that change is going to

0:49:43.520,0:49:47.040
happen is inevitable. It is 100%

0:49:47.040,0:49:49.360
certain. And so as long as we

0:49:49.360,0:49:52.160
can stay adaptable, flexible,

0:49:52.160,0:49:53.600
not become too ossified in our

0:49:53.600,0:49:55.280
beliefs and always keep that

0:49:55.280,0:49:57.360
beginner's mind, the ability to

0:49:57.360,0:49:59.360
learn new technology. I've been

0:49:59.360,0:50:00.480
really, really impressed,

0:50:00.480,0:50:01.600
particularly in the past year or

0:50:01.600,0:50:03.600
two, post-Gutenberg, how so many

0:50:03.600,0:50:04.720
folks across WordPress have been

0:50:04.720,0:50:06.960
picking up JavaScript. You know,

0:50:06.960,0:50:08.800
taking where they were probably

0:50:08.800,0:50:12.320
PHP pros and JavaScript novices,

0:50:12.320,0:50:13.760
they've really invested the time

0:50:13.760,0:50:15.440
to become incredible JavaScript

0:50:15.440,0:50:16.960
developers, and now the entire

0:50:16.960,0:50:17.760
WordPress community is

0:50:17.760,0:50:19.360
benefitting from that. There

0:50:19.360,0:50:20.560
will be new generations of

0:50:20.560,0:50:22.960
technology. I imagine 17 years

0:50:22.960,0:50:24.320
from now, there will be

0:50:24.320,0:50:25.520
something after JavaScript that

0:50:25.520,0:50:26.480
will be the most important thing

0:50:26.480,0:50:27.760
to WordPress. I don't know what

0:50:27.760,0:50:28.800
that will be yet, but I'm

0:50:28.800,0:50:30.560
looking forward to finding it

0:50:30.560,0:50:32.080
out, and I hope that you're a

0:50:32.080,0:50:33.440
part of the journey as well, so

0:50:34.240,0:50:34.880
see you around.

0:50:35.480,0:50:38.960
>> Hi, my name is Tobi or Tobi

0:50:38.960,0:50:40.880
Ffjellner, as my handle is here

0:50:40.880,0:50:44.400
for WordPress. I'm one of the

0:50:45.840,0:50:47.040
people in the biggest

0:50:47.600,0:50:49.760
contributor team, polyglots. We

0:50:49.760,0:50:51.840
have almost 60,000 people who

0:50:51.840,0:50:54.000
have contributed at least some

0:50:54.000,0:50:56.080
translations to WordPress to

0:50:57.040,0:50:59.600
around 200 different language

0:50:59.600,0:51:01.600
versions, and out of those,

0:51:02.160,0:51:04.720
between 40 and 60 are actively

0:51:04.720,0:51:06.480
maintained, so that you can use

0:51:06.480,0:51:09.040
them right now if you want. And

0:51:09.040,0:51:12.160
a lot of people do that. 55% of

0:51:12.160,0:51:14.640
all WordPress sites around the

0:51:14.640,0:51:16.400
world that we know about use

0:51:16.400,0:51:18.400
some other language than U.S.

0:51:18.400,0:51:21.760
English. My question is about

0:51:21.760,0:51:24.240
multilingual WordPress. It has

0:51:24.240,0:51:26.240
been mentioned a couple of times

0:51:26.240,0:51:28.400
that in a future phase,

0:51:28.400,0:51:30.720
Gutenberg will cater for

0:51:30.720,0:51:33.120
multilingual content. I would

0:51:33.120,0:51:34.960
like to suggest that we already

0:51:34.960,0:51:36.960
now make decisions on what

0:51:37.520,0:51:39.520
storage structures we are going

0:51:39.520,0:51:41.680
to use and procedures, and

0:51:41.680,0:51:45.360
perhaps even already now go

0:51:45.360,0:51:47.680
forward to make WordPress

0:51:47.680,0:51:49.200
multilingual. There are already

0:51:49.200,0:51:51.200
solutions, and we could probably

0:51:51.200,0:51:53.520
reuse some of those, and by

0:51:53.520,0:51:54.800
doing this we open the

0:51:54.800,0:51:57.360
possibility for a lot of new

0:51:58.480,0:52:00.400
solutions to come up that could

0:52:00.400,0:52:02.800
support procedures around

0:52:02.800,0:52:04.160
translation, handling the

0:52:04.160,0:52:06.320
multilingual content, and so on.

0:52:06.320,0:52:09.120
And that part is where Gutenberg

0:52:09.120,0:52:10.160
actually would need to develop

0:52:10.160,0:52:12.320
something, but for the storage

0:52:12.320,0:52:14.160
procedures and so on, I think

0:52:14.160,0:52:15.840
we're talking more about PHP

0:52:15.840,0:52:17.520
development, where we could

0:52:17.520,0:52:20.160
reuse already existing plug-ins

0:52:20.160,0:52:22.800
to a large extent. Thank you.

0:52:23.880,0:52:26.160
>> Tobi, thank you so much for

0:52:26.160,0:52:27.680
your question, and, of course,

0:52:27.680,0:52:29.120
thank you for your contributions

0:52:30.160,0:52:31.360
for -- with translations and

0:52:31.360,0:52:33.120
that entire polyglots team. Much

0:52:33.120,0:52:35.840
love to the polyglots team. I,

0:52:35.840,0:52:37.920
like you, am very anxious to get

0:52:37.920,0:52:41.520
multilingual into Gutenberg,

0:52:41.520,0:52:42.720
whether we do it as part of

0:52:42.720,0:52:44.240
core, as part of an official

0:52:44.240,0:52:47.840
plug-in, TBD, but part of the

0:52:47.840,0:52:50.160
reason we made it Phase 4 is I

0:52:50.160,0:52:51.760
know that we can only do so many

0:52:51.760,0:52:54.960
things well at a time. And it is

0:52:54.960,0:52:57.200
supremely important that we

0:52:57.200,0:52:59.520
really execute super well on

0:52:59.520,0:53:01.440
these first phases of Gutenberg

0:53:01.440,0:53:03.200
Blocks. That's why also, even

0:53:03.200,0:53:04.400
though I'm super excited about

0:53:04.400,0:53:05.280
it, we haven't officially

0:53:05.280,0:53:06.560
started anything with the

0:53:06.560,0:53:07.840
real-time co-editing yet, for

0:53:07.840,0:53:11.520
Phase 3. If we don't get Phase 1

0:53:11.520,0:53:13.680
and Phase 2 to be the best

0:53:13.680,0:53:15.200
experiences in the world for

0:53:15.200,0:53:17.120
editing, bar none, of any open

0:53:17.120,0:53:18.240
source, any proprietary

0:53:18.240,0:53:21.520
competitors, any builders, Phase

0:53:21.520,0:53:23.200
3 and Phase 4 just won't matter,

0:53:23.200,0:53:26.240
right? Because it just --

0:53:26.240,0:53:27.760
WordPress won't be relevant a

0:53:27.760,0:53:30.720
decade from now. So I do believe

0:53:30.720,0:53:32.400
that that is the most important

0:53:32.400,0:53:34.640
problem that we're facing. And

0:53:34.640,0:53:36.400
part of why, even though we do

0:53:36.400,0:53:37.520
have a wide breadth of

0:53:37.520,0:53:38.560
contributors, and like you

0:53:38.560,0:53:40.160
mentioned, some plug-ins that do

0:53:40.160,0:53:44.000
solve multilingual already, I

0:53:44.000,0:53:46.000
don't want to dilute sort of the

0:53:46.000,0:53:48.720
core contributors' focus away

0:53:48.720,0:53:50.240
from the initial phases of

0:53:50.240,0:53:52.320
Gutenberg, because that's just

0:53:52.320,0:53:53.840
how important I think they are.

0:53:54.400,0:53:56.000
Now, that said, much like

0:53:56.000,0:53:57.440
Gutenberg has innovated in

0:53:57.440,0:53:59.200
plug-ins and then it gets later

0:53:59.200,0:54:00.480
adopted and merged into core,

0:54:01.280,0:54:02.640
there is nothing stopping, I

0:54:02.640,0:54:04.640
think, you know, more innovation

0:54:04.640,0:54:05.840
or more investments happening in

0:54:05.840,0:54:07.280
the plug-ins. In fact, I think

0:54:07.280,0:54:08.640
it's interesting that the

0:54:08.640,0:54:10.160
plug-ins can take various

0:54:10.160,0:54:11.520
different approaches with

0:54:11.520,0:54:13.600
regards to data storage and we

0:54:13.600,0:54:14.960
can see which works the best and

0:54:14.960,0:54:16.640
what scales, and the pluses and

0:54:16.640,0:54:19.200
minuses of each. My hope is that

0:54:19.200,0:54:20.720
down the line, much like the

0:54:20.720,0:54:22.320
page builders are coalescing

0:54:22.320,0:54:24.320
around sort of Gutenberg as --

0:54:24.320,0:54:26.160
and Blocks as page building,

0:54:26.720,0:54:27.840
kind of primitive that they all

0:54:27.840,0:54:30.320
build on top of. My hope is that

0:54:30.320,0:54:31.600
using learnings and hopefully

0:54:31.600,0:54:32.640
contributions from all of the

0:54:32.640,0:54:33.760
folks currently during

0:54:33.760,0:54:35.840
multilingual plug-ins right now,

0:54:35.840,0:54:37.840
we can figure out what is the

0:54:37.840,0:54:40.480
sort of 20% that gets us 80% of

0:54:40.480,0:54:41.680
the way there and create a

0:54:41.680,0:54:42.800
common framework that all of

0:54:42.800,0:54:44.960
them build on and then, you

0:54:44.960,0:54:46.000
know, much like we are with

0:54:46.000,0:54:48.320
Gutenberg Blocks, that Rails

0:54:48.320,0:54:49.760
will, you know, work well with

0:54:49.760,0:54:51.200
every other plug-in and theme.

0:54:51.200,0:54:52.880
So that is the hope, that is the

0:54:52.880,0:54:56.080
plan. 2022 is what I am

0:54:56.080,0:54:58.480
personally hoping to begin

0:54:59.040,0:55:00.720
working and focusing on this.

0:55:00.720,0:55:02.640
That also gives me a few years

0:55:02.640,0:55:05.520
to learn another language. Thank

0:55:05.520,0:55:06.480
you for your question. I'll see

0:55:06.480,0:55:07.280
you around WordPress.

0:55:09.080,0:55:12.640
>> Hi, Tom. I'm Otto. You wrote

0:55:12.640,0:55:15.120
in with this question. It reads,

0:55:15.120,0:55:16.160
sorry I can't make a video to

0:55:16.160,0:55:17.520
ask my question, but what I

0:55:17.520,0:55:18.720
would like to ask is what you

0:55:18.720,0:55:19.920
think about plug-ins like

0:55:19.920,0:55:21.680
Wordfence and Security Ninja

0:55:21.680,0:55:23.120
which recommend removing version

0:55:23.120,0:55:24.320
information from WordPress

0:55:24.320,0:55:25.760
headers and changing file

0:55:25.760,0:55:27.760
operations for certain files. If

0:55:27.760,0:55:28.560
you agree with these

0:55:28.560,0:55:30.000
permissions, then I wonder why

0:55:30.000,0:55:30.960
they aren't implemented in the

0:55:30.960,0:55:32.640
WordPress core. Or if you

0:55:32.640,0:55:34.400
disagree, then why are these

0:55:34.400,0:55:36.560
plug-ins allowed to remain in

0:55:36.560,0:55:38.240
the plug-in libraries and

0:55:38.240,0:55:40.160
charged for making changes that

0:55:40.160,0:55:41.040
are not recommended by

0:55:41.040,0:55:44.080
WordPress. That's a good

0:55:44.080,0:55:49.040
question, Tom. Well, removing

0:55:49.040,0:55:50.320
version information is often

0:55:50.320,0:55:51.600
referred to as a security

0:55:51.600,0:55:54.240
measure, but on the whole, it is

0:55:54.240,0:55:56.240
kind of an ineffective one. You

0:55:56.240,0:55:57.120
see, the thinking is that

0:55:57.120,0:55:58.960
hackers search for versions in

0:55:58.960,0:56:00.320
things like the HTML of the site

0:56:00.320,0:56:01.840
before they run scripts on it,

0:56:02.640,0:56:04.160
but history has shown that to be

0:56:04.160,0:56:07.040
rarely the case. The most common

0:56:07.040,0:56:08.640
problem faced by sites is

0:56:08.640,0:56:10.640
essentially bots and scripting

0:56:10.640,0:56:12.160
attacks. From these kind of

0:56:12.160,0:56:14.080
automated attempts, the failed

0:56:14.080,0:56:16.560
cases don't really matter, so it

0:56:16.560,0:56:18.720
doesn't save a hacker any time

0:56:18.720,0:56:20.160
or effort to have sophisticated

0:56:20.160,0:56:21.440
code to check versioning first.

0:56:22.480,0:56:24.000
So, by and large, this kind of

0:56:24.000,0:56:25.920
thing is the same as hiding the

0:56:25.920,0:56:27.760
login screen. It's not for

0:56:27.760,0:56:29.200
security, it's mostly for

0:56:29.200,0:56:31.680
vanity. The problem really with

0:56:31.680,0:56:32.560
calling these kind of things

0:56:32.560,0:56:34.720
security measures is that users

0:56:34.720,0:56:36.320
who don't understand security in

0:56:36.320,0:56:37.760
the form of layers of protection

0:56:38.480,0:56:39.600
will think that doing these is

0:56:39.600,0:56:40.960
the only security they have to

0:56:40.960,0:56:43.360
have. I've seen people use bad

0:56:43.360,0:56:45.280
passwords simply because they

0:56:45.280,0:56:46.640
assume the login screen couldn't

0:56:46.640,0:56:47.680
be found in the first place.

0:56:49.200,0:56:50.720
Doing such things like removing

0:56:50.720,0:56:52.240
versions or hiding logins or

0:56:53.120,0:56:54.480
anything like that isn't

0:56:54.480,0:56:55.840
actively dangerous or harmful,

0:56:56.400,0:56:57.520
it's just not the first thing

0:56:57.520,0:56:58.720
you should be doing to improve

0:56:58.720,0:56:59.760
the security of a website in

0:56:59.760,0:57:02.240
general. So in that respect

0:57:02.240,0:57:03.040
they're allowed in the plug-in

0:57:03.040,0:57:05.040
directory the same as anything

0:57:05.040,0:57:06.640
else is. I mean, plug-ins are

0:57:06.640,0:57:07.840
allowed for people who want to

0:57:08.400,0:57:10.240
do such things, even if that

0:57:10.240,0:57:12.880
isn't the majority of users. I

0:57:12.880,0:57:13.760
mean, that's what plug-ins are

0:57:13.760,0:57:14.880
for, after all, it's to

0:57:14.880,0:57:15.920
customize your site the way you

0:57:15.920,0:57:17.920
want it. As for whether they can

0:57:18.560,0:57:20.320
charge for making changes, all

0:57:20.320,0:57:21.760
plug-ins on wordpress.org are

0:57:21.760,0:57:26.080
free. Any charges made by

0:57:26.080,0:57:28.160
plug-ins such as pro versions

0:57:28.160,0:57:30.000
that are sold elsewhere is sort

0:57:30.000,0:57:32.160
of outside of our purview. So in

0:57:32.160,0:57:34.880
that respect, I would say I only

0:57:34.880,0:57:37.040
use free plug-ins, so there's

0:57:37.040,0:57:38.160
probably a free plug-in that

0:57:38.160,0:57:40.080
will make the changes you want.

0:57:40.080,0:57:41.120
Thanks for your question, Tom.

0:57:41.680,0:57:42.880
Appreciate it. Hope that helps.

0:57:44.600,0:57:47.600
>> Hi, Matt. I'm Winstina. In

0:57:47.600,0:57:49.680
2017, I presented at Wordcamp

0:57:49.680,0:57:52.320
U.S. on how cities and towns can

0:57:52.320,0:57:53.680
work with their residents to

0:57:53.680,0:57:58.560
sell locally online. My question

0:57:58.560,0:58:01.760
for you is this: What more can

0:58:01.760,0:58:04.400
Woo achieve beyond the freedom

0:58:04.400,0:58:06.400
of empowerment and expression

0:58:06.400,0:58:08.160
for all to sell digitally?

0:58:09.120,0:58:11.200
Essentially, what's your vision

0:58:11.200,0:58:15.280
for Woo democratizing commerce

0:58:15.280,0:58:17.840
during this pandemic and beyond?

0:58:20.000,0:58:20.440
Thanks.

0:58:20.440,0:58:22.800
>> Hi, Winstina. My name is Paul

0:58:22.800,0:58:24.080
Maiorana. I'm the CEO here at

0:58:24.080,0:58:25.520
WooCommerce. Thank you for your

0:58:25.520,0:58:27.120
question and thank you for

0:58:27.120,0:58:28.160
everything you do to support

0:58:28.160,0:58:31.360
local businesses. We share that

0:58:31.360,0:58:33.280
mission, ultimately. So your

0:58:33.280,0:58:34.160
question couldn't be more

0:58:34.160,0:58:35.840
pertinent in a year like 2020

0:58:35.840,0:58:37.120
that has brought such hardship

0:58:37.120,0:58:38.320
to small businesses.

0:58:38.880,0:58:40.560
WooCommerce powers over 2

0:58:40.560,0:58:42.480
million stores on our platform,

0:58:42.480,0:58:43.600
and we take that role really

0:58:43.600,0:58:44.160
seriously.

0:58:45.520,0:58:47.440
One of the things that we've

0:58:47.440,0:58:49.520
been focused on this year, we

0:58:49.520,0:58:50.400
know that WordPress and

0:58:50.400,0:58:52.880
WooCommerce can often be - or

0:58:52.880,0:58:53.760
require a little bit of

0:58:53.760,0:58:55.360
technical knowledge, or even

0:58:55.360,0:58:56.560
just some courage to kind of get

0:58:56.560,0:58:57.840
up and running with if you're

0:58:57.840,0:58:58.880
less experienced with the

0:58:58.880,0:58:59.440
platforms.

0:59:00.240,0:59:02.080
And this year, especially this

0:59:02.080,0:59:04.640
year, stores may not necessarily

0:59:04.640,0:59:06.000
have the budget to go out and

0:59:06.000,0:59:08.320
hire that additional help. So,

0:59:09.120,0:59:11.120
we've been focused this year on

0:59:11.120,0:59:12.320
empowering merchants to be more

0:59:12.320,0:59:13.600
self-sufficient and removing

0:59:13.600,0:59:15.120
many of the obstacles that a

0:59:15.120,0:59:16.320
merchant might hit in getting

0:59:16.320,0:59:18.080
their store online and then

0:59:18.080,0:59:19.360
running and growing that store.

0:59:21.440,0:59:22.320
We've been focused on our

0:59:22.320,0:59:23.760
on-boarding for one,

0:59:24.560,0:59:26.240
streamlining the setup process

0:59:26.240,0:59:27.920
in configuration for Woo, such

0:59:27.920,0:59:29.200
that you can get to that first

0:59:29.200,0:59:30.400
sale that much more quickly.

0:59:31.360,0:59:32.960
We're redesigning the navigation

0:59:32.960,0:59:34.320
around WooCommerce to make it

0:59:34.320,0:59:35.600
that much more intuitive, again,

0:59:35.600,0:59:36.640
for folks who are maybe less

0:59:36.640,0:59:38.080
experienced with WooCommerce and

0:59:38.080,0:59:38.640
WordPress.

0:59:40.480,0:59:41.600
We've been investing big in the

0:59:41.600,0:59:43.600
Block Editor and bringing new

0:59:43.600,0:59:45.520
product blocks into WooCommerce

0:59:45.520,0:59:46.960
to enable our merchants to be,

0:59:48.000,0:59:49.360
again, more self-sufficient in

0:59:49.360,0:59:50.400
the way that they merchandise

0:59:50.400,0:59:51.440
their products and not have to

0:59:51.440,0:59:52.880
be reliant on a developer to

0:59:52.880,0:59:57.040
implement those promotions. And

0:59:57.040,0:59:58.000
we also know that it's not

0:59:58.000,0:59:59.040
enough to just get a store

0:59:59.040,1:00:00.720
online and kind of, you know,

1:00:00.720,1:00:02.720
operate the store. Our merchants

1:00:02.720,1:00:04.640
want to grow, so we need to help

1:00:04.640,1:00:06.080
them reach their customers, so

1:00:06.080,1:00:08.080
we've also been investing a lot

1:00:08.080,1:00:09.120
in improving the marketing

1:00:09.120,1:00:10.400
solutions that are available for

1:00:10.400,1:00:11.840
WooCommerce to help our

1:00:11.840,1:00:13.840
merchants grow their stores. So,

1:00:13.840,1:00:15.600
I hope that's helpful. Thank you

1:00:15.600,1:00:16.800
for contributing to WordPress.

1:00:17.480,1:00:20.480
>> Wow, that was a lot of

1:00:20.480,1:00:23.120
questions and answers. I really

1:00:23.120,1:00:24.800
appreciate everyone from the

1:00:24.800,1:00:26.000
community who helped answer the

1:00:26.000,1:00:28.560
questions. As always with

1:00:28.560,1:00:30.080
WordPress, these things are so

1:00:30.080,1:00:31.120
much better when we work

1:00:31.120,1:00:33.600
together, and it was exciting to

1:00:33.600,1:00:35.200
me to be able to do a

1:00:35.200,1:00:37.120
distributed and virtual version

1:00:37.120,1:00:38.320
of what happens sometimes at

1:00:38.320,1:00:40.320
Wordcamps when I'll pass the mic

1:00:40.320,1:00:41.600
to someone, usually in the front

1:00:41.600,1:00:42.880
row from the WordPress

1:00:42.880,1:00:44.240
community, who knows so much

1:00:44.240,1:00:45.520
more than I can and can answer

1:00:45.520,1:00:47.520
the question so much better. So

1:00:47.520,1:00:48.480
keep an eye out for these

1:00:48.480,1:00:50.400
recordings and captions and

1:00:50.400,1:00:51.600
more, which will be on

1:00:51.600,1:00:55.840
wordpress.tv and the WordPress

1:00:55.840,1:00:59.120
YouTube channel. With that, I

1:00:59.120,1:01:00.800
bid you adieu. Thank you so much

1:01:00.800,1:01:03.280
for tuning in. I am so

1:01:03.280,1:01:04.960
appreciative to the WordPress

1:01:04.960,1:01:06.800
community this year for being

1:01:06.800,1:01:09.920
just a place of stability and

1:01:09.920,1:01:11.680
strength. I really love and

1:01:11.680,1:01:13.840
appreciate you all. Thank you so

1:01:13.840,1:01:17.040
much and see you again online.