►
From YouTube: Create:Editor Product/UX Weekly - 2021-06-09
Description
Weekly Editor group sync between Product and Design
A
All
right,
hello,
everyone-
this
is
the
product
and
design
sync
for
the
editor
group,
it's
june,
9th
2021
and
I'll
jump
right
into
my
agenda
items.
So
the
the
one
thing
I
wanted
to
highlight
is
that
I'm
still
working
on
the
communication
plan
for
our
upcoming
features
in
140.
A
B
A
In
the
wiki
now
that
that's
turned
on
for
everybody
on
gitlab.com,
so
I
think
that's,
I
created
a
feedback
issue
for
it
already.
So
we
just
need
to
link
to
the
feedback
issue
in
that
message
that
we
talked
about
putting
in
the
content
editor
and
then
in
the
feedback
issue.
I
was
going
to
potentially
link
to
a
video
and
like
the
direction
page,
which
both
I
need
to
create,
hopefully
by
the
end
of
the
week.
A
So
I
will
today
finally
get
around
to
creating
an
issue
that
has
an
outline
of
what
I
would
want
to
talk
about
in
a
short
video
like
like
less
than
five
minutes
and
I'll
ping,
you
on
that,
and
we
can
make
sure
we
cover
all
our
bases
and
I'm
representing
it
accurately,
and
then
we
will
I'll
record
it
probably
friday,
along
with
our
kickoff
video.
A
So
if
that's
good,
then
I'll
do
the
same
for
navigation
and
settings
on
the
top
bar
and
we
have
an
issue
for
creating
a
broadcast
banner
on
gitlab.com
for
the
new
navigation.
So
that
will
be
the
one
I'm
going
to
follow
up
today
and
make
sure
that
we
don't
miss
for
for
the
for
shipping.
A
If
it
needs
to
get
done
by
the
cutoff
for
the
build
there,
then
I'm
not
sure
what
engineering
needs
to
go
into
creating
that
alert,
but
that'll
be
something
for
me
to
work
on
today.
A
Yeah,
I
think
the
the
key
thing
here
that
I
want
to
try
is
linking
to
the
feedback
issues
in
both
cases,
so
that
we
can
have
a
single
place
to
let
everybody
voice
their
opinions.
Point
out
bugs
or
otherwise
ask
questions
so
that
we
can
head
off
conversations
that
go
off
the
rails
on
hacker
news
or,
like
you
know,
people
feeling
like
they
are
surprised
by
changes
and
it
weren't.
You
know
something's
not
working
to
their
expectation
or
whatever
meeting
their
expectations.
A
So
yeah
trying
to
wrap
that
up
this
week
because
I'll
be
out
next
week
and
we're
shipping
soon.
A
I
gave
a
little
more
thought,
shifting
gears
to
the
embedding
snippets
stuff
that
we
talked
about
last
time
and
I
refined
the
issue
a
little
bit,
but
I
still
feel
pretty
good
about
our
approach
right
now,
which
is,
let's
think
about
this
in
an
ideal
you
know
mature
state
and
then
in
14,
1
I'll,
be
coaching
product
manager,
intern
and
and
then
in
that
milestone,
we'll
work
on
carving
out
what
the
actual
first
mvc
looks
like
that'll,
be
part
of
his
task
and
I'll
work
with
him
through
that.
A
We
don't
need
to
come
at
this
from
both
directions.
I
think,
let's
focus
on
how
we
think
embedding
content
specifically
snippets,
but
how
we
think
that'll
work.
We
could
even
assume
that
we've
already
got
the
block
based
editing
in
place.
If
you
want,
because
I
think
that's
pretty
certain
that
we're
going
to
head
in
that
direction,
I
and
then
as
part
of
the
mvc,
we
can
say
like
well.
What
does
it
look
like
if
it's
in
the
toolbar
and
or
something
like
that
right
so
yeah?
That
would
be.
A
That
would
be
helpful
to
get
a
little
thought
put
into
that
while
I'm
gone,
and
then
we
could
sync
up,
maybe
when
I'm
back
at
the
end
of
towards
the
end
of
june.
But
if
you
do,
I
know
you
have
a
lot
on
your
plate.
If
you
don't
have
time
for
that,
we
could
also
potentially
schedule
like
just
a
like
a
whiteboarding
session,
like
you
and
me
sometime
when
I'm
back
and
just
kind
of
loosely
map
it
out.
That
might
be
enough
direction
and
just
carve
out
like
90
minutes
or
something
like
that.
B
All
right,
so,
when
you
were
updating
this,
this
issue,
were
there
questions
that
you
have
around
what
users
want
or
like
the
pain
points
that
they're
trying
to
solve.
Is
it
just
because,
where
I'm
going
with
this
is
like
yeah,
it
feels
like
the
flow
seems
all
right
and
at
the
moment
there
isn't
any
adding
a
snippet.
B
So
it's
like
if
we
want
to
get
some
user
feedback
on
some
ideas
right
now,
we
can
probably
put
together
something
maybe
the
week
that
you're
back
so
that
we
can
get
the
ball
rolling
so
that
when
you
have
that
discussion
with
the
intern,
there's
actually
like
a
user
perspective
on
the
problem,
rather
than
saying.
A
B
We
have
snippets
and
we
want
to
add
them
inside
the
wiki.
We
know
it
happens.
It's
just
really
painful
right
now,
so.
A
Yeah,
so
I
think
the
more
I
dug
into
this,
the
more
there's
there's
two
there's
two
pain
points,
one
embedding
a
live
like
an
actual
embedding
of
a
snippet
requires
a
script
tag,
so
there
are
places
where
that
isn't
going
to
work
either
somebody's
blocking
our
javascript
or
it's
not
rendered
like.
I,
I
don't
think.
Actually
I
didn't
even
try
it
on
the
handbook.
A
It
should
work
on
the
handbook,
but
regardless,
like
there
are,
there
are
environments
where,
like
embedding
a
student
is
not
possible,
so
you
would
have
no
capability
of
executing
the
script
to
embed
a
snippet
that
stays
up
to
date.
So
that's
pain,
point
number,
one
which
is
more
of
a
technical
problem
that
we
need
to
solve
and
like
viewing
the
documents
and
in
certain
environments,
but
there's
the
the
actual
problem
to
solve
for
the
the
use
case
of
actually
using
it.
A
A
Accessing
exam
code,
examples
that
you
might
reference
in
multiple
places,
but
it's
important
to
keep
them
up
to
date.
So
if
you
take
the
case
of
like
an
api
documentation
page
or
something
like
that,
you
might
have
snippets
where
in
a
static,
wiki
or
or
like,
if
you're,
just
writing
markdown,
you
would
write
a
code
block
and
you
would
paste
your
code
in
and
say
this
is
the
script
to
start
the
server
and
then
later
on
in
the
document
you
might
say
this
is
like
you
know
how
you
update
and
etc
right.
A
A
A
Then,
as
I
update
the
snippet,
it's
updated
everywhere,
I
used
it.
Maybe
I
can
have
multi-file
snippets,
which
is
nice
too,
and
then
I
think
the
the
other
benefit.
This
isn't
necessarily
a
problem
to
solve
pain,
point
right
now,
but
the
other
benefit
we
could
achieve
down.
The
road
is,
as
we
make
snippets
better
the
functionality
within
the
content
editor
and
any
place
that
uses
the
content.
Editor
improves
as
well.
A
So,
for
example,
we
start
having
snippets
that
can
be
that
can
run
like
evaluate
the
code
itself
or
you
could
like
run
a
javascript
and
have
basically
like
a
little
code,
sandbox
embedded
in
in
your
documentation
page
or
you
could
have
a
more
enhanced
sharing
options
or
just
like
smaller
things,
like
code
themes
and
color,
color
themes
and
stuff
like
that.
So
that's
that's
kind
of
the
motivation
and
obviously
all
of
that's
validated
only
by
anecdotal
experience
and
and
our
existing
backlog.
B
Cool
yeah
thanks
for
that
background.
Those
examples.
B
Yeah,
so
on
my
side
with
that
now
I
I
I
didn't
have
time
to
take
a
look
at
the
embedding
snippets
stuff
so
I'll
take
a
look
at
some
kind
of
like
what
I
did
with
the
content.
Toolbar
exploration,
it's
just
kind
of
high
level,
thinking
around
that,
so
that
we
have
tangible
items
for
you
for
us
to
discuss
this
when
you
come
back.
So
let's
aim
for
that
because
yeah,
I
think
we're
both
kind
of
busy
this
week.
A
Yes,
that
sounds
good
and
then
the
last
on
my
agenda.
We
can
probably
do
most
of
this
async
in
the
issues
in
planning,
but
the
plan
was
to
move
off
of
settings
and
navigation
focused
work
and
pick
up
some
of
the
other
categories
in
fourteen
one.
There
are.
There
is
inevitably
some
carryover
work
like
we
have
to
remove
some
feature
flags
and
do
a
little
bit
of
potentially
a
little
bit
of
work
that
didn't
make
it
into
14-0.
So
we
should
have
a
discussion.
A
I
see
that
you
link
to
the
epic
where
we're
collecting,
refinements
to
the
top
nav
and
sidebar
I
mentioned
before
we
hit
record
I'm
going
to
have
a
pretty
high
bar
for
for
what
will
make
the
cut
for
14,
1
and
14
2,
but
there's
there's
likely
some
work.
I
think
a
good
candidates
to
put
in
here
or
to
schedule.
A
Yeah,
I
think
that's
an
example
of
like
the
kind
of
work
that
I
would
prioritize.
I
don't
I'm
still
on
the
fence
on
when
and
if
we
should
tackle
the
group
sidebar
refactor.
So
one
we'll
talk
about
that
in
the
issues,
though,.
B
All
right,
it
sounds
good
all
right,
so
now
I'm
switching
it
over
to
design
and
research
yeah.
So
first
question
is
now:
if
we're
shifting
gears
towards
editor
of
priorities,
one
of
the
things
that
have
has
been
in
the
backlog
of
thinking
about
things
is
the
commit
flow.
So
when
you
make
some
changes
in
the
wiki
and
you
submit
the
changes,
there's
a
text
box
for
commit
like
a
commit
message:
yeah.
A
B
B
So
we're
yeah
try
to
figure
out
kind
of
take
an
audit
and
then
yeah,
maybe
next
week,
an
activity
for
myself
is
just
to
dig
through
to
see.
If
there's
any
related
issues
don't
commit
flow
ideas,
but
I
don't
think
there
is
much
but
yeah.
A
Yeah,
I
I
think
that
would
be
really
helpful
to
just
throw
out
a
whole
bunch
of
ideas
and
get
some
of
the
engineers
who
may
have
been
thinking
about
this
before
we
even
arrived
in
this
category
to
to
share
their
thoughts.
I
did
see
in
the
web
ide
strategy,
epic,
something
about
improving
the
merge
request
process,
so
there
might
have
been
epic
merging
this
workflows,
but
also
I
found
a
an
issue
in
our
triage.
A
All
right
so
there's
the
related
epic
for
the
web
ide.
I
don't
know
if
it's
got.
This
doesn't
have
much
in
it,
but
it's
something
and
then
I
was
triaging
a
feature
request.
That
was,
it
was
interesting
because
it
it
was
the
almost
exactly
the
use
case
we
were
talking
about
for
the
static
site
editor.
It
was.
A
Somebody
wanted
to
edit
the
get
lab
docs
site
and
they
found
a
small
typo
and
they
said
it's
too
much
work
to
clone
the
repo
start.
My
local
dev
environment,
create
you
know,
make
my
changes,
create
a
merge
request
and
then
go
through
that
whole
process.
So
their
proposal
was
like
just
let
me
click
a
link
and
like
bring
up
a
text
view
and
let
me
edit
it
and
then
have
a
streamlined,
merge,
request
process
and
I
was
like
actually
we
were
we're
working
on
almost
exactly
this.
A
It's
not
integrated
into
git
lab
docs,
but
like
keep
an
eye
on
these
categories
because
we're
thinking
about
these
problems.
So
it
was
a
little
bit
of
validation
for
for
that
for
that
use
case
and
that
problem
to
solve
that
we
we've
been
thinking
about
for
18
months,
but
it
did
have
me
thinking
like
there
is.
I
think
they
also
it
got
created
in
the
wiki
category
within
with
the
labels,
and
so
they
were
saying
like
it'd,
be
great
to
do
this
in
the
wiki
as
well.
A
B
It
was
interesting
so
and
that's
so
in
that
scenario
it
was
actually
like
long
pages
still
like
a
page
with
many
many
sections
so
like
if
you're
going
to
edit
it.
That
idea
was
like
I
just
want
to
edit
this
one
section
and
then
I
could
edit
it
and
then
submit
the
changes
and
not
have
to
open
up
the
whole
file
find
where
I'm
at.
So.
I
think
it's
a
similar
problem,
different
solution,
but
it
is
an
interesting
idea.
B
Yeah,
it's
it's
almost
like
taking
suggests
suggested
changes
from
the
mr
world
by
applying
it
to
like
an
editing
world.
Yes,.
B
A
A
How
about
streamlined
so
this
one
was
the
one
that
I
saw,
and
actually
it
was
enrique
that
that
ping
being
on
it
because
he
was
triaging
actually
now
that
I
remember
we
were
both
doing
triage
at
the
same
time,
but
we
can.
We
can
look
through
that.
I
ended
up
closing
it
because
it's
roughly
a
duplicate
of
the
work
that
we
want
to
do.
A
I
included
links
to
our
strategies.
All
that
said.
We
should
think
about
the
commit
flow
updates
when
I'm
back.
I
think
that
would
be
great
work
to
start
planning
and
validating
and
I
think
there's
there's
a
lot
of
great
work
to
be
done
so
yeah.
B
B
Yeah,
so
I
sense
is
it's
kind
of
my
new
toy
for
this
week.
So
thanks
to
the
work
of
the
engineers
on
our
team,
we.
Finally
we
we
did
a
lot
of
work,
the
top
nav
to
take
a
look
at
tracking.
You
know
your
project
startup
projects,
the
user
menu.
I
don't
think
we've
gone
into
the
detail
of
each
individual
top
nav
item
like,
for
example,
community
forum,
like
how
many
clicks
on
that.
I
don't
think
it
goes
down
to
that
deep.
B
I
I
haven't
checked,
because
I
I'm
not
focused
on
that
right
now.
I
was
more
curious
with
the
top
now,
with
with
the
frequency
of
like
recently
visited,
frequently
visited
links
versus
other
links
on
the
page.
B
Search
was
used.
How
often
that's
used,
so
we
don't
have
like.
We
have
like
a
volume.
We
can
check
volumes,
but
yeah,
probably
nothing
much
more
than
that.
There's
not
a
lot
of
like
you
can't
tie
sessions
together.
So
you
can't
say:
okay,
people
who
looked
at
search
also
clicked
on
this
or
anything
like
that.
So
right.
A
B
Gives
us
interesting
signals,
so
one
of
the
big
ones
was
fran
actually
closed,
the
instrumentation
ticket
for
left
sidebar
and
then
in
there
we
talked
about
tracking,
expand,
collapsed
flyout
or
like
the
nest
in
menu
and
the
the
events
that
fran
was
able
to
capture
for
us.
Yeah
helps
with
answering
that
question
which
is
exciting.
For
me.
I
posted
my
initial
kind
of
analysis
on
it.
It's
very
rough,
but
you
can
jump
into
it
to
see
if
there's
any
like.
B
Any
blind
spots
that
I
am
missing
or
jumping
to
conclusions
on
certain
things
or
like
one
thing
that
jeremy
brought
up
just
recently
before
this
call
was:
oh:
does
this
data
filter
out
bots
and
ui
test
testing
frameworks
right.
A
B
So
I'm
not
sure
but
yeah.
This
is
the
kind
of
stuff
that
would
be
good
to
have
so
that
we
can
make
the
data
as
real
as
possible,
like
as
clear
as
possible
for
us
to
make
a
decision
at
the
moment,
I'm
taking
I'm
looking
at
them
as
relationships
or
like
sizing.
So,
for
example,
if
if
start
project
has
like
five
times
as
more
clicks
as
or
your
projects
has
about
five
times
as
more
as
like
start
projects,
you're
like
that's
interesting,
so
is
that
big
yeah.
B
A
These
are
already
great
data
to
see,
I'm
really
surprised,
but
also
not
surprised
about
how
how
low
the
mobile
events
are
like
how
infrequently
some
of
this
nav
is
used
on
mobile,
but
that
makes
sense
given
the
complexity
and
how
how
low
our
mobile
usage
is
in
general
yeah,
I'm
gonna
dig
into
these
dashboards
and
and
I'll
leave
some
feedback
on
the
issue
as
well.
A
A
B
A
Yeah,
I
will
I'll
take
a
look
at
those
yeah,
absolutely
cool.
I
have
to
jump
for
an
interview
in
three
minutes,
so
anything
else
before
I
do
that.
B
Nope
yeah-
that's
pretty
much
it
for
this
sync
section.
So
all
good.
A
Cool
well,
I
will
probably
be
pinging,
you
a
whole
bunch
over
you
over
your
night
and
into
tomorrow.
So
I
expect
a
lot
of
to
do
but
they're
mostly
going
to
be
fyis
or
for
for
feedback
on,
like
our
the
outlines
for
our
communication
strategy
and
stuff.
So
hopefully
it's
not
too
overwhelming,
but
have.
A
And
talk
to
you
soon.