- [Man] Maybe you can set up some points.
Give a warm welcome to Tammie Lister.
(audience clapping)
- Hello, I hope everybodyhad some good cake
and tea and is all ready for this.
As said, I'm Tammie Lister.
I don't really need to introduce myself.
That was an awesomeintroduction, thank you.
You can find me @karmatosedon all the things.
So, I'd just like tokinda get this out there.
This is not gonna be a technical talk
and, this is also not a workshopon how to build a block.
There's gonna be lots of stuff like that,
these couple of days.
But this talk is alsonot just for designers.
This is for anyone thatwants to understand
and really to look at the designbehind Gutenberg, as well.
And, hopefully I'm gonna have it useful
for people who want to build blocks
and to start creatingthings with Gutenberg.
I'd like, if possiblequestions at the end.
I'm hoping that I do havespace for questions at the end
so people can kind of do that.
I'm gonna be going quite fast.
I have quite a number of slides.
Can anyone hear some feedback
or is that just me who's hearing that?
- [Man] There's some feedback.
- Okay. (giggles)
Hopefully, I'm gonna kind of go
through those slides there.
And at the end, there'sgonna be a link for resources
so as we're going through that pace
hopefully we can get there.
I would also like to say that
these screenshots arevalid as of a week ago.
Gutenberg is a project being developed on
and it's still kind ofthings are gonna be changing,
but some of the principlesthat I'm gonna share
are not gonna be changing.
And kind of that.
So I'd like to pan out first of all
to the vision of Gutenberg.
And then I'd really kind of like to
hone in to blocks specifically.
So in short, everything is a block.
Text, images, galleries, widgets,
shortcodes, even chunks of custom HTML,
wherever it's from theeditor or if it's a plugin,
they're all are a block.
You should really only haveto learn how the block works
and then you know how to do everything.
So that's kind of thefundamental principles
of Gutenberg that it's built on.
Let's kind of move alittle bit out of that
and look at some of the language used
around the kind ofinterface with Gutenberg
and really start lookingat the specific elements
which are worth noting and those patterns
before then we dive intolooking at blocks, as well.
So first of all we're gonna take a look
right at the beginningby panning right out
and start looking at the screen.
So here is it broken down into shapes.
And if you think about,it's pretty familiar, right?
This is pretty WordPressyif you look at these shapes,
you have the patterns that you recognize.
And this is Gutenberg itself
sitting in WordPress inthe editing experience.
And although you can see the roots here,
you can also see some differences.
One of the roots, for example,is the document sidebar.
We have sidebars already within WordPress.
And here you have ita little bit different
when you close that sidebar you also get
a more minimal writing experience.
So that's the screen itself.
Now I'm gonna have a little bit of a look
at the action bar.
And let's kind of start on the top,
which, you know, we'relooking for the interface.
And this is the top tool bar,
in Gutenberg, the action bar.
This is what a blueprint
really looks like, for that.
And diving into, each element,
we have a way you can add a block,
a way to redo or undo a block,
and you also have someextra information about
the content and everything
that's being written.
Then you also have,
wherever this has been saved,
or updated,
and you have publish,
and preview,
and that little cover icon
is where you can see the actual settings,
or the sidebar, as well.
And the ellipsis is something
that we're gonna get into
a little bit later,
that's where extra things are.
So let's kind of look at the common thing
with WordPress,
the sidebar.
We saw a little bit earlier,
And let's kind of examine that
in the context of Gutenburg.
Here is the patten of the blueprint
of the sidebar.
And here we have, you can get to it
though the action bar
or through the advancesettings by the block.
This is now beingrenamed to block settings
because it's the block settings.
So that's kind of where this is.
Lets look have a little bit
of a look at the document side bar
because this is the first tab
and this really is the most common thing
that you are gonna expect.
Its not blocks.
Its not having anything really different.
You can see here.
You have all the things you'd expect.
You know, visibility, publishing,
You know as we go kind of in,
you see all these revisions
and tags, and categories.
Its all the things you'd expect to see
on a web press documentthat you can interact with.
Now, moving to the actionheart of Gutenburg.
Let's have a little bit of a look about,
how you add a block to your content.
So there is a couple of different ways
that you can add a block.
You can do this by using the plus icon
in the action bar.
You can also do it by having after blocks.
This is what you see whenyou first load the page.
A code to add a block
or as you are writing,
you can go through the next block
and this will appear,
and you can hit the plus icon,
and it will also suggesthere a combination
of frequent and recent blocks as well.
And there is a way you cando it in between blocks
and, this is called the sibling way
of adding a block.
As you can see here, you hover,
and then you click
and then you can add a blocks in between.
There's a way also to add blocks
which I really think isone of my favorite ways
of adding blocks.
And, that's using theforward slash command.
Just like in Slack or any other apps.
You can do this to bringup various block types.
I don't know if anyone hasexperience in using this
but, for me it's reallyfast way of writing.
As you start writing yourcontent and you can use it.
It's a great really wayto use the keyboard,
and really create thatflow as you're writing.
So, we looked at how you add a block.
Now I'm gonna look at the library,
and this is where all the blocks live.
And, this allows you tobrowse block by block as well,
and then they're in different sections.
Here you can see the most used blocks.
And then, you can also searchfor blocks in the library.
And we are working ondifferent ways to iterate this
but, this is the current status of this.
And then, you see kind of a scrolled list
which is in different sections as well.
And, you can see that imbeds
also, have their own section in this.
So that seems like Web Press TV,
YouTube, they all have their own block
that you can just, give you a link
and it will magically pullthe right imbed through.
Shared blocks are a great way to save
and reuse a block.
You can do this to any block.
You customize it, how ever you want it,
make it your own andthen you just reuse it
through, your site.
So, you flag it as a reusable block
and then you can see it here,
and you can preview what theyalso be like, which is great
because you are customizing
and doing different changes.
So being able to kindof preview those changes
is great way to do that.
For everyone's with me so far,
I'm gonna move a little bitinto some more bits now.
The ellipsis is a core part of the way
Gutenberg gives you more options.
Some of you might know thisfrom different mobile devices
and other interactions.
This is pretty common interaction
for people to recognize now
and, it simply means more.
In the tool bar,
the ellipsis shows thingslike switching between code
and visual editing.
So you can make those different choices.
And, you can also fixthe tool bar to the top
and, we're gonna get to that,into it a little bit later,
in tool bar positioning as well.
And, each block also has an ellipsis
and, this is commonfeatures across all blocks.
Editing HTML, deleting, and transforming.
And transforming is where each block
can transform into a different block.
Placeholders,
remember how I said that
there are kind of these design plans,
so placeholders reallyis a key part of this.
Placeholders are a way that you can,
say you have a patient,play it for example,
you can rather than havinga blank page load up,
you could load up specific blocks already
for someone to fill out.
That's a lot better way forsomeone to interact with,
a page template.
But, placeholders also as you are aware
they aren't really,
maybe you are just blocking out the page,
you're just saying,
I want an image here, Iwant some content here,
I want maybe a list here
and then you go fill things out.
Placeholders I'm gonna looka little bit more into this.
Placeholders is gonna bea common thing for at this
because they really key point of blocks.
Placeholders can have outlines
but they could also have actions like,
here with the image block.
That was a fast drawn
through some of wider design language
and vision of Gutenberg.
And, now going to the rest of this talk
really hone in a little bit more
into what a block is made of.
So looking at a blueprint.
Here is a blueprint of a block.
Pretty simple, right?
Has a tool bar, has the ellipsis
and has some arrows tomove it up and down.
That's what a block is made of.
So lets kind of look at a little bit
of these individual things around a block.
First of all, we're gonnalook at the block toolbar.
Here you can see the power graph block,
with the toolbar beside it.
Remember as I said that itwas that setting, before.
Where you can change,
and actually have the toolbar
to be up or in the action bar.
Well that was becausein usability testing,
we found people werepretty much 50/50, split,
on where they wanted by the block
or, whether they wantedit up on the tool bar.
So, for now we havegiven people that option.
To have either of those.
And, we have really been gonegoing back and forth on that.
But, for now settling tolet people have that choice.
So remember the documents sidebar?
Well, blocks have one too.
And, now you can see this
the entire side bar forthe paragraph block.
You can see all ofthese different settings
that you can have, you can do drop cap,
you can do alignment,
you can do different font sizes.
All these different settings,
and each block has differentsettings for it, as well.
Often asked, is where do the settings go?
So, the rule of thumb is in the toolbar,
you have primary actions
and these are things that a block can not
function without.
Where as the secondaryactions, anything else,
goes in the side bar.
That's a good rule of thumb
if you're writing a blockto kind of think about.
The primaries for a toolbar
and then, secondary is for the side bar.
So, I mentioned briefly,block transforming,
and almost all blocks can be transformed
into another type of block
This allows easy for you tochange content, for example.
You do this by either clicking
the drop down in the toolbar
which will show you the different blocks
or through the ellipsis menu again.
And the ellipsis is yourconstant point for all this.
And, here you get a list of everything
a block could transform into.
Each block is different.
For example here, you canchange a paragraph to a list,
a quote, or even a heading.
So when you making blocks.
I think the fundamentals to talk about
is the states of blocks.
Here we have the unselected placeholder.
This is when you just select a block,
you just load it,
you haven't added any content,
you haven't done anything.
This is for the image block.
I haven't added an image
and I haven't done anything,
I've just said, "I wannaan image block here."
And this shows,
generally, in the sense of this,
it will show upload us,
and so it's a call toaction to do something.
The selected is after you've added content
and then I selected the block, I get this.
For example, with images I now have a way
that I can resize the image there.
And, this is unselected
so I have not clicked on that block
but it's actually got content
and this is where it looks pretty close
to how it's gonna look on the front.
This is, as your scanningthrough your document,
this is what you would see.
That was a fast trackthrough basic anatomy
of some blocks.
I'm now gonna look at someactual examples of blocks.
And see how that applies to them.
The first of these,
is rather a complicated one.
And since it has lots of options
and that's the gallery block.
Here you can see the placeholders stays.
You have an upload and call to action,
and as you hover over it,
you can see these settings as well.
This is an encouragement.
Someone would know, whatyou would do with this.
You can also drag images as well.
Specifically for the image block.
And, here you have theunselected filled out state.
It looks pretty much howit's gonna look on the front.
The selected state when filled out,
has a little plus icon
that is not gonna show in the front
but, that's just saying,
"would you like to add more images?"
And, you can actually,
with the gallery block,
go a step further
and when you go into an individual image,
you can actually edit acaption there, and there.
Anyone who's kind ofusing WordPress for a bit,
that's a great way of doing it.
Rather than, having to go in and edit
then come back out again, do it again.
You can just change the caption like that.
The toolbar, it has allthe must-have actions
like editing, and alignment,
the things you really,
really want to have with a gallery block.
And the ellipsis shows further actions
in its advanced settings,
and also converting.
Sensibly, what wouldgallery block convert to?
Just images.
Then it would be like a row of it,
image, image, image,
that's what it would convert to
and, for gallery it can beconverted into separate images.
The setting side bar shows those
nice to haves, the extras,
all that kind of different things,
you don't need to crop.
That's probably quiet useful, occasionally
but its not essential for the block.
The same as the different rows,
that's a really fun thing to try,
if you haven't tried the gallery block.
Just moving up, and moving it down.
To do the different sizes of blocks.
And then I'll have a lookat a really basic one now
and that's a simple payment.
But it's a really great illustration
of how a block does nothave to be complicated.
I think sometimes,
we get very complicatedin thinking about blocks.
But the simpler the better,
when it comes to interfaces.
Here we have the unselected state,
and here we have the selected state.
Pretty simple, right?
It is just this one thing,
it's a basis to set payment.
Now have to go simple.
I'm gonna go even more complicated
than the gallery,
and I'm gonna have a lookat the slideshow block.
This is similar to the gallery
so I'm not gonna show every state
but this has a lot more options.
You can actually follow this,
along on Github here.
This is actually an issue,
where this is being developed.
Probably won't ship with Gutenberg
but, it's great to kindof explore these blocks.
Here, this is the advanced settings
for the slideshow,
because slideshows havethat many settings,
and exposes them
but these are secondary.
If you had these right in the toolbar,
it wouldn't be a greatuser experience at all.
But, having this in the slide,
that works in the slide show.
I wanna take a little bit of your time
to give you some hints.
Now, we have gone throughsome basics of blocks,
and to really hope that,
I allow you to make blocksa little bit easier.
The first hint,
is when you are designing a block,
all blocks have an icon
and they have some texts thatsays the name of the block.
Keep the icon simple,and signify the block.
The same goes for the texts.
Don't have three lines,
'cause imagine what that's gonna look like
in the library?
That's not gonna be good.
So a short name,
and an icon that signifiesexactly what that block is.
Have good placeholder defaults,
and really think of howthat page is made up
in a template.
And really kind of havethat vision as well.
And, I think I missed a slide
but I'm gonna add a slide
that I would also like,
you to think about,
how things work on differentmobile devices as well.
Think about how it adaptswhether you're walking around
or your using it on a smaller device.
When we use the word mobile,
we generally mean a smaller device.
Not necessarily that you'rejust wandering around with it.
'Cause we use the iPadat home as well, right?
But, don't say we're wanderingaround with it all the time.
But think about that not everybody
uses the desktop for everything.
And have these good defaults.
Think of a page made up in a template,
and think of what it looks like.
When it's unselected,
show a preview of the block like this,
make sure that you do that,
make sure it looks exactly
how it's gonna look on the front.
Every block at a minimum
should have a description
of what it looks like,
when it views in the additional setting,
So, make sure that it does that.
Say what it does, whenyou see in the side bar
this is what it's gonna show.
So make sure you do that.
I like to share some thoughts
based on things that I'veheard people say as well
or asked me about Gutenbergand specifically about blocks.
These are kind of questions
and we're gonna have time some times
for some questions,
but I hope I answer some now.
This is what I was saying like,
blocks should reallyadapt to different devices
and make sure you block feels,
or looks like on that device.
Test on those different devices.
Test that experience.
Gutenberg uses existingpatterns in WordPress
and I think that somethingthat we need to remember.
They're some new stuff,
there's also some stuff
that the foundations,
Gutenberg stands on thefoundations of WordPress.
For example,
toolbars exist in WordPress already.
Here you can see one
and then here yo see another one
in the editor itself.
Sidebars also exist in WordPress already.
Here you can see one,
and here you see another sidebar as well.
And it's really important to kind
of remember that these designpatterns are still there.
One of the questionsprobably in the top three
that gets asked is whereshould a block live?
Should it be in a theme?
Or should it be in a plugin?
The answer is, it depends.
But, likely plugins.
The reason is thereprobably is a good argument
for in a minority of cases,
to have a block that only works
when a specific theme is activated.
But that's probably the minority.
The majority people would want to use,
no matter what theme they had.
So, it depends but likely plugins.
One concept that's mentioned is,
should we do direct manipulation?
What is direct manipulation
with regards to Gutenberg?
So, this is a reallylengthy way of saying that,
you see something, you click it
and, it does something.
But, this is a great way
of describing what direct manipulation is.
And, this is Gutenberg.
So, this is direct manipulation.
Gutenberg has direct manipulation.
We sometimes add a lotmore weight to that term,
than we probably should
but that's what you do.
You're seeing it there,
you're clicking, you're interacting.
Everything with blocksis direct manipulation
and should be direct manipulation.
One thing I like to cover is,
what you see is not what you get.
At Automatic we have few challenges
which is experiencingsomething either someone does,
testing, you know reallygetting a feel for something.
And one of those was thedesigners had entry challenge
to use Gutenburg.
And Mel Choyce, who's actually gonna be
the design lead for phase two
of the customization of Gutenberg.
She had this quote that just struck me,
and I felt I had to reallycover this in this talk.
"Just because it looksright in the Editor,
"doesn't mean it looks right
"when rendered on thefront-end of your site."
And she's right.
Themes can still affectheavily, the output.
There are think supports
and other ways to ease this
but, right now the balance between
and overly aggressive Gutenberg styling
and leaving out thethemes is being struck.
And that's somethingwe're working through.
We've gone different directions
and that's something we're working
through as a community.
There are several, Github issues,
that you can join in and havethose discussions as well.
If you look at it here.
This what is looks like in the editor,
and then here is whatit looks like in 2014,
and then what it looks likein Gutenberg starter theme.
Where we go as a community,
with what you see is what you get.
Is that to us as a community to go,
I think sometimes people plant it
and say this is the line.
We have to go to whatwe see is what you get.
But, it really dependson how far we go there.
That's something that we haven't got
there, yet with.
And, I don't think that's something
we're gonna say I have an answer today.
So, beyond blocks.
I like to kind of bringsomething kind of with Gutenburg.
It's always asked whenshould I build a block?
That's a common question.
Do I extend it, do I build a block?
What do I do?
And mostly its gonna be a block
that you make.
But there are also otheroptions with Gutenberg
that I don't think everybody knows about.
This where the potential is for plugins,
to really create a morenative seamless additional
experience within WordPress
and to really truly extent it,
not just build on top of it
or around it.
And create that more, I useit as an app like experience.
You know that kind of feeling of it.
Here you can see,
and I've got the Github issues here.
Some potential ideas,
maybe you have WolframAlphain the side bar like this.
Or, maybe you have something
that I think that WordPressreally should have
which is collaborative editing.
This is actually an issue,
and this is being, peopleare working on this
and working few designs.
Our commenting is also something
that's being worked on like this.
And what about readability?
So, could you scan yourdocuments for readability,
using the ellipsis?
This is where you start to see,
that ellipsis become a little bit more
of those applications side.
I hope I've kind of, it'sa speed through Gutenberg
and a speed through the design.
But, you can see here,
there's actually a page
which has all my talks(metal clinks)
it has slides, it also has some resources
which I hope to share, I'mgonna tweet out as well.
And, there's actually a form on there.
If there's something,
and we're gonna havesometime for questions
but is there something you like,
that should be included in that talk?
Then please fill out the form
and I will happily add it.
I'm iterating this talk
and I would really like tomake it cover everything,
that people wanted about blocks.
And, I should say thank you.
Also to, Joen, Matias and Mel.
Who really have helped with the design.
Joen was the original design lead,
and Matias is the technical lead,
and it's said Mel is gonna be design lead
of the customization phase.
They are behind this design work as well.
And I would just like to say thank you
to anyone that has made a contribution
to Gutenberg.
And, a contribution is a review,
is a note, is a comment, is a issue.
It doesn't just have to be code.
Every single one matters,
and that how we've got tothis point with the product.
So, you can find me on@karmatosed on all the things
and I would like to takequestions now if possible.
Thanks.
(audience clapping)
- Thank you very much.
Are there any questions?
Please speak precisely on questions.
- Hi.Thank you.
- I like the idea thatit is super restricted.
Are you making it,
to force to stop the developers
ideas, input different style,
(excessive echoing)
- So controlling, I think it's more
of a matter of education.
So this part of why I'm giving this talk.
If we're educating as a community,
we are learning, these design patterns.
Then, I think we could maybe
not repeat some of the mistakes.
I always believe ineducation over control.
So, I would like to think
we can try that route, first of all.
- Thanks for the talk, Tammie
I was asking about the columnsblock, any plans for that?
'Cause, you could putbig texts in the blocks
and citing those.
- So the columns were experimental block.
(gently laughs)
Which that one hasexperimental byte for a reason.
We actually have text columns
but, we also the experimental blocks
where you can adddifferent blocks already.
So, that's already progressingwhat you're saying.
The idea of that is it might kind
of develop more than that.
We also have somethingcalled nested blocks.
Are you aware of that, as well?
That's a block in a block.(gently laughs)
Or blocks in a block.
That's the way we can maybe
expand differently there as well.
- Can we get twelve more questions?
The shorter the better.
- [Man] Thank you for the talk.
Obviously, I know you caninstall the plugin now
with its experiment Gutenburg.
Is there any news on,
when is it actually gonnaship with WordPress?
- So shipping, no.
Likely guarantees, most proposal in April?
March proposals areaway with the community
for those who don't know.
That those who are making it say,
"Hey this thing is kind of ready."
And, that is somethingthat we're working towards.
Anyone who can help us with that?
We have weekly meetings.
They are
1300 UTC
on Wednesdays,
and chat.webpress.org #core editor.
I think I got that right.
And also on Github,
there's also mild stones on Github
so, if people follow those,
you'll see there'sMarch proposal milestone
for each component.
A component is a sectionof WordPress as well.
So, you'd be able to seethat following along.
And as that gets less and less,
you'd be be able to kind of predict
when those are gonna happen as well.
- Okay, next question.
- Oh, you answered my question.
But I was wondering,
how much Java Scriptwould you be able to know
to manipulate Gutenbergto do certain things
via out of the box?
- Could you repeat the beginning bit
'cause I didn't hear that, I'm so sorry.
- How much Java Script
would you need to know to manipulate
Gutenberg to do things out of the box?
- So, none really.
'Cause as you see withparagraph block, right?
I mean it depends on whatyou mean by manipulate.
(announcer mumbles)
Do you mean...
When you say manipulate
'cause when I say manipulate,
I'm thinking I wanna change the background
or the text on a paragraphblock, for example.
You do need to know noJava Script to do that
because that's already an option.
If you might by manipulation mean
I want to make my own block
or I want to extend a block,
then yes, you will haveto know how to do that.
There's an amazing course,
I think he's giving a talk,
Zack Gordon's course?
I'mma give him a plug.
I would highly recommend to learn that.
He also, does a great Java scripts.
There so many differentlearning resources.
There's also the handbook.
Wordpress.org/Gutenberg,
that's where the handbook is.
So the link here has lots of resources
that you can get too as well.
- [Announcer] Zack Gordonis tomorrow morning
in this room 11:20.
There's also, some transcript materials.
- Yes.Yeah.
- [Announcer] Next question.
- Hey, Tammie.
Just wondering if you got
any plans in the future.
If you want to do like, a custom page
and we already have some blocks set up
for someone to edit.
You know like have choices like all pages.
or pages
like about pages justthings that people pages,
something like that.- Yeah.
- You already had a text,images sent out to people,
you have any plans todo that in the future?
- So, there are lots of plans.
In regards to,
so actually, what you can do now
'cause some post is for custompost types or templates,
you can do what I wassaying with the placeholders
when you just load it with specifics.
That's like step one.
Step two would belooking at layout blocks.
That's when, after the editor phase
which is want I'm part of.
Then, Western router, ML Choice
will be coming in
and they will be leading us
through the customization focus
for Gutenberg.
And, that's when we'regonna see a lot more
of that layout, that site building stuff.
But already, we have a tasteof that with placeholders
and page templating.
- Thank you.No problem.
- The very last row has a question
and the center ground.
- I tend to have betas,
gonna sell out
so, the certain page templates
or some custom protocol
only use, certain kind of layouts,
is there a plan,
so say certain custom post type wall
be allowed to use certain blocks
but not others?
Where as page code use all of them.
- So, blocks are gonnabe able to be user roles,
that's actually, I can'remember the name of it.
There's couple of different plugins
that people have beenexperimenting with this,
with block control.
I think it is called block control.
Or, something like that.
There's plugins people are doing
that you can do thatfinite control as well.
Which, I think is super interesting.
'Cause, often things happen in a plugin
that we then bring into core, right?
So, there's some greatcommunity experiments happening,
there's themes with blocks,
there's sweets of blocks
that do things that weare not providing in code.
It's really really interesting
in the plugin repository,
to already see what people are doing,
and outside as well.
- Okay, last row.
Yes.
- [Man] There's beenquiet a mixed reaction
with Gutenberg,
how is some of peoples frustrations
influence the design of it?
- Well with anything inthe community, we listen.
Right?
So, of course.
I don't think frustrationinfluences as much as,
hearing why someone is frustrated.
So, listening of course.
Everybody who is developing Gutenberg
has been listening.
So, absolutely the community has made this
what it is.
It's just not group of people,
who are locked away
and making this product.
We've been making it in the public
and we're making withthe help of contributors,
and there's been communityhave been helping this.
So, absolutely, everybodyhelps and progresses
the product.
Just like with WordPress, right?
- There's a question here.
- [Woman] Hi, that wasreally interesting talk.
As an agency, we publish websites for hire
and they just come back
and say we just need alittle bit of change.
If we build blocks in acertain way on the site,
and then we need to adjust those blocks?
Have you got any advice on how we should,
what sort of workflow we should use?
When we've got minor standing issues
you have to succumb to the text field
and how to block cares.
How could we simply managethat on the website?
- Can I pan out a little bit and say,
do you write your ownplugins at the moment?
Exactly the same then.
(gently laughs)
'Cause I just wanted to know
because basically,
I'm assuming you'd be doing,
you've been putting theblocks into a plugin.
- [Woman] It's one approach, isn't it?
- Yeah, yeah.
If you were doing that, the same.
How you update your plugins,
maybe you got multi side,
maybe you've got deploy mechanism
that you deploy
but its exactly the same.
The comments is actuallyan interesting one
to point up on.
So, there is like fall backs,
and backwards compatibility.
So you would have to recheck
if you changed everything
then of course you'regonna have an issue there.
We're looking at easier fall backs
for things like that and Gutenburg already
does some of those.
To reckon, I change it
'cause some of theseblocks are changing anyway
as the team we're working on this.
But, I think the commentsare in the editor
but the out put doesnot have those comments.
If you view source, they're not there.
They're just a way of saying, hey,
Gutenberg do this thing on the front
and hat's what it does, okay.(gently laughs)
- Okay, one more question back there.
- [Man] So, less of a question
more of a statement, really.
I've been reading, obviously,some of the reviews,
from time to time.
I just wanted to say
that you're a better person,
than what I am in responseto some of those reviews
and you everybody working on this project
is doing a pretty amazing job
regardless of what other people say.
- Thank you.(joyously laughs)
(audience clapping)
- All right this is my last question.
With Gutenberg would there be any need
for advanced custom fields then?
'Cause if you can create all these
edited boxes.
Why would you need advance custom fields?
- I think that's up to people to decide.
I don't wanna tell people
how to do any work flow.
I think what we are doing with Gutenberg
is we're giving a new set of tools,
and over time people aregonna work with that,
and in advanced custom fields,
you are looking at,
how can they work with Gutenberg?
How can they add things?
There's gonna be things
that Gutenberg doesn'tdo, like, blocks don't do,
extensibility, adding, converting.
Sites that already exist.
So, I think that's up to eachperson's individual work flow,
and I think that something as a community,
if you think,
the way that people originally
worked with WordPress few years ago
changes, right?
SO, that's something with Gutenberg,
we're gonna be finding these workflows.
- Thank You.
Anymore questions?
In the back again.
- [Man] Thanks, it was a great talk.
I just wanted to ask about multi site
and more complex WordPressset ups with blocks.
Is it something thatthey are looking into,
that you'll be able toshare blocks amongst sites,
so you can have an organization level,
set of shared blocks.
- I know that multi site is one aspect
that we're gonna have to outta the box,
work at least with multi site.
I don't know about the sharing.
That's actually an interesting aspect.
I'm not sure that's actuallycurrently worked on.
I would say its probablya version two or whatever.
But, I'm actually gonnafind that out for you,
and then I will try andtweet out that answer
because, I'm not sure specifically.
- Just to make sure,
anyone can make it better,
it's an old soul project.
When you first get it, just comment
or contribute.
Thank you very much.
- Thank you.(audience clapping)