►
From YouTube: Create:Editor- August 2021 Monthly Meeting
Description
In this video, we'll talk about the longer vision for the Editor teams work and what we'll tackle in the next few milestones.
A
B
A
D
A
But
like
if
you
look
at
that,
photo
there,
so
this
is
the
prediction
for
2040.,
so
all
of
the
red
areas
are
supposedly
going
to
be
underwater
and
we're
talking
like
a
couple
of
feet
of
water
as
well,
and
so
my
parents
house
is
just
smackdown
in
the
middle
there
in
rahini,
but
like
bald
oil
port
marnick.
That's
where
I
used
to
go
to
school.
All
of
this
place,
apparently
just
completely
underwater.
E
D
D
D
A
D
A
Yeah
sure,
and
so
from
my
perspective,
so
the
say:
do:
ratio
70
throughout
the
month
of
july,
which
is
really
good.
Our
general
ballpark
for
our
okr
and
create
is
between
70
and
80.
So
we're
we're
managing
to
do
the
things
we
say
we're
going
to
do
without
over
committing,
which
is
the
sweet
spot
to
be
in
narrow.
Mr
rate
is
9.125
or
9.
A
E
A
D
Okay,
well,
I
always
say
that
I'm
gonna
go
quick
and
then
I
talk
for
hour
and
a
half
on
everything
in
my
agenda,
but
I
don't
actually
want
to
spend
a
ton
of
time
I'd
like
to
leave
it
open
for
q,
a
and
discussion,
but
the
strategic
product
updates
section
I
did
want
to
share
if
you
didn't
see
it
which
you
might
not
have,
because
I
didn't
post
it
in
our
room.
We
have
a
new
group
direction
page,
and
this
is
not
something
we've
had
before.
D
We
had
all
our
category
direction
pages,
but
as
an
experiment
within
the
dev
section
pms
that
we
were
talking
about
whether
or
not
this
would
be
valuable
and
what
form
it
should
take
and
group
direction
pages
for
a
lot
of
teams
is
potentially
repetitive
information
with
their
category
directions
and
they're
trying
to
talk
about
how
to
automate
it.
But
I
volunteered
us
because
I
thought
a
group
direction
page
would
be
actually
very
beneficial
to
us.
D
A
lot
of
this
information
I
had
in
our
hq
epic,
which
is
like
what
we're
working
on
and
why
I
thought
it'd
be
great
to
surface
this
in
a
sort
of
executive
summary
form
about
these
are
the
categories
we
own.
This
is
where
they're
at
links
to
their
direction
pages
and
just
like
one
or
two
sentences
about
what
we're
working
on
and
why,
where
we're
spending
our
time
and
and
then
links
to
it's
a
landing
page
of
sorts
for
for
how
to
get
around
relevant
direction
information.
D
I'm
hopeful
that
this
will
have
two
two
outcomes:
one.
It
will
make
it
much
more
clear
for
anybody
asking
what's
the
editor
group
working
on
and
why
right
like
sales,
execs
anybody
who
isn't
in
the
weeds
with
our
group
might
say
what's
going
on
with
snippets,
why
isn't
there
much
traction
there
like,
or
I
haven't
seen
a
new
snippets
feature
in
a
while?
D
It
also
afterwards,
I
realized
in
talking
with
david,
could
help
us
with
discussions
around
hiring
and
growing
the
team.
So
as
we
show
the
categories
that
we
own,
which
ones
we're
not
working
on,
we
might
be
able
to
make
a
case
for
hey.
You
want
some
improvements
to
snippets.
Well,
we're
either
taking
time
away
from
this
or
we're
getting
more
people.
So
hopefully
it
makes
these
kinds
of
conversations
easier,
and
I
will
do
my
best
to
keep
it
up
to
date.
D
The
next
step
is
to
go
through
and
update
our
individual
category
direction
pages,
which
has
been
on
my
plate,
for
I
don't
know
four
months,
and
I
need
to
go
back
and
do
that.
I
also
created
direction
pages
for
the
source,
editor
and
content
editor
that
are
mostly
placeholder
now
and
I
need
to
flesh
those
out.
So
I
have
a
lot
of
writing
in
my
future,
but
this
is
the
beginning
of
it,
and
hopefully
it's
helpful
to
everybody
keep
an
eye
on
there.
D
It
shouldn't
be
a
surprise.
The
information
either
hopefully
like
you-
knew
what
we
were
working
on
already
and
you
knew
that
we
weren't
putting
much
time
into
some
of
these
categories.
The
biggest
change
here.
This
was
also
a
way
to
communicate
the
shift
in
our
focus
away
from
navigation
and
settings.
So
I
can
put
it
in
on
paper
and
say,
like
look,
you
know
we're
returning
our
focus
to
our
other
categories
and
yeah
that
that
was
another
strategic
timing
related
thing
with
why
I
wanted
to
write
this
page.
E
I
know
you
kept
saying
it
I
was
like.
Maybe
I
should
take
a
look
at
it
and
then
I
saw
it
and
you
already
moved
on
I'm
joking,
I'm
sorry,
but
can
you
dive
into
like
how
one
may
interpret
these
percentages
on
the
page?
It
says
like
what
you're
working
on
and
why
and
one
question
it
comes
up
to
is
like
there's
no
time
value
to
those
percentages.
E
D
Yeah,
that
is
a
good
question
and
it
is
not
an
exact
science
and
I
certainly
I
actually
loathe
the
breaking
up
of
individual
people's
times
and
saying,
like
you're,
going
to
spend
40
percent
of
your
time
on
this
and
60
of
your
time
on
that.
This
is
more
as
like
in
capacity
planning
road
mapping
and
it
is
fuzzy
and
they're
approximate
so
like
as
I'm
thinking
about
what
work
goes
into
a
milestone.
D
I'm
saying
like
maybe
we
can
fit
one
snippets
issue
or
like
one
bug
related
to
snippets
in
maybe
we
can
put
two
or
three
people
in
content
editor.
Maybe
we
can
put
most
of
our
time
into
web
id
and
source
editor
this
month
and
then,
like?
Maybe
maybe
one
milestone,
excuse
heavier
towards
settings
now,
because
we
find
a
bug
or
there's
like
one
thing
we
want
to
fix,
but
these
are
approximations
of
how
we're
planning
milestones
and
not
necessarily
like
you
know.
D
E
D
I
I
like
that
and
it's
possible
well.
First
of
all,
it
was
very
stressful
for
me
to
try
and
make
these
add
up
to
100
like
making
sure
that
I
didn't
say
we're
working
on
120
of
our
time
or
you
know-
and
there
are
ranges
on
here,
so
there
is
flexibility.
I
like
that
approach,
I'll
I'll,
think
about
breaking
it
out
into
like
top
tier
focus
like
secondary
focus
and
like
back
burner.
D
I
did
I
just
hesitated
to
say
I
hesitate
on
the
category
pages,
and
I
hesitate
on
here
saying
like
we
are
specifically
not
focusing
on
this
live
preview
is
the
only
one
that
has
an
absolute
zero.
I
guess
static
site
editor
does
too,
but
in
a
way
because
of
content
editor,
we
are
working
on
something
that
could
benefit
that,
depending
on
where
we
head
with
it.
So
I
I'll
think
about
that.
It's
good
feedback.
E
B
B
And
these
percentages
also
reflect
where
he
and
michael
and
the
rest
of
the
the
product
team
devote
their
effort
in
deciding
what
we
want
to
do,
which
comes
from
from
them
based
on
customer
demand.
But
it's
not
like
all
external.
But
to
answer
your
question,
it's
like
once
they
decide
what
we're
going
to
do
and
it's
pretty
well
set
up.
Then
then
the
team
waits,
but
as
far
as
the
the
focus
that's
sort
of
outside
and
above
the
the
specific
day-to-day
planning
and
waiting.
B
D
D
E
Well,
just
to
clarify,
I
think
it's
really
cool.
I
think
it's
cool
that
it
all
adds
up
to
100,
because
I
know
that
that
constraint
is
hard,
but
those
constraints
help
us
make
make
decisions,
because
you
have
to
prioritize-
and
I
think
I
think
I
really
like
the
intention.
What
what's
behind
here
is
really
good
thanks.
D
D
Yeah
well
and
ultimately,
the
percentages
raw
numbers
are
easier
to
parse
for
for
certain
stakeholders
and
just
like
glance
at
and
so
there's
also
the
risk,
and
I
fall
in
this
trap.
All
the
time
like
when
you
have
more
than
one
top
priority
right,
it
starts
to
get
fuzzy
also.
So
when
you
have
three
things
that
are
your
top
priority,
it's
not
really
your
top
priority
so
anyway
I'll
keep
that
feedback
in
mind.
D
This
is
a
sort
of
pilot
there's
another
group
working
on
a
group
direction
page
and
then
there's
other
groups
outside
of
dev
that
have
already
started,
like
naturally
started
working
this
way
and
use
only
a
group
direction
page.
I
don't
think
we're
going
to
get
away
with
that
yet,
but
this
is
a
work
in
progress.
Feedback
is
welcome
and
I'll.
Keep
that
in
mind.
B
So
just
the
final
note
on
your
question,
paul
like
if
you
look
on
the
the
product
development
workflow
page
that
I
sent
the
gitlab
uses,
the
the
validation
track
is
sort
of
what
we
were
talking
about.
That's
all
in
eric
and
the
designers
like.
What
are
we
going
to
do
and
how
do
we
validate
that
and
get
it
very
clearly
defined,
and
then
the
build
track
would
be
more
of
the
the
xp
where
the
team
comes
in
and
says:
okay,
what's
the
weight
of
this
and
how
we
can
execute
on
it.
B
D
Now,
specifically
on
the
web
id
and
source
editor,
I
we
haven't
come
together
as
a
group
to
talk
about
the
the
shift
towards
sas
reliability,
but
we've
talked
about
it,
a
bunch
async
and
I
really
appreciate
all
your
input
in
those
epics
and
I
was
gonna
link
them.
But
then
I
started
talking
so
they're
they're
in
the
web,
ide
and
wiki
category
strategy,
epics
for
improving
reliability
and
over
the
course
of
this
quarter.
D
It
seems
pretty
clear
that
we
have
some
work
that
we
should
do
and
can
do
to
improve
reliability
of
our
categories.
It
sounds
like
right
now
we're
rallying
around
two
main
things
for
the
web:
ide,
the
state
refactor,
which
is
long
overdue,
and
I'm
very
excited
that
we're
getting
a
chance
to
do
it
and
potentially
moving
to
graphql
for
for
the
requests
and
improving
performance
and
reliability.
D
There
I'm
going
to
leave
sequencing
those
up
to
the
experts-
and
my
only
ask
is
that
we
take
the
next
couple
weeks
to
refine
the
epics
and
make
sure
the
issues
are
weighted
and
have
a
sense
of
a
plan,
but
other
than
that.
I'm
very
excited
about
the
work
there.
That's
what
we'll
be
doing
for
the
next?
D
That
stuff
is
still
of
high
interest
and
then
maybe
a
little
longer
term.
We
need
to
validate
this
a
little
more
and
work
on
design,
but
I
think
it's,
it's
probably
really
good
to
bring
in
the
mr
discussions
into
the
web
ide.
That's
probably
more
of
like
a
first
part
of
next
year.
Focus
or
something
so
we
don't
need
to
rush
on
that.
We
need
some
design
and
validation
work,
but
I
think
that'll
be
our
next
big
thing.
D
F
It's
in
review
for
just
to
set
the
the
explanation
bar
correctly
here.
The
merge
request
currently
in
the
review
is
for
live
preview
for
the
blobs.
I
have
the
I
have
the
the
patch
from
to
make
it
work
in
web
id
and
maybe
after
the
first
round
of
review.
Maybe
I
will
just
push
that
to
to
the
same
merge
request
and
then
I
will
have
the
live
preview
in
web
id
as
well.
F
F
I
was
I
was,
I
was
considering
route
routing
this
from
through
pros
mirror
through
through
the
great
work
that
enrique
and
himanshu
work
on
to
do
this
on
the
on
the
to
this
cloud
client
side.
But
the
the
problem
is
that
that
would
take
time,
and
this
would
not
generate
the
exact
preview
that
users
will
get
afterwards
when
they
save
the
page
anyway.
So
that's
why
I
decided
to
take
the
s
baby
steps,
and
now
we
are
just
fetching
the
preview
from
the
server
to
make.
That's.
D
Consistent
that
sounds
like
the
right
call
and
a
good
iteration,
but
I
think
we
should
continue
that
conversation
about
how
we
can
and
just
make
that
round
trip
even
more
efficient
and
use
the
work
that
we're
doing
on
the
content.
Editor.
I
think
that's
great
the
other
thing
in
relation
to
the
mr
discussions
and
stuff.
I
think
we'd
want
to
focus
on
source
editor
and
building
and
maturing
the
extension
so
that
things
like
merge
requests.
D
D
I
know
I
said
this
like
probably
a
month
ago,
but
we'll
set
up
a
think
big
session
for
for
the
web
ide
soon,
maybe
after
our
team
building
meeting
and
and
dennis
when
you're
back
from
pts,
so
that
you
can
join
so
we'll
get
it
on
the
calendar
and
and
find
a
time,
that's
right
for
everybody.
But
I'd
really
like
to
just
get
all
these
ideas
out.
There
too,
I
was
being
a
little
flippant
with
the
content.
D
Editor
there's
there's
some
aspects
of
gitlab
flavor
markdown
that
we
can't
parse
that
just
need
custom
renders
and
we're
trying
to
get
it
all
done
in
the
next
couple
miles
done
so
I
created
an
epic
yesterday
and
we're
trying
to
to
really
figure
out
what's
essential,
and
this
is
the
I
finally
found
it.
So
I'm
going
to
put
it
here.
This
is
the
epic
that
we'll
kind
of
use
to
track
rendering
of
gitlab
flavored
markdown.
There's
I'm
very
excited
by
what
I
saw
at
the
end
of
the
day.
D
Yesterday
is
enrique
posted
a
comment
to
me
in
an
issue
where
he
created
a
tutorial
for
rendering
for
creating
an
extension
to
render
emojis
and
I'm
excited
to
follow
through
it
and
see.
If
I
can
even
pick
off
like
the
easiest
thing
on
this
list
and
and
try
and
help
out,
but
don't
get
your
hopes
up,
I'm
probably
not
going
to
be
able
to
do
it.
B
G
D
It
so
I
I
would
love
some
input
on
this
issue.
This
epic
in
particular.
This
is
also
an
interesting
one,
because
I'm
going
to
try
out
our
automation
with
our
new
okr
tracking
tool
and
which
requires
a
checklist
in
the
epic
description.
It's
very
like
specific
how
we
have
to
set
it
up,
but
I'm
trying
to
create
a
checklist.
That's
almost
an
iteration
plan
to
get
to
the
point
where
we
can
make
the
content
editor
the
default
markdown
editor
for
a
small
portion
of
the
population.
D
We
don't
need
to
make
it
for
everybody,
but
maybe
like
our
group
or
or
gitlab
team
members,
or
something
like
that,
just
to
set
a
bar
for
ourselves
so
creating
the
gm
test.
Spec
is
the
first
checkbox
on
that
list,
and
that
issue
is
part
of
this
epic.
I'm
trying
to
get
just
the
bare
minimum
number
of
rendering
issues
that
will
make
it
so
that
we
don't
have
any
data
loss
or
data
corruption,
bringing
in
existing
wiki
pages.
D
I
think
the
biggest
one
that's
missing
on
this
list
is
wiki
specific
markdown,
so
I
moved
it
under
the
next
section,
so
things
like
being
able
to
create
links
in
the
wiki
automatically.
I
don't
know
how
content
editor
is
going
to
parse
that
we
can.
We
can
discuss
that
async,
but
let's,
let's
tighten
up
this
list
and
then
I'll
connect
it
to
the
ally
and
we
can
just
have
a
plan
and
start
checking
things
off
as
they
get
done.
G
G
Community
community
friendly
are
these
issues,
so
we
are
trying
to
do
like
in
my
case.
I
I'm
trying
to
write
a
tutorial
to
make
easy
to
pick
up.
Like
you
know,
extensions
are
easy
to
implement.
Even
we
have
like
parts
of
the
source
code
like
we
have
this
picture
where
you
paste
you
you
copy
html
in
in
an
issue,
and
you
get
markdown.
So
that's
also
based
on
pros
meter
and
it
has
a
schema.
So
we
can
use
some
of
that
code
as
an
example.
G
We
could
also
like
record
a
very
appearing
session
and
just
implement
another
simple
extension
and
share
that
youtube
link
as
an
example
for
a
while
communicator
community.
So
I
think
that
we
discussed
last
week
that
we
could
submit
some
of
those
issues
for
the
next
hackathon
and
all
of
those
resources
could
be
helpful
to
encourage
people.
E
I,
I
think,
that's
a
great
idea,
I
think
spending
just
a
little
bit
of
time
so
that
we
can
crowdsource
it
effectively
could
help
it
so
that
our
team
isn't
necessarily
the
only
people
implementing
all
this
would
be
would
be
really
cool.
Even
people
outside
of
our
group
that
are
get
lab.
Engineers,
too,
might
be
interested
in
contributing
to
outside
things,
as
well
with
that.
Looking
at
all
these
issues
and
some
crazy
idea,
is
it
because
these
are
almost
all
like
just
pure
functions.
E
It's
like
hey,
given
this,
we
expect
this
output
or
whatever,
like,
is
it
possible
that
we
could
even
just
create
like
the
test
case
like
we
know,
this
is
solved
if
this
is
the
test
case
that
would
like,
if
this
passes,
like
almost
a
test
driven
development
issue,
but
very
not
strict.
Do
you
think
that
would
make
it
more
friendly,
too
or
yeah?
That's
very
creative.
G
With
his
help,
where
we
use,
like
other
a
test
case
in
a
markdown
in
a
jammer
pile
with
a
magnum
example,
but
that's
like
very
easy
as
well
like
the
tutorial.
That's
the
way
that
the
tutorial
starts
with
a
failing
test
where
we
just
set
the
the
example
and
then
we
implement
the
extension
cool.
I
think
that
makes
sense.
B
E
B
Let's
talk
more
about
that
eric,
maybe
I
think
that's
the
reason
to
defer
doing
that,
because
the
biggest
benefit
of
that
is
like
locking
down
the
regression
on
both
sides,
the
back
and
never
changes
unless
the
framing
changes
at
the
same
time.
But
that's
not
necessarily
urgent
right
now,
because
we
don't
change
to
get
that.
Flavor
marked
down
that
often.
D
G
D
D
I
would
like
to
get
to
the
point
where
we
can
make
it
the
default.
Markdown
editor
in
the
wiki,
meaning
we
have
full
support
for
gfm,
there's
no
data
loss
and
then
we
can
start
refining
the
ux
and
building
custom
editing
tools
at
a
certain
point.
That
would
also
mean
persisting
the
user's
preference
for
using
it
at
a
certain
point.
Then
we
would
remove
the
preference,
so
that
might
be
six
milestones
from
now.
D
E
E
D
Yes,
I
have
thought
about
that.
I
should
have
said
at
a
certain
point
in
there
too,
we
need
to
tighten
up
the
relationship
between
content,
editor
and
source
editor
as
source
editor,
as
our
raw
viewer
in
our
raw
tech,
editor
and
content
editor
as
our
whizzy
wig
editor
and
be
able
to
switch
between
those
two
is
critical.
We've
seen
that
feedback
already
with
the
wiki,
like
some
people
say
this
is
great,
but
I
don't
want
it
right.
That's
fine,
and
we
don't
want
to
force
anybody
to
use
this.
D
We
don't,
I
don't
think
the
content
under.
I
should
have
clarified
it's
not
the
exclusive
way
to
edit
markdown
content.
It's
just
that.
We
don't
maintain
the
existing
classic
editor
anymore
and
instead
we
would
use
content
editor,
which
hopefully
also
has
a
mode
that
shows
just
raw
markdown
and
lets
you
edit.
That
way.
The
challenge
here
with
issues
is
that
the
issue
editor
also
has
all
those
extra
extensions
like
the
the
picker
for
issues
and
and
emojis
and
stuff
like
that.
D
D
E
Okay,
I
I
know,
as
I
was
thinking
about
it
growing,
I
would
trip
over
myself
a
whole
lot,
because
I,
if
I'm
not
in
them
world,
I
start
typing
them
commands
and
nons
in
windows.
If
I'm
not
in
markdown
world,
I
start
typing
markdown.
So
I
know
that
other
users,
if
we
all
of
a
sudden
change
it
on
them,
would
run
into
the
same
thing.
D
That
that
is
the
concession
that
I'm
hoping
we're
making,
but
there
still
is
a
there
still
is
a
percentage
of
our
audience
that
is
going
to
be
like
I
don't
I
don't
want
you
to
style
it
for
me.
I
want
to
see
it
in
this
way,
because
I
like
looking
at
the
matrix
right
like
it's,
it's
how
I
think,
which
is
fine
and
there's
nothing
wrong
with
that.
So
I
think
we
should
keep
that
in
mind
as
a
fallback
and.
E
G
D
That
one
that
one
person
can
honestly
go
use
a
different
tool.
I
do
not
ever
want
to
write
another
markdown
table,
html
tables.
Sure,
like
you,
want
to
write
all
your
opening
tags.
Markdown
tables
are
a
mess,
I'm
glad
this
is
being
recorded.
I
hope
we
put
it
on
youtube.
I
I
want
everybody
who
maintains
markdown
to
understand
how
messy
those
tables
are
can't.
C
Yeah,
I
think
what
we
can
do
is
we
can
have
a
toggle
button
that
lets
you
edit
in
a
markdown
editor
or
in
or
in
content
editor.
That
would
be
a
great
place.
We
don't
have
to
have
a
setting
in
that
is
hidden
in
the
settings
section.
You
can
just
have
a
setting
sort
of
a
button.
That's
always
there,
but
yeah
that
reduces
for.
D
D
So
I
think
in
in
the
technical
exploration
there,
we
can
rule
it
out
or
decide
how
it
needs
to
change
in
order
to
make
it
more
flexible
or
more
performant
or
whatever
the
concerns
are,
I'm
I
use
it
as
a
shorthand,
because
this
is
that's
how
I
think
about
editing
code
in
the
context
of
our
group,
but
yeah.
I
think
we
do
need
a.
We
do,
need
a
discussion
and
a
technical
plan
to
make
that
a
reality.
F
Just
to
give
some
background,
we
we
had
the
the
dedicated
session
with
the
source
code
group
earlier
today
regarding
exactly
this
thing
exactly
this
this
topic,
because
they
were
the
moving
force
behind
using
source
editor
for
rendering
the
blobs
and
they
already
have
the
have
it
implemented
behind
the
feature
flag.
Then
another
group
had
it
has
it
for
their
needs.
The
I
don't
remember
exactly
it's
in
the
security
security
stage
or
not
stage,
but
whatever
it
is
like
I
don't
know,
is
it
stage
security?
F
It's
not
staged
right,
it's
just
it's
just
global
global
thing:
okay,
yeah
secure,
but
they
have
like
they
have
groups
there
as
well.
So
it's
it's
kind
of
like
I
don't
know:
okay,
whatever
they
they
use
it
as
well,
and
using
the
conversation
we
had
in
slack,
I've
voiced
over
all
the
concerns
that
have
been
raised
during
the
slide
conversation
by
himanshu,
but
by
by
paul
by
chad.
F
F
F
What
what
solution
source
code
will
end
up
with
is
still
unknown,
because
we
still
have
to
run
a
lot
of
tests,
performance
tests
to
figure
out
the
most
performant
solution.
But
that's
that
shouldn't
really
block
our
discussions
of
because
we
have
our
use
cases
for
for
rendering
the
code
snippets
called
code
blocks
anyway.
D
A
G
G
F
F
F
What
this
is
about.
Vmr
is
the.
Let
me
just
copy
paste
this,
so
the
here
is
the
url.
So
the
data,
mr,
provides
the
provides
the
view
component
that
we
can
use
technically
anywhere
in
the
product
with
to
show
the
code
blocks
that
are
not
server
side
generated,
but
not
go
through
rouge
like
we.
We
just
take
the
string
as
the
input
for
the
code
block
and
pass
it
down
to
this
component,
and
it
is
going
to
use
it's
going
to
be
formatted
and
highlighted,
but
using
not
rouge,
but
monaco.
D
I
thought
somebody
was
playing
with
there.
Okay.
The
last
thing
is
on
the
agenda
settings
and
navigation,
and
I
wrote
none
of
the
things
with
the
focus
on
reliability.
We
had.
I
had
planned
loosely
to
to
address
some
of
the
feedback
on
settings
navigation
over
the
coming
milestones,
we're
likely
not
going
to
return
to
that
in
the
immediate
future.