►
From YouTube: Create:Editor Product/UX Weekly - 2021-01-27
Description
Weekly Editor group sync between Product, Design, and UX Research
A
Hello,
everyone:
this
is
the
editor
product
design,
weekly
meeting
for
january
27th
2021,
and
I
will
basically
turn
my
time
over
to
you
all,
because
I
just
put
a
couple
quick
agenda
items
and
none
of
them
are
really
worth
verbalizing.
All
that
much
I'll
be
putting
a
schedule
putting
a
meeting
on
the
schedule
for
kicking
off
the
wysiwyg
rich
text,
editor
for
breaking
down
iterations
and
look
forward
to
starting
that
work.
A
B
All
right,
so
within
the
design
world
last
week
was
last
weekend.
This
week
was
actually
dealing
with
other
teams.
Scenarios
with
settings
and
navigation.
So
first
up
in
navigation
is
the
one
team
looking
at
putting
import
and
create
links
into
the
drop
down
menu
and
how
that
may
pan
out
in
in
our
new
world.
B
So
the
current
direction
that
I
had
chatting
with
them
is
that
they
should
go
ahead
and
put
in
the
links
that
they
want
to
do
because
they're
solving
a
problem
for
their
users,
which
is
not
really
a
navigation
problem,
but
it's
like
they
want
to
put
the
links
in
there,
so
it's
exposed
so
that
that's
what
they
their
research
shows
that
people
are
naturally
looking.
B
Let
them
run
with
that
and
then,
when
we
cross
our
bridge
of
consolidating,
then
looking
at
how
potentially
that
would
look
with
their
thoughts
in
mind.
So
yesterday
did
some
iteration
on
that
which
is
actually
kind
of
doing
some
of
the
work
on
breaking
down
the
top
nav
work
as
well.
So
this
helps
with
creating
that
epic.
B
So
I'm
looking
to
get
that
out
later
today
or
early
tomorrow,
so
for
your
feedback,
eric
and
then
yeah
so
expect
that
later,
like
for
your
friday,
yeah
so
and
the
other
thing
I
was
looking
at
was
in
the
one
group
looking
at
the
allow
force
push
setting.
So
this
is
more
like
an
intricate
level
of
detail
for
for
settings.
B
Some
developers
have
fed
back
on
the
issue,
so
I'm
going
to
look
into
that
to
see
where
the
edge
cases
are,
which
is
also
useful
for
us,
because
it'll
be
pushed
down
on
certain
patterns
and
stuff,
it's
good
to
see
if
it
holds
up
in
real
life
scenarios
and
things
that
are
more
complicated
to
set
up.
So
I
think
these
were
two
really
good
things
to
stress
tests.
B
Some
of
the
thinking
that
we've
had
internally
within
our
group,
we
haven't
done
a
lot
of
externalized
externalizing
and
that
but
yeah
that's
coming
up
soon,
because
I'm.
B
Into
ux
research
was
last
week
I
like
quickly,
put
together
a
moderated
session
around
saving
and
updating
within
settings
and
kind
of
the
other
thing
was
the
use
of
toggles,
whether
we
should
keep
them
or
remove
them
and
yeah.
There's
some
good
signals
from
that
solution.
Validation
that
I
think
helps
solidify
my
thinking
around
the
ad
and
update
more
particularly
eric
around
you
know.
If
you
click
add,
then
we
would
show
it
in
line
as
a
first
step
and
then
the
future
step
could
be
like
a
modal
or
whatever
else.
B
I
think
that
is
the
right
direction
to
go,
as
in
the
ideal
state
should
be
a
modal
or
some
kind
of
thing
that
pops
out,
but
in
the
interim,
if
we
use
the
inline
view
that
that's
sufficient,
like
it's
usable,
it's
not
like
super
awesome
compared
to
the
other
stuff,
but
it
is
a
valid
it's
a
valid
solution,
especially
given
the
amount
of
places
we
have
to
implement
it.
It's
it's
not
a
bad
direction
in
the
spirit
of
mvc.
A
A
My
fear
was,
we
would
hit
the
same
milestone
right.
They
would
be
like
working
in
that
area
of
the
code
base,
try
and
merge
something
and
realize
we
messed
up
the
whole
top
now
for
them.
I
looked
at
your
proposal.
A
Work
on
that
in
1310,
but
yeah,
I
think
that's
going
to
be
a
really
good
change,
so
glad
you
were
able
to
to
work
in
their
needs
into
that
pattern
that
you've
already
tested
and
yeah.
Everything
else
sounds
great.
I'm
I'm
excited
to
see
the
the
unmoderated
user
testing,
giving
some
good
actionable,
or
you
know,
like
good
feedback
that
we
can
either
use
to
validate
or
or
or
adjust
our
proposals.
B
Cool
and
quickly,
on
the
ux
research
side,
there
was
a
homepage
redesign
survey,
which
was
essentially
a
banner
ad
on
the
home
page.
That
was
run
twice
for
30
minute
durations
last
year.
This
is,
we
got
like
36
results
and
I
just
spent
a
little
bit
of
time
to
put
together
the
findings
from
it
and
any
insights
from
it
itself.
B
So
that's
in
the
issue.
There
yeah,
I
think,
there's
some
stuff
that
have
come
up
in
the
past,
like
starring
things
and
remembering
stuff
like
that.
So
nothing
came
out
as,
like.
I
hear
surprise
for
us,
but
it's
more
signals
that,
like
yeah,
it's
still
coming
up
in
different
ways
like
the
different
like
now.
This
is
a
survey
and
the
same
kind
of
points
are
coming
up.
So
I
created
a
separate
issue
to
like
come
up
with
different
ideas
or
solutions
to
move
that
forward.
B
Yeah
because
I
didn't.
D
B
A
solution-
validation
per
se,
so
you
can't
say
like
yes
we're
going
forward
with
this.
So
that's
why
I
was.
I
broke
it
off
into
that
separate
issue,
yeah
and
upcoming
solution.
Validation.
Is
I'm
actually
going
to
think
about
using
an
unmoderated
session
to
look
at
like
merge
request
settings?
So
this
is
the
idea
of
like,
if
you're
looking
at
a
merge
request-
and
you
want
to
change
some
settings
about
it.
How
would
you
do
that?
B
B
You
know:
where
should
we
place
settings
should
it
be
within
the
left
menu
on
all
product
areas?
How
is
the
navigation
between
that
link
to
settings,
or
should
it
be
like
in
a
drawer
or
something
like
that?
So
that's
in
my
head.
That's
what
I'm
kind
of
trying
to
start
to
get
feedback
on
secondary
stuff
that
I'm
looking
at
is
a
setting
search
and
web
id
kind
of
stuff.
But
those
are
probably
looking
like.
Maybe
two
weeks
out.
C
B
No,
so
this
is
like
you're
within
the
merge
request
area
of
the
product.
So
yes,
so
from
there.
If
you
wanted
to
look
at
your
approval
rules
or
add
an
approver
to
the
list,
how
would
you
get
to
it
and.
A
B
Kind
of
that's
the
scenario
that
I'm
looking
for
so
it'll.
A
B
C
Do
you
think
maybe
some
things
from
the
category
maturity
scorecard
could
work?
I
remember
there
were
some
settings
related
to
code
owners
and
then
their
approval
ones
as
well.
So
we
can
talk
about
that.
More
okay.
C
Yeah,
oh,
is
it
is
it
on
to
me
now?
Okay,
I
think
it
is
so
I
update
that.
Actually,
this
is
a
good
segue,
so
I
launched
a
project
level
settings
tree
test
in
the
workshop
so
similar
to
the
things
that
I
did
for
the
project
and
group
level
left
sidebars.
C
I
thought
it
might
be
helpful
to
start
with
this,
so
that,
because
it's
a
it's
considering
the
entire
flow
of
things,
they
could
go
down
a
lot
of
different
paths
and
get
lost
if
I
did
an
unmoderated
study,
so
I'm
thinking
that
it
makes
sense
to
limit
it
for
the
general
one
and
then
do
the
unmoderated
ones.
For
the
the
more
specific
scenarios,
like
the
merge
requests
that
you
could
kind
of
form
them
a
bit
better.
C
But
if
you
want
to
take
a
look
at
some
of
the
results
that
are
coming
in,
you
can
use
that
link.
It's
still
actively
collecting,
but
just
in
case
you're
curious.
It's
it's
been
interesting.
So
far,
looking
at
some
of
the
the
tasks
like,
I
think
we're
going
to
get
some
interesting
things
around
what
people
expect
in
settings
general
versus
some
of
the
places
within
settings.
C
In
addition
to
the
question
of
settings
versus
the
feature
sections,
because
some
of
them
there's
a
lot
of
competition
within
settings,
you
know,
is
it
in
general?
Is
it
in
repository?
Is
it
in
access
tokens
things
like
that?
So
it's
been
interesting
so
far,
but
I
do
think
it'll
give
us
some
information
that'll
be
useful
but
yeah,
so
that
is
in
progress.
I'll
give
you
an
update
on
that
when
it
is
complete
and
yeah
other
than
that,
I'm
currently
working
on
sus
and
another
navigation,
related
survey.
C
There's
so
much
happening
right
now,
but
so
I'm
delayed
on
my
overall
navigation
analysis
but
I'll
resume
that
next
week
and
there
will
probably
be
more
to
consider
with
the
data
we
get
from
sas
as
well.
So
it
should
be
interesting.
C
I
think
this
one
is
for
me
this
one's
even
more
interesting
to
see
where
they
think
to
go,
because
you
have
some
cases
where
it
was
difficult
to
avoid
saying
the
actual
word
you
know
like
repo
mirroring
repository,
but
in
that
case,
when
there
was
one
that
might
prime
them,
I
tried
to
balance
it
by
saying
like
set
so
set.
Where
would
you
go
to
set
a
setup
repository
mirror?
C
It's
like
you
have
both
set
reminds
you
of
settings
and
repository
makes
you
think
of
repository,
so
that
was
kind
of
a
balancing
act,
but
it's
interesting
to
see
where
they
end
up.
Despite
these
things,
one
that's
pretty
interesting
is
the
task
of
where
would
you
update
the
description
for
your
project
so
far,
the
majority
is
clicking
on
project
details,
but
that
is
done
in
settings
general.
So
that's
another
one
that
might
be
a
little
more
clear-cut
than
some
of
the
others,
but
we'll
see.
A
So
this
is
unmoderated
correct,
so
you
didn't
watch
them.
Do
this.
C
Just
search
so
it
wouldn't
capture
whether
they're
searching
for
anything.
C
So
what
I'm
thinking
of
doing
is
looking
at
the
results
from
this
study
just
to
see
how
the
tasks
were
and
then
either
running
an
unmoderated
version
of
this,
where
they
do
this
same
study,
just
while
recording
themselves
or
using
this
set
of
tasks
and
having
them
do
it
in
get
lab.
I
haven't
decided
which
path
yet,
but
just
so,
we
can
get
more
context
to
the
thought
process
as
they're
doing
this.
That
might
be
a
follow-up
that
I
do.
A
Cool
yeah,
I
was
just
looking
at
this
paths
thing
and
I
was
just
wondering
how
many
of
them
even
thought
to
just
search
for
the
term
which
wouldn't
have
worked
in
a
lot
of
these
cases.
I
think,
but
would
have
been
curious
and
potentially
changed
if,
if
like
a
lot
of
them,
did
that
would
have
maybe
changed
how
we
prioritize
the
global
search
versus
just
like
fixing
the
ia
of
the
left
nav.
But
you
know
I,
this
is
great
and
it's
also
just
a
great
baseline.
C
C
C
B
Yep-
and
that
is
exactly
the
solution-
validation
that
I
want
to
do,
but
you
brought
up
a
good
point
about
whether
search
is
a
potential
option
or
like
would
people
go
there
immediately?
So
what
I
plan
to
do
for
that
in
the
unmoderated
one
is
that
if
they
click
on
search,
then
a
pop-up
appears
that
says,
like
hey,
looks
like
you
wanted
to
search,
please
verbalize
what
you
wanted
to
search
up
for
surprisingly,
with
the
unmoderated
testing
people
actually
speak
out
as
they
talk.
I
think.
A
B
Lot
more
than
actually
the
one-on-one
stuff,
so
maybe
they're
trained
like
user
testing
users.
That,
like
you
know
this,
is
how
you
get
paid
or
like
the
credit
for.
A
B
Work,
but
I'm
really
impressed
with
the
amount
of
work
that
people
actually
do
like
they
actually
yeah
spell
out
everything
they
read
out
the
questions
out
loud,
I'm
like
well.
This
is
much
better
than
when
I
was
doing
the
test,
one
so
yeah.
I
think
if
we,
if,
if
you
structure
an
unmoderated
one,
it's
it
could
be
as
good
as
like
a
face-to-face
one
but
yeah
you
can't
dive
deeper,
so
you
almost
have
to
like
anticipate
some
stuff
for
for
the
test.
I
did
for
the
adding
and
updating
one.
B
I
secretly
did
the
first
one,
which
was
just
adding
something
to
be
inline
and
then
my
follow-up
question
was
like
what
would
you
do
to
improve
it?
And
one
person
said
oh,
I
wish
this
could
be
like
a
pop-up
or
something
so
that,
like
I
maintain
focus,
I'm
like
yes,
because
the
next
one
was
like
a
pop-up
and
they
were
like.
Yes,
this
is
exactly
what
it
was
so.
A
C
A
D
C
Yeah
that
I
definitely
got
a
couple
of
comments
so
far
where
it
was
like
I
like
it
when
settings
are
configured
inside
the
repository
such
as
gitlab
yaml
or
the
issue
template
folders,
and
it's
like
very
specific,
okay.
Well,
thank
you
for
that
piece
of
information
and
then
another
one
was
like.
I
would
recommend
a
search
input
field
to
search
across
all
settings
like
jetbrains
products.
I'm
like
okay.
A
A
To
submit
a
fix,
it's
a
community
contribution
right.
A
Well,
thank
you
michael
for
thinking
about
that
and
your
testing
I'd
be
interested
to
see
if
people
click
on
the
search,
the
global
search
at
all
or
any
kind
of
search
that
you
display.
A
Awesome
well
yeah,
I
mean,
I
guess,
just
to
wrap
up
like
I
said
we,
because
we
we
we
spend
so
much
time
talking
about
settings
and
navigation
and
these
meetings
I
and
we
should
it's
a
very
it's
top
of
mind
for
you
both,
but
we
do
have
six
other
categories,
so
I
I
feel
like
I
should
represent
them
a
little
bit
in
the
conversation.
A
So
I
will
just
touch
on
what
I
said
again.
Our
hope
is
that
we
can
start
moving
on
the
rich
text
editor
with
wiki
as
the
target
category
for
our
our
you
know,
initial
nbc
starting
next
milestone.
So
I
was
talking
with
roman
about
this
and
I
think
we're
gonna
try
and
schedule
like
a
a
weirdly.
A
Structured
kickoff
meeting,
that's
also
like
issue
refinement
and
iteration
planning
with
enrique,
and
whoever
else
wants
to
join
next
week
to
just
dive
into
the
technical
details
about
like
what
we
need
to
do
starting
next
milestone.
We
don't
need
to
go
that
much
further
out
and
so
michael.
I
know
we've
talked
about
like
getting
a
mock-up
for
what
it
would
look
like
honestly,
I
think
enrique's
proof
of
concept
using
gitlab
ui
components
that
he's
already
put
together.
A
If
you
slap
that
in
the
wiki
that's
pretty
close
to
the
mvc
that
we
need,
but
you
know,
obviously
you
need
to
to
have
a
chance
to
have
input
there.
I
don't
believe
that
we're
at
any
risk
of
like
absolutely
needing
that
for
the
next
milestone,
though
there's
a
lot
of
foundational
work.
My
impression
is
that
we'll
need
to
do
so.
A
You're,
not
you're,
not
going
to
be
left
out
or
fall
behind
in
this
scenario,
but
I'll
keep
you
in
the
loop
and
certainly
if
the
meeting
aligns
with
your
awake
times,
it'd
be
great
to
have
you.
There
it'll
probably
be
more
like
technical
foundational
issues
that
we're
writing,
though
so
and
then
yeah
you
mentioned
web
ide
stuff.
We've
been
having
several
conversations
recently
about
a
couple,
a
couple
considerations
in
the
web
ide
that
will
probably
play
into
maybe
a
little
bit
later
this
year.
A
Maybe
second
quarter
this
year
in
planning
some
some
ux
improvements
that
we
could
do
there,
that
I've
looped
you
into
some
issues
michael,
but
we
can
talk
about
them
in
more
detail.
The
one
that
we
were
talking
about
over
the
past
couple
days
was
really
interesting
and
that's
the
idea
that
the
web
ide
could
be
used
by
people
who
don't
have
the
ability
to
push
commits
or
maybe
not
want
to
push
commits
with
their
edits.
And
so
what
kind
of
paths
can
we
give
them
instead
of
just
turning
off
the
web
ide?
A
A
If
you
can't
commit,
then
you
could
either
like
right
now
so
right
now,
if
you
can't
commit
if
it's
a
read-only
repository
or
if,
if
you
don't
have
permissions
to
commit,
you
can
fork
the
project
assuming
the
project
allows
forks,
and
then
you
can
obviously
edit
your
fork
and
and
create
a
merge
request
from
the
web
ide.
But
assuming
that's,
not
a
path
you
want
to
take
or
can
take.
A
It
would
be
kind
of
cool
to
be
able
to
edit
like
three
or
four
files
and
create
a
patch
file
to
include
and
send
to
an
engineer.
So
I
believe
that's
something
we'd
be
looking
into.
A
A
We
should
talk
about
the
the
the
usability
and
ux
around
the
the
combining
of
the
review
and
commit
tabs
and
what
those
different
paths
look
like
if
the
web
ids
in
different
states-
and
things
like
that,
so
you
know
when
you're
ready
to
take
a
breath
from
settings
and
nav
work,
I'm
sure
we
could
we
should.
We
could
kick
off
some
testing
and
and
design
ideation
around
that.
B
Yep,
oh,
that
is
bundled
you
know,
with
the
direction
that
I
had
with
the
web.
Id
testing
things
yeah,
I
think
when
I'm
at
preview
is
yeah,
is
that
editor
review
commit.
A
B
A
And
I
think
in
general,
like
there's
just
like
a
maybe
some
some
thought
around,
like
the
state
and
the
different
paths
that
you
take
within
the
web
ide
given
different
permissions
and
different
places
where
you
want
the
code
to
end
up.
Another
thing
we
talked
about
is
like
what,
if
you
wanted
to
take
your
changes
and
create
a
multi-file
snippet
out
of
it
and
or
take
that
patch
file
and
create
a
snippet
from
the
patch
file
and
then
save
that
so
like
a
little
bit
more
integration
with
our
other
categories
and
potentially
enabling.
A
I
don't
know
if
intimidated
is
the
right
word
but
like
the
the
friction
to
actually
creating
a
merge
request
might
be
too
high
and
they
might
either
reach
a
dead
end,
because
their
role
prevents
them
from
creating
creating
that
or
they
may
feel
uncomfortable
with
it,
and
just
want
to
like
share
this
in
some
other
way.
A
Another
use
case
they
brought
up
today
was
that,
like
during
code
review
engineers
in
our
organization
and
our
team,
even
or
our
group
will
sometimes
create
patch
files
as
part
of
the
review
process
and
be
like
hey,
you
know
like
if
you
did
it
this
way
it
might,
it
might
be
better
and
I've
already
kind
of
made
those
changes
and
if
you
want
to
just
apply
them,
here's
some
here's
the
patch.
A
So
it's
a
it's
an
interesting
use
case.
Obviously
one
we
wouldn't
want
to
just
rush
into,
but
I
think
if
we
got
the
mvc
behind
a
feature
flag,
we
could
probably
test
it
pretty
easily
to
see
if
people
would
understand
it,
and
then
we
can
craft
the
the
use
the
ux
around
the
effort
that
you
already
have
in
play.
I
think.
B
Yeah
those
are
really
interesting
scenarios.
I
never
thought
about
it
from
that
angle.
So,
thanks
for
sharing
and
yeah
it
would
be
a
a
nice
side
break
another
thing
to
look
at
so
yeah.
A
Not
that
you
need
more
work,
but
if,
if
it
gives
you
a
chance
to
step
away
and
think
about
something
else,
then
I'm
happy
to
to
chat
about
it
anytime.
So
there
is
an
issue
for
the
patch,
I'm
gonna
start
refining
it
a
little
bit
and
I'll
I'll
ping.
You
on
that,
and
I
think
it
even
got
assigned
to
you
during
our
issue
refinement.
So
you
might
just
see
it
in
your
notifications.
So
just
back
your
mind
not
top
priority,
but
something
we're
thinking
about
right
now:
okay,
cool
and
we're
over
time.
A
A
Yeah-
and
I
guess
I'll
I'll
see
you
all
next
week,
most
likely
looking
at
the
calendar
but
have
a
great
rest
of
your
week
and
rest
of
your
day.
I'll
see
you
on
slack.