►
From YouTube: Create:Editor Product/UX Weekly - 2021-04-21
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
and
I'll.
Kick
it
off
with
just
a
few
sort
of
request,
slash
fyis,
mostly
for
michael.
The
first
was
during
the
issue
refinement
session.
This
morning
we
were
going
over
sort
of
the
three
main
priorities:
top
nav
left
nav
and
the
content
editor
mvc
when
it
comes
to
the
left,
nav
dennis
had
a
specific
request
to
just
make
sure
that
we
have
documented
the
absolute
final
scope
for
14-0
and
not
anything
forward-looking.
A
A
A
But
if
we
could
just
document
that
in
the
epic,
then
he
will
have
a
single
source
of
truth
for
it.
B
Yeah
I
was
gonna,
ask
which
issue
or
epic
do
you
want
that
in
but
yeah
I'll
do
that
at
the
epic
level,
yeah.
A
B
A
And
I
think,
similarly
documenting
the
final
proposed
architecture
that
we
want
to
see
in
14-0,
so
an
ideal
state
for
all
the
different
moves
of
categories
and
breaking
up
operations
and
renaming
such
and
such
and
all
those
issues
that
are
in
there
now
probably
be
easier.
If
we
just
had
one
place
to
look
and
say
this
is
what
it
should
look
like
at
the
end,
and
then
we
can
work
backwards
and
making
sure
all
those
issues
get
closed
out.
And
I.
C
A
C
Oh
yeah,
no,
no
worries!
It's
just
that
reading
the
agenda
brought
the
question
up
to
me
of
so
like
what
realistically
could
actually
change
beyond
what
we've
kind
of
already
explored
like,
for
example,
the
ideas
around
spreading
settings
and
analytics
everywhere
like
is
that
even
feasible
for
14.00?
Because
if
it's
not,
then
we
can
like
take
it
off
of
our
brain
space
for
the
the
near
term.
So
if
you.
A
Yeah,
that's
a
great
great
question.
I
will
say
that
the
the
one
thing
that
sounds
like
it's
coming
from
this
is
that
settings
is
an
entirely
different
beast
and
creating
new
settings.
A
Views
would
increase
the
scope
to
the
point
where
we're
risking
fortino
our
ability
to
deliver
14
now
so
michael
as
much
as
I
want
to
ship
that
one
where
we're
breaking
out
merge
requests
into
its
own
top
level
friend
implied,
although
he
was
on,
he
had
a
bad
connection,
couldn't
stay
for
the
whole
meeting,
but
he's
made
it
clear
in
an
issue
async
and
during
the
meeting
that
that
is
more
complex
than
we
might
have
time
for
for
14
hours.
A
So
I
think
it
follows
that
in
order
to
get
the
right
mapping
for
all
those
settings
views
we
would
need
to
break
it
break
some
of
them
out
and
that
would
probably
be
out
of
scope
for
14..
Oh,
I
don't
know
the
complexity
for
analytics.
I
know,
but
I
feel
like
that
still
needs
to
be
validated
by
the
analytics
group.
I
don't
really
have.
A
The
the
gist
of
what
I
heard
is
if
we
were
able
to
deliver
this
refactor
that
fran's
working
on,
which
is
still
an
if
he's
working
as
fast.
He
can
given
the
other
priorities
with
the
database
optimization,
but
if
we
can
deliver
that
refactor,
it's
fairly,
I
don't
wanna.
I
don't
wanna
use
the
word
easy.
It's
fairly,
inexpensive
to
rename
left
nav
items
and
regroup
them
and
move
them
around.
It's
not
as
easy
to
create
new
settings
views
and
create
entirely
new
routes
for
pages
to
land.
So
I
think
that's
kind
of
our
barometer.
C
Thank
you
yeah,
just
because
of
all
the
different
types
of
things
that
were
floating
around,
like
maybe
having
tabs
on
pages
and
maybe
doing
life
cycle
buckets.
I
just
wanted
to
see
if
those
would
be
even
just
too
big
for
14.00,
then
whatever
uncertainties
or
things
that
maybe
michael
knows
up,
we
could
focus
on
that
in
terms
of
research
and
getting
anything
past.
The
line
for
14.00.
B
A
Yes,
I
will
drop
it
in
the
link
here,
all
right.
It's
just
just
had
my
email
open,
so
here's
the
comment
and
I'll
just
read
it.
So
it's
documented
on
the
call
too
so
fran
said
the
the
work
we
need
to
do
here
is
not
small
here,
meaning
moving
the
merge
request
from
general
to
its
own
settings
view
and
making
it
so
they
don't
collapse
anymore.
So
we
need
to
split
the
view
component
in
order
to
extract
the
settings
options.
A
We
need
then
add
the
sidebar
entry
create
a
controller
with
a
route
and
action
for
this
new
setting
and
then
create
a
specific
view
component
and
do
all
that
behind
a
feature
flag.
So
there's
a
fair
bit
of
work
to
to
make
that
smallish
change,
but
I
think
it's
gonna
have
to
be
like
a
a
wait
and
see
because
we
don't
know
how
much
progress
in
1312
he's
going
to
be
able
to
make
on
the
refactor.
A
Although
it
is
nice
that
atar
is
going
to
be
able
to
jump
in
and
help
build
out,
the
group
re
group
sidebar
refactor,
so
at
the
group
level,
the
left
now
so
hopefully
we'll
be
able
to
you,
know,
work
in
parallel
there
and
get
it
done
a
little
faster.
A
The
last
note
I
had
today
towards
the
end
of
the
day
I
finally
got
around
to
doing
something.
I've
been
wanting
to
do
for
weeks,
which
was
build
out
a
bunch
of
issues
for
implementing
different
content
types
for
the
content.
Editor
so
background
here
is
that
tip
tap
and
prose
mirror
have
bass
support
for
common
mark.
In
order
to
get
to
the
point
where
we
have
the
ability
to
render
and
edit
every
type
of
content
available
in
get
lab,
flavored
markdown
we're
going
to
need
to
create
extensions
for
every
node
type.
A
So,
in
order
to
organize
this
and
prioritize
this,
we
talked
about
creating
issues
for
sort
of
issue
pairs
for
every
node
type.
Some
of
this
is
already
done
because
of
the
base
level
common
mark
support.
A
So
we
saw
a
demo
today
with
enrique
showing
kind
of
the
the
current
status
of
the
content
editor
in
the
wiki,
and
it
has
things
like
bold
and
list
items
and
stuff
like
that
already
built
in,
but
I'm
going
to
create
just
like
a
boatload
of
issues
and
those
will
all
require
at
least
a
little
bit
of
input
from
design.
So
I
just
wanted
to
give
you
a
heads
up
that
I'll,
probably
just
per
our
last
meeting,
make
sure
that
they
all
start
in
workflow
design.
A
You
have
a
chance
to
look
at
them,
provide
guidance
on
which
icon
we
should
use
or
create
an
icon.
If
we
don't
have
one
and
if
there's
any
custom
ui
for
something
like
creating
links,
you
have
a
chance
to
weigh
in
on
how
that
should
be
presented,
etc.
So
you'll
probably
get
pinged
on
a
whole
bunch
of
issues.
Hopefully
a
lot
of
them
are
just
like
use.
This
bold
icon
that
we're
using
already
and
we're
done,
but
just
to
make
sure
you're
in
the
loop
I
figured
putting
them
in
workflow
design
would
be
good.
A
Cool
cool,
so
that's
it
for
my
agenda.
B
Cool
this
week
is
probably
pretty
quick
for
me,
so
yeah
over
the
next
week,
or
so
just
ensuring
that
the
issues
are
up
to
date
for
14.00
and
anything
further,
I'm
trying
to
make
sure
that
issues
are
up
to
date.
At
the
same
time,
it's
like
getting
my
own
head
up
to
date
by
like
cleaning
up
to-do's
and
stuff.
B
So
that's
why
you
probably
see
me
messaging
you
eric
on
like
four
four-month-old
issues,
that's
just
because
I'm
finally
like
trying
to
get
it
on
top
and
just
being
more
deliberate
with
my
actions
on
a
side
note,
I
got
access
to
side
sense,
finally
to
create
reports.
This
is
probably
why
I
was
struggling
in
the
past
because
I
was
like
I
couldn't,
do
anything
or
see
the
queries,
so
I've
done
a
lot
of
sites
and
some
periscope
work
in
the
past.
B
So
I
could
help
out
with
creation
of
dashboards
and
stuff
like
that.
If.
B
Are
in
there
right
now,
then
yeah.
If
there's
any
issues
in
the
past
that
you
haven't
got
a
chance
to
tackle,
feel
free
to
like
ping
me
on
them,
and
I
can
take
a
look
at
trying
to
do
stuff
there
and
yeah
I'll
just
segue
into
my
ux
research
comment.
Yeah.
D
B
Debrief
last
week
was
really
good.
I'm
gonna
take
some
of
that.
Some
of
the
conversations
there
and
then
refine
that
into
like
another
video
and
then
share
the
findings
and
this
week
for
greater
audience.
A
A
Just
to
hear
you
talk
about,
it
was
really
helpful
and
it
was
a
great
way
to
see
the
thought
process
of
like
this
is
how
we
structured
the
the
research.
This
is
what
we
noticed,
and
this
is
sort
of
my
action
items
that
I'm
proposing
and
all
that
does
get
documented
issues,
but
just
hearing
you
talk
about
it,
it's
it's
easier
to
digest
and
consolidate.
So
I'm
a
big
fan
of
keeping
this
moving
forward.
B
And
yep
cool
we'll
do
that
and
yeah
the
goal
of
this
versus
the
more
polished
one
is
like.
Sometimes
you
know
you
just
want
to
like
rubber
duck
and
just
talk
about
things
and,
like
maybe
the
angle
you're
coming
at
or
you're,
oblivious
to
it
or
you're
like
trying
to
push
your
own
agenda
so
yeah.
It's
just
a
chance
for
the
group
to
chime
in
and
kind
of
help
out
shape
that
message.
So
yeah
yeah.
A
Appreciate
it,
and
also
I'm
glad
to
hear
that
you've
done
some
periscope
and
science
work
before
I'll,
probably
take
you
up
on
I'm
trying
to
get
better
at
sql
in
general,
but
also
navigating
around
size
sense,
which
is
a
whole
other
thing
I
know
chad
has
offered
before
so
now.
I
have
basically
two
people
who
have
offered
that
I
need
to.
I
can
weigh
who,
whose
time
I
want
to
steal
and.
A
E
D
D
So
that
seems
like
a
good
place
to
start
okay
yeah.
When
I
I
cut
myself
off
before
I
went
too
deep,
but
I
had
started
like
a
document
of
everything.
When
I
tried
to
look
into
this
before
and
I
found
you
know,
five
different
people
telling
me
four
different
things
of
six
different
places
to
find
stuff
and
different
ways
to
get
metrics
so.
C
B
Yeah
well,
no,
no
problem,
one
of
the
things
that
will
probably
come
up
your
way
next
week
is
actually
perfect
because
it
gives
me
some
time
to
like
think
about
it.
This
week
is
the
bigger
left,
nav
initiatives,
as
kind
of
like
the
bigger
interaction
patterns,
and
things
like
that.
So
you
know
so.
This
is
not
slated
for
14.00.
This
is
probably
more
for
like
future
direction
of
like
where
the
left
nav
could
be
heading
so
yeah.
Well,
we'll
set
up
a
separate
call
for
that
one
next
week,
but
yeah.
A
I
should
probably
go
back
and
highlight
that
enrique
did
demo
a
working
version.
Him
and
hamachu
have
been
working
on
the
content
editor
in
the
wiki
view
and
there's
an
mr
out
there.
I
know
michael
you've
seen
it
because
you
provided
great
feedback
on
the
experience
around
switching
between
the
current
slash
old
markdown
editor
and
the
new
content
editor,
but
the
the
demo
was
exciting,
so
we're
getting
there.
It's
almost
usable
there's
light
at
the
end
of
the
tunnel,
and
it's
it's
looking
really
cool.
A
I
think
it's.
I
think
he
I
mean
we
should
be
pretty
close
to
being
able
to.
You
know,
put
it
somewhere
that
we
can
start
playing
around
with
it
and
and
demoing.
It
I'll
caveat
that
by
saying
that
today,
tip
tap
opened
up
public
beta
for
their
2.0
version
and
so
enrique's
doing
a
little
bit
of
a
research
spike
to
see
what
it
would
take
to
do
the
upgrade.
A
D
B
A
design
perspective
like
I'm,
pretty
excited
about
the
styling
changes
and
then
yeah.
I
think
the
2.0
kind
of
might
address
the
better
block,
editing
experience.
So
one
of
the
things
that
I've
ran
into
when
creating
the
prototype
for
the
user
testing
was.
Oh,
you
know
how,
like
other
platforms,
have
like
a
plus
sign
or
like
some
kind
of
visual
cue
to
say
like
if
you
click
on
this,
then
you
can
add
the
floating
menu
in.
So
perhaps
that
kind
of
addresses
that
and
opens
the
door
for
different
interactions
of.
A
Yeah
same,
I
think
I
think
it's
a
it's
going
to
be
a
big
upgrade
and
if
we
can
just
come
out
the
gates
with
it,
I
think
it's
it's
going
to
be
better
long
term.
Hopefully
it's
stable
enough
and
and
ready
for
our
usage.
A
I
did
have
a
question,
and
I
just
kind
of
learned
this:
through
an
email
I
traded
with
the
tip
top
team,
it
seems
like
their
relationship
to
y.js
is
actually
a
lot
closer
than
I
thought,
which
is
why
they're
using
it
as
the
sort
of
back
end
for
their
collaborative
editing
component,
and
I
was
wondering
chad
if
you
could
maybe
on
a
different
call
or
just
like
help
me
understand
how
why
dot
js
fits
into
the
puzzle,
and
I
understand
we
can't.
A
We
likely
can't
use
it
because
it's
a
node
service,
but
like
what.
D
Build
so
yeah,
that's
a
very
deep
question
and
one
that
I've
been
pushing
whenever
people
mention
collaborative
editing
and
the
the
important
thing
to
know
is
you're
not
just
gonna
get
collaborative
editing
to
collaborative
editing
just
by
using
a
client
library
and
by
true
collaborative
editing.
I
mean,
like
multiple
people,
editing
the
same
document
at
a
time
or
multiple
people,
concurrently
reordering
items
on
a
list
like
issues
in
the
board.
D
D
And
the
the
way
to
do
that
is
hold
on
a
second
okay,
sorry,
multiple
people
sharing
the
office.
So
the
issue
is
on
the
back
end.
You
need
to
have
the
right
architecture
to
support
that
which
is
something
to
handle
those
concurrent
things:
it's
either
an
event,
sourcing
architecture
or
a
timestamp
type
architecture,
and
if
you
look
at
the
tip,
tap
dots
and
I've
linked
to
it
a
couple
of
places
you
can
see
where
they
discuss
that
you
have
to
have
a
back-end
to
support
that
a
just
a
regular,
relational
database.
D
You
know
standard
out-of-the-box,
drills
paradigm
is
not
going
to
give
it
to
you
and
just
having
pub
sub
with
you
know:
action,
cable
or
sockets,
pushing
out
your
changes.
That's
not
it!
You!
You
have
to
have
commands
that
are
coming
in
concurrently,
ordered
emitting
events.
The
clients
are
listening
to
those
events.
They
have
optimistic,
concurrency,
rolling
back
their
changes
if
they
didn't
get
their
change
in
it's
a
lot
of
architectural
concerns
on
the
back
end.
D
A
D
Know
bartek
marnein
is
who's
now
in
charge
of
staffing.
These
single
and
engineer
groups
like
around
observability
and
you
know
collaborative
editing,
here's
one
who
originally
hired
me.
So
I
know
him
and
I've
been
like
making
sure
he's
aware
of
these
things
like
as
much
as
I
can
concerns
that
we
need
to
hire
the
right
people,
and
these
are
deep
problems
that
you
need
to
approach
the
right
way.
A
B
For
breaking
that
down
chad,
it
was
very
clear
and
like
not
too
technical,
so
it's
like
I
understand
cool.
My
question
is
from
a
problem.
Validation
standpoint.
Have
we
done
anything
in
the
spirit
of
like
collaborative
editing,
kind
of
seeing
what
that
might
look
like
for
git
lab
or
like
what
kind
of
problem
it's
trying
to
solve
from
a
research
standpoint
or
a
product
standpoint,
eric
or
catherine.
A
I
haven't
seen
any
formal
opportunity,
canvases
or
any
like
true
business
case
other
than
we
feel
strongly,
that
there
is
desire
a
customer
desire,
and
so
it's
on
my
plate
to
put
together
some
proper
research
from
that
standpoint
from
the
problem,
validation,
standpoint
and
obviously
I'd
work
with
you
and
catherine
to
try
and
get
the
data.
I
need
to
make.
That
decision
is
definitely
something
we
are
investigating
on
a
more
of
a
like
a
gut
understanding
of
the
market,
rather
than
a
proper
like
work
stream.
A
Okay,
well,
I
think
that's
enough
of
hypotheticals
for
that,
and
I
will
I'll
continue
to
ask
dumb
questions
about
collaborative
editing,
as
I
gather
this
information
and
try
and
figure
out
whether
it's
something
we
can
or
want
to
do.
But
that's
helpful.
D
So
I
can
jump
in
about
the
top
nav
a
little
bit
yeah,
so
the
first
of
all.
We,
we
had
a
really
good
discussion
with
fran
after
the
backlog,
refinement
and
we're
in
a
much
better
place
and
an
agreement
upon
a
shared
architecture.
He
took
a
lot
of
our
suggestions
and
we're
gonna
change
our
like
some
of
our
naming
and
terminology
to
be
more
consistent
with
what
he's
doing,
and
so
that
landed
in
a
really
good
place.
As
far.
D
Stuff
usable
we
so
in
the
non-responsive
view,
it's
it
mostly
works,
there's
some
styling
and
stuff
the
responsive
view
like
we
have
the
basics
and
we're
still
getting
the
like.
The
the
recent
or
more
frequently
used
projects
or
whatever
stuff
added.
D
But
I
talked
to
paul
and
I'd
like
to
shoot
by,
hopefully
the
end
of
this
week
or
the
beginning
of
next
week
that
we
have
something
close
to
ready
to
merge
behind
a
user
specific
feature
flag
that
we
can
turn
it
on
and
and
start
playing
with
it,
even
if
it's
not
complete-
and
I
think
the
main
blocker
for
that
is
me
like
cleaning
up
the
tests
for
the
enable
feature
flag
and
just
before
this
meeting
I
finally
got
the
latest
epic
spam,
mr
green
and
ready
for
review.
D
A
Yeah,
if
you
can
target
our
group
and
then
we'll
see
if
it
works,
and
we
can
target
a
wider
group
or
all
of
gitlab
or
something
like
that
in
the
following
weeks
and
get
some
good
feedback.
I
think
that's.
A
A
Cool
well,
we
are
through
the
agenda.
I
don't
have
anything
else
so
I'll.
A
Yeah
wrap
up
the
meeting
a
few
minutes
earlier,
unless
anybody
else
has
anything
else
to
bring
up.
Oh
and
chad,
my
gdk
just
successfully
built
and
is
running.
So
thank
you
for
unblocking
me.
There.
D
A
Yeah,
that's
great,
I'm
looking
forward
to
to
that
and
now
I
can
install
it
locally.
So
yeah
awesome,
okay!
Well,
everyone
have
a
great
rest
of
your
day
and
I
will
talk
to
you
soon.
See
you,
on
slack
and
in
the
on
the
internet,
see
ya
bye.
Everyone.