►
From YouTube: Create:Editor Product/UX Weekly - 2021-06-30
Description
Weekly Editor group sync between Product and Design
A
All
right,
hello,
everyone.
This
is
the
editor
group
product
and
design
sync
weekly
meeting
and
I
usually
dominate
the
top
part
of
the
agenda.
So
I
was
just
gonna
turn
it
over
to
you.
B
Michael
thanks
for
that
eric,
so,
first
of
all,
thanks
for
feeling
a
lot
of
the
feedback
from
the
14.00
release
with
respect
to
the
top
tab
in
the
sidebar,
so
lots
of
constructive
feedback,
which
is
really
helpful
for
the
team.
So
this
week
took
a
look
at
refining
the
styling
for
the
themes
and
the
colors,
so
that
issue
is
good
to
go
so
I'll
update
the
badge
on
that
after
this
call,
but
yeah
that
one's
good
to
go.
B
Some
of
the
feedback
about
the
larger
screens
was
something
that
I've
been
talking.
I
talked
to
paul
about
last
night
and
like
we
talked
about
like
some
ideas
around
that.
So
that
seems
pretty
interesting
that
we
can
iterate
upon
that
in
the
future.
B
I'll
also
talk
to
paul
about
patching
snippets
questions
from
the
web
ide
and
whether
it's
a
good
idea
or
not
a
good
idea
and
like
the
general
flow,
I
have
a
better
understanding
of
that
whole
flow
from
a
developer's
standpoint
and
I'll
look
to
refine
what
I
took
a
blind
stab
at
last
week
of
like
creating
the
flow
for
that.
So
I'll.
Look
at
refining
some
of
that
over
the
next
day,
because
I'm
off
on
friday.
A
That's
great
I've
been
really
enjoying
watching
the
conversation
async
in
that
issue,
so
I'll
look
forward
to
seeing
how
you
synthesize
that
conversation
with
paul
because
clearly
like
there
was
more
to
it
really
the
problem
area
that
I
was
looking
at
when
I
created
the
issue
and
kind
of
started
thinking
like
we
should
pick
this
one
up,
it
was
more
like
hey.
If
you
maybe
don't
want
to
commit,
there
might
be
something
else
useful
you
can
do
with
that,
but
you
know.
A
Obviously
there
were
there's
some
like
more
involved
considerations
that
have
been
coming
up
in
that
thread
and
and
for
those
that
haven't
been
following,
like
the
reason,
the
other
reason
it
came
up
is
because
we're
doing
something
in
the
vs
code
extension
to
create
patch
snippets
from
the
from
vs
code
that
you
can
just
like
kind
of
retrieve
quickly
and
insert
right
in
the
editor
and
the
ide,
and
we
thought
well.
A
B
Yeah,
so
so
my
takeaway
from
that
right
now
is
that
snippets
creation
also
depends
on
the
project
having
snippets
enabled.
So
it's
it's
something
that
you
we
need
to
do
a
check
for,
and
we
need
to
account
for,
for
if
we
do
want
to
introduce
creation,
a
snippet
somewhere,
whether
creating
a
snippet
while
you're
committing
something,
is
the
right
idea
or
not.
It's
like
probably
something
to
be
determined
further
for
us,
but
the
patch.
C
B
So
instead
of
making
multiple
comments
and
suggestions,
you
could
just
create
a
patch
file
from
the
web
ide
and
then
bring
that
over
into
the
world
of
emergency
press
review,
and
just
had
that
one
comment
and
then
the
person
reviewing
can
then
decide
whether
to
apply
that
patch
and
thus
see
the
difference
or
just
look
at
the
file
itself.
So
it
opens
up
the
doors
for
that
kind
of
thing,
and
this
is
probably
going
to
be
a
cross
collaboration
with
the
code
review
group
but
yeah.
B
A
I
was
thinking
a
lot
about
that
too,
and
other
people
on
the
call,
chad
and
matt
amy
might
not
understand,
and
I
might
not
have
seen
the
chatter
but
we're
working
on
defining
some
q3
okrs
and
one
of
them
I'm
trying
to
wrap
my
head
around
is
like
the
improving
the
usability
broadly
between
the
web
ide
and
the
mr
workflow,
and
I
think
this
falls
in
nicely
there.
Things
like
having
comments
show
up
in
the
web
ide.
You
know
discussions
from
the
mr
show
up
in
the
web.
A
D
Yeah
I'll,
just
just
on
that
note,
I've
I've.
A
D
Using
code
stream,
which
is
the
a
third-party
integration
for
jetbrains
ides,
and
I
think
they
have
others
just
because-
and
they
asked
me
for
feedback,
but
I
said
you
know
we
want
to
ideally
dog
food
everything
within
gitlab,
so
I
wouldn't
see
this
being
widely
used
within
git
lab,
but
it
is
probably
an
interesting
thing
to
look
at
to
see
how
they
do
it:
stream
code
stream
and
apparently
it's
free
now
for
individual
usage.
I
guess.
B
Cool
I'm
just
shaking
my
head
like
this,
because
the
first
screen
on
there
has
like
a
comment
box
next
to
two
files
which
looks
very
eerily
similar
to
one
of
my
exploration
of
like.
Oh,
you
can
do
comments
in
the
web
id
with
this.
It's
just
like
interesting.
Oh.
A
Thanks
for
pointing
that
out,
I
think
just
to
go
back
to
the
topic
of
feedback
from
the
fortino
release.
To
summarize-
and
we
talked
about
this
before-
but
to
summarize
the
the
feedback
on
the
top
nav
has
been
in
the
issue
relatively
critical,
though
minor
and
constructive.
So
I've
been
encouraged
by
the
types
of
feedback
we're
getting
and
considering.
The
volume
of
people
that
have
been
exposed
to
the
top
now
is
actually
a
very
small
number
of
people
who
are
pointing
out
things
that
aren't
working
for
their
workflow.
A
So
I
think
it's
been
great.
I
I'm
glad
to
hear
that
you're
already
talking
to
paul
on
some
of
the
changes.
I
also
would
like
to
highlight
that
some
of
the
feedback
is
summarized
as
like:
there's
a
lot
of
empty
space
and
left
now
in
the
top
nav
and
the
the
the
fact
is
like
this
was
an
iteration.
It
was
a
big
iteration.
It
was
a
big
change,
but
we
we
knew
that,
like
the
whole
top
nav
there's
a
vision
for
it
right,
we've
we've
kind
of
thought
about.
A
A
That's
not
the
spirit
of
our
our
way
of
working.
We
we
found
a
smaller
area
that
we
can
ship
right
away
and
we
shipped
it,
and
so
now
people
are
responding
to
the
fact
that
yeah
like
we
could
have
probably
done
a
more
holistic
overhaul
of
the
top
nav
and
shipped
it
in
14-5
or
15-0,
and
then
that
maybe
that
we
wouldn't
gotten
that
feedback,
but
we
wouldn't
have
received
this.
This
really
constructive
feedback.
A
You
know
at
this
early
point
so
very
happy
with
how
the
the
feedback's
going
and
similarly
for
the
content
editor
it's
very
validating
for
our
roadmap.
People
are
pointing
out
things
that
are
missing
in
the
content.
Editor
that
we
know
are
missing
that
we
know
we're
doing
next
and
that
we,
some
of
them
like
images
and
tables,
were
actually
already.
You
know
planned
for
14
1,
so
we're
on
the
right
track
there
and
shifting
gears
to
embedding
snippets
in
the
content
editor.
A
We
don't
need
to
do
a
huge
sync
on
this,
but
that
is
something
that
matthew's
gonna
be
helping
out
breaking
down
the
designs
into
mvcs
or
in
mvc
and
hopefully
getting
that
into
14-2
as
part
of
this
exercise,
so
anything
that
you've
started
to
explore.
I
know
I
I
gave
you
sort
of
an
artificial
deadline
at
the
end
of
this
week,
so
you
might
not
be
ready
to
to
share
or
anything
michael.
But
if
you,
if
you
have
anything,
you
want
to
chat
about,
feel
free.
B
Yeah,
nothing
to
really
share
at
this
moment.
I
think
everything
is
similarly
connected,
lovely
for
me
this
week.
So
with
the
world
of
snippets,
there
was
a
a
issue
that
was
brought
up
about
and
not
looking
right
on
mobile,
and
I
discovered
that,
like
our
snippets
behave
differently
on
github.com
versus
like
an
external
site,
I
have
no
idea
what's
going
on
there.
I
don't
know
if
one's
an
older
version
or
one's
a
newer
version,
but
you
know
this
different
behaviors,
but
then
that
that
kind
of
got
me
in
the
mindset
of
snippets.
B
I
feel
like
there's
going
to
be
a
flow
that
uses
contextual
menus
to
look
up
a
snippet
snippet
that
you
want
to
add.
So
that's
something
now,
I'm
going
to
dive
deeper
with
enrique
tomorrow's,
so
yeah,
tomorrow's
going
to
be
a
fun
busy
day,
but
yeah.
So
far
this
week
was
more
focused
on
the
navigation,
stuff
and
yeah,
just
figuring
out
how
snippets
and
embedding
them
works,
but
yeah
it's
it's
confusing.
Why
they're
different,
but
yeah.
D
A
I've
also
taken
this
opportunity
to
learn
a
little
more
about
snippets.
We
have
snippets,
has
been
somewhat
on
the
back
burner
since
we
took
over
all
the
categories
in
the
editor
group,
and
I
haven't
looked
super
closely
at
the
process
for
embedding
them
in
external
sites.
So
just
writing
the
issue.
For
example,
I
learned
a
little
bit,
but
I
had
not
come
across
this
mobile
interface,
which
is
not
ideal,
so
this
is
great.
A
I
will
leave
it
there.
It
sounds
like
you're.
Gonna
have
a
great
conversation
with
enrique
on
this.
If
you
want
to,
you
could
add
me
and
matthew
is
optional.
I,
depending
on
what
time
it
is
we
may
or
may
not
join,
but
it
might
be
interesting
to
listen
in
or
just
record
it
and
share
afterwards.
That
would
be
fine
too.
I
will
be
sure
to
watch
it
if
I
can't
join.
A
I
will
transition
over
to
docs,
specifically
because
I
was
having
a
one-on-one
with
matthew
yesterday
and
he
asked
a
question
like
about
stable
counterparts
and
like,
what's
the
what's,
the
relationship
with
tech
writing
like,
and
I
said
well,
not,
everybody
is
as
good
as
amy,
but
she's
very
proactive
and
we've
had
a
great
relationship
working
with
tech
writing.
I
previously
we
were
one
of
many,
like
groups
assigned
to
a
tech
writer,
and
we
have
been
getting
a
lot
of
your
wonderful
attention.
A
C
B
A
C
A
Rallying
around
on
the
changes
so
yeah,
I
don't
want
to
imply
that
it
was
a
singular
effort.
It
was
not
the.
A
Rallied
behind
the
global
changes
to
the
docs
that
were
necessary
and
yeah
to
keep
them
in
sync
and
get
everything
launched.
A
You
know
right
when
it
needed
to
be
was
just
really
satisfying,
and
it
shows
that
when
you
have
a
chance
to
involve
your
stable
counterparts
early
in
the
process
identify
those
things.
I
also
highlighted
that
in
the
process
of
reviewing
the
docs,
we
learned
about
some
areas
that
we
maybe
hadn't
considered
like
in
the
admin
section,
or
you
know
the
like
edge
cases
that
we
maybe
needed
to
account
for
in
in
the
design.
C
Matthew
what
you
will
see
when
working
with
me
is
that
I
am
probably
the
nosiest
and
most
forward
of
the
tech
writers
in
our
our
current
team,
because
that's
just
how
I
roll,
I
don't
know
what
I'm
gonna
catch
until
I
catch
it,
and
this
this
one
was
a
particularly
big
one
if
it
works
better
to
talk
with
david,
to
get
an
idea
of
how
I
work
with
teams
david,
and
I
have
worked
on
a
previous
team
before
so.
It's
very
much
a
case
of
oh
you
again
cool
but
yeah.
C
E
A
All
right,
I
think,
with
that,
we're
at
the
end
of
the
agenda.
We
have
two
minutes
before
we
have
to
jump
to
the
backlog
refinement
session,
but
any
any
parting
words
I'll.
Take
that
as
a
now
all
right
thanks
everyone
for
joining,
and
we
will
I'll
see
a
couple
of
you
in
two
minutes.
I.