►
From YouTube: Create:Editor Product/UX Weekly - 2021-03-30
Description
Weekly Editor group sync between Product, Design, and UX Research
A
All
right,
hello,
everyone!
This
is
the
editor
group
product
design,
ux
research,
weekly,
sync
call
for
march
31st
2021.
I
don't
have
any
topics
on
the
agenda
so
I'll
hand
it
over
to
michael
go
ahead.
Man
yeah.
B
Yep,
so
we
jump
straight
into
the
world
of
research
this
week
and
we're
taking
our
lens
off
from
settings
and
navigation
for
a
short
few
days
to
look
at
the
web
ide
and
the
editing
experience
for
exploring
how
we
might
edit
using
like
a
rich
text
editor
so
for
the
web
id
one.
B
What
I'm
actually
looking
at
for
that
one
is
exploring
dennis's
proposal
of
removing
the
one
tab
of
at
the
moment
we
have
like
code
review
and
changes
or
commits,
and
so
those
three
tabs
and
then
become
one.
B
What's
that
called
is
kind
of
part
of
the
solution,
validation,
but
there's
also
another
proposal
that
was
created
a
few
months
before
we
started
becoming
the
consolidated
group
of
the
editor
and
in
that
one
designer
mike
there
not
me,
was
looking
at
potentially
moving
completely
away
from
the
layout
that
we
have
now
and
then
presenting
things
into
separate
lists
of
like
changes
and
files.
B
So
more
humanistic
labeling
on
our
web
id
thing
once
you
get
into
it
so
played
around
with
some
of
those
explorations
and
I'm
testing
out
how
tree
whether
we
should
have
a
tree
navigation.
You
know
when
we
shield
changes-
or
you
know
the
alternative
to
that-
is
doing
what
they
do
in
visual
studio
code,
where
you
just
list
the
files
and
then
you
have
like
the
path
to
the
file,
and
you
know
kind
of
like
grayed
out
text,
there's
pros
and
cons
to
both.
So
that's
what
the
solution.
B
Probably
likely
we're
going
to
remove
the
tab,
but
is
more
like
future.
Looking
of
like
okay,
which
direction
of
that
future
state
of
making
the
web
ide
a
little
bit
clearer
to
work
with,
would
we
be
going
towards,
and
that
was
one
of
the
questions
like
do.
We
make
the
one
step
to
remove
the
tab
now
and
then
do
all
this
logic
to
change
it,
or
do
we
just
make
the
giant
step
to
jump
to
the
other
ideal
state
so
that
that's
the
root
cause
of
that
web
id?
B
The
editing
experience
one?
Is
it's
really
fun
because
that's
gonna
be
a
solution,
validation
where
we're
actually
gonna
get
people
to
type
using
the
tip
tap
framework
so
putting
together
example
of
all
the
things
we
want
in
our
editors
and.
C
B
C
B
C
B
Something
you
can
do,
it's
just
going
to
be
go
ahead
and
do
it.
Things
will
appear
like
speak
out
loud
and
tell
us
what
you
expect
to
happen.
So
that's
kind
of
the
direction
of
that
experience
so
working
on
that
at
the
moment
and
then
hoping
to
get
that
out
early
next
week
on
tuesday
wednesday
because
of
the
long
weekend.
B
So
that's
the
things
in
in
that
area
and
then
once
that
happens,
then
I'm
probably
gonna
shift
back
a
little
bit
to
setting
the
nav
to
handle
any
solution,
validations
that
could
be
done
now
and
most
more
on
the
documentation
side
moving
forward.
So.
A
Yeah,
that's
great.
I
just
made
a
couple
notes,
as
you
were
talking
and
thank
you
because
actually,
the
other
topic
that
I
couldn't
remember
that
I
wanted
to
bring
up
was
one
of
the
ones
you
mentioned.
So
I
did
finally
get
to
watch
that
video
of
you
and
and
mike
the
the
two
michaels
talking
about
web
id
was
really
a
good
video.
It's
on
our
playlist
for
anybody
watching
along
here
go
back
and
watch
it.
It's
very
insightful.
A
I
was
especially
interested
both
in
the
consolidated
like
sidebar,
but
the
the
explorations
for
like
a
split
action
button,
depending
on
where
we
go
with
our
different
paths.
We
have
like
an
issue
in
the
backlog
for
generating
like
patch
files
from
the
web
id.
If
you
can't
commit-
or
maybe
you
can
commit-
or
you
know,
saving
those
two
snippets
or
you
know
generally
alternate
paths
other
than
committing.
A
To
be
frank,
I'm
still
a
little
concerned
about
introducing
a
modal
there,
but
I
can
be
swayed
I'm
I'm
biased
against
modals,
but
right
now
I
guess
the
like
sliding
tray
is
effectively
a
modal,
it's
just
not
taking
over
the
screen,
so
six
and
one
half
a
dozen,
the
other,
but
otherwise
yeah.
I
think
I'm
really
excited
in
that
direction.
I
think
it
is
a
great
place
we
could
be
investing
in
after
we
hit
our
goals
for
14.00
and
turn
our
eyes
back
to
the
web
ide.
A
A
And
then,
as
far
as
the
tip
tap
editing
experience,
two
updates
on
that.
I
saw
your
message
about
the
toolbar
and
using
that
as
the
mvc,
I'm
I'm
comfortable
using
that,
so
that
we
can
keep
moving
forward,
knowing
that
we
might,
depending
on
the
outcomes
of
this
research,
just
shift
our
longer
term
goal.
Even
if
we
have
to
have
our
first
couple
mvcs
using
the
toolbar
and
then
re
redo
some
work.
Hopefully
it
won't
be
too
much
lost
work.
A
I
still
maintain
that
an
ideal
framework
would
the
consumer
of
the
editor
as
you're
instantiating
it.
You
could
potentially
opt
into
either
experience,
because,
if
we're
going
to
make
it
reusable
across
gitlab,
there
might
be
times
where
the
toolbar
is
more
is
more
fits
better
with
the
use
case.
I'm
thinking
like
comments,
and
things
like
that.
A
So
I
don't
think
it'd
be
necessarily
wasted
work
to
move
forward
with
a
toolbar,
but
I
think
for
longer
form
writing.
My
hypothesis
is
that
the
block
editor
will
be
more
enjoyable,
but
I'm
good
with
waiting
on
the
outcomes
of
that
research
and
see
if,
if
everybody
else
agrees
and
then
also
separately-
and
maybe
this
doesn't
need
to
be
recorded.
But
I
managed
to
get
in
touch
with
the
tip
top
maintainers.
The
folks
that
made
tip
tap
and
have
email
contact
with
them.
A
B
Cool
yeah
now
that
that
comment
around
consolidating
the
commit
experiences
is
probably
going
to
be
a
really
fun
one,
also
from
a
collaborative
collaboration
standpoint
with
the
pipeline
editor
team
who's.
Also,
looking
at
this,
so
yeah
yeah,
there's
fun
things
coming
up
over
the
next
few
months.
A
Yeah
or
next
year,
so
you're.
Actually
I've
got
some
notes
that
I
made
right
after
your
meeting
because
I
couldn't
help
it.
But
I
have
like
this.
A
I
don't
know
if
the
lights
go,
this
outline
of
all
the
different
like
areas
of
the
editor,
the
components
that
we
that
we
need
to
kind
of
split
up
and
and
make
like
make
progress
towards
more
modular
experiences,
so
that
our
our
vision
of
in
context,
editing
where
an
editor
can
progressively
become
more
complex,
as
the
use
case
needs-
and
we
don't
have
such
a
clear,
like
distinction
between
web
ide
and
single
file
editor-
and
you
know
we
can
be
a
little
more
nebulous
there-
there
there
are
different,
maybe
modes
or
modules
or
whatever,
that
I
was
sketching
out
after
kind
of
inspired
by
your
talk.
A
B
C
Yeah,
my
last
one
is
more
of
an
fyi
so
on
the
trying
to
get
ahead
of
maybe
some
of
the
conversations
that
michael
might
have
as
part
of
the
mock-up
work
for
the
the
proposal
for
the
left
nav.
I
want
to
kind
of
look
to
see
if
I
can
gather
existing
analytics,
related
research
and
kind
of
explore
some
of
those
questions
before
I'm
out
of
office
and
then
I'll
be
gone
for
a
little
bit
and
then,
when
I
come
back,
I
plan
to
to
pick
up
just
like
the
work
on
evaluating
that
proposed
structure.
C
C
A
Should
I
should
next
week
I
didn't
realize
next
week
is
my
son's
spring
break.
I
thought
I
had
a
little
more
time,
but
I'll
probably
be
in
and
out
partially
I'll
try
and
be
responsive,
though
it's
not
official
vacation
but
we'll.
A
He's
in
preschool
they're
taking
friday
off
so
and
then
the
whole
following
week
and
they're
back
in
on
the
monday
after
so
it's
six
days
off
school.
But
you
know
it
spans,
like
nine,
nine
or
ten
days.
B
Cool
yeah
this
this
year's
my
daughter's
first
year
in
like
school
school
in
australia,
and
they
they
have
two
weeks
breaks
every
quarter
so
so
like
now
they
get
two
weeks
and
then
they
get
another.
Two
weeks
later,
I'm
like
oh,
that's
kind
of
cool
that
things
are
consolidated
like
that
and
then
yeah
when
it's
winter
in
north
america,
it's
summer
here,
so
they
they
get
their
longer
break
there.
So
I'm
like!
Oh
it's
it's
a
different
structure
from
what
I
grew
up
but
yeah.
B
A
Chad,
before
we
wrap
anything
anything
you
want
to
bring
up.
No
thanks
for
all
the
hard
work
thanks
for
joining.
Thank.
C
A
Thanks
everyone
for,
for
your
chat
and
I'll,
see
you
well.
Maybe
we
should.
It
sounds
like
catherine
you'll
be
out.
We
could
probably
just
do
this
async
next
week
in
pick
it
up
the
following
week,.