►
From YouTube: Create:Editor - June 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
A
A
A
A
We
can
work
async
on
like
making
sure
that
the
communication
is
tight
and
the
feature
flags
get
turned
on
by
default
at
the
appropriate
time.
But
I'm
feeling
very
very
happy
with
where
we
are
and
just
really
excited,
because
it's
all
falling
into
place-
and
I
know
you've
all
been
working-
really
really
really
hard
on
it,
probably
spending
more
hours
than
you
should
to
make
sure
we
get
this
in
for
14.00,
and
I
do
appreciate
it.
I
promise
I
won't
do
this
to
you
again,
at
least
not
until
15.00.
A
A
The
two
bigger
strategic
things
that
I
I
want
to
push
for
this
month
is
understanding
some
opportunities
around
rethinking
our
commit
flow,
and
we
talked
about
like
kind
of
building
a
component
that
could
handle
any
kind
of
get
actions
that
we
want
to
throw
at
it
and
then
maybe
behind
the
scenes,
working
on
improving
the
performance
and
resilience
of
that
endpoint,
so
that
we
can
make
it
not
take
25
seconds
to
create
an
mr
or
something
along
those
lines.
Based
on
the
feedback
we
got
from
the
static
site
editor.
A
I
think
it's
relevant
anywhere
that
we
start
introducing
a
commit
flow.
This
could
be
used
in
the
web
ide.
It
could
be
used
in
a
future
pages
based
wiki
knowledge
base
product
offering.
So
we
have
opportunities,
just
like
we've
done,
with
the
content,
editor
and
and
the
source
editor
to
build
something
reusable
and
extensible,
or
at
least
customizable.
A
That
could
bring
value
to
a
lot
of
different
categories,
most
of
which
we
own,
but
some
of
which
we
don't
that's,
going
to
take
probably
a
a
little
bit
of
planning.
It's
not
something
we'd
ship
in
14
1,
but
I'd
like
to.
I
was
talking
to
michael
in
our
design.
Sync
I'd
like
to
set
up
a
think
big
session.
A
I
had
shifting
gears.
I
had
a
great
conversation
with
some
of
the
folks
on
the
plan
team,
about
their
vision
for
the
issue
and
epic
description
experience
and
and
how
you,
the
the
the
conversation
started
as
a
as
a
way
to
understand
what
we
might
be
able
to
do
to
bring
conversations
and
and
comments
up
into
the
description
itself
and
it
kind
of
evolved
into
just
us.
A
Sharing
our
visions
and
roadmaps
for
for
both
of
those
areas
and
how
the
content
editor
being
introduced
into
the
issues
could
help
them
achieve
some
of
their
goals
and
where
we
might
need
to
extend
our
vision
wider
to
support
some
of
the
workflows
that
they're
thinking.
But
I
will
post
the
video
which
was
recorded.
It
was
a
good
conversation
and
the
designers
are
thinking
big
about
the
problems
that
they're
trying
to
solve
there
in
the
the
main.
A
Takeaway,
though,
is
that
once
we
can
get
content
editor
in
there,
the
there
are
a
lot
of
opportunities,
especially
around
embeddable
content.
If
you
could
embed
a
like
a
road
map
view
or
something
like
that,
you
know
providing
a
way
to
create
extensions,
that
they
can
build
custom
ui
around
the
drafting
experience
to
extend
beyond
even
get
lab,
flavored
markdown
or
you
know,
introduce
the
ability
to
query
something
and
then
output
html
into
the
editor
itself,
that
that's
that's
some
really
interesting
stuff
they're
thinking
about.
A
C
A
I
think
for
the
content
editor,
our
focus
should
be
almost
entirely
on
just
getting
to
full
support
for
gfm,
but
tables
and
images
are
probably
our
biggest
focus
for
the
next
two.
If,
for
some
reason
we
can
ship
those
quickly
like
there's
plenty
of
other
things
like
mentions
or
labels,
or
things
like
that,
that
probably
would
be
really
really
helpful,
although
maybe
less
used
in
wiki
in
the
context
of
a
wiki,
they
are
important
to
build
the
support
for
that.
A
B
A
Just
do
collaborative
live,
editing,
14.2
I'll,
announce
it
right
now
right,
so
we've
got
a
product
intern,
starting
in
14,
1
and
I'll,
be
working
with
him
to
to
break
down
the
concept
of
embedding
snippets,
which
I
think
is
another
really
exciting
problem
to
solve.
So
an
mvc
there
for
how
we
can
handle
embedded
content
in
the
content
editor
and
how
we
can
display
like
browsing.
A
Your
available
snippets
for
inclusion
in
the
content.
Editor
there's
a
lot
of
interesting
problems
to
solve
there.
The
the
work
that
I'm
hoping
that
we
will
achieve
in
14,
1
and
14
2
is
to
take
the
problem
and
break
it
down
into
something
really
small
that
we
can
ship
in
in
14
to
so
that'll,
probably
be
the
other,
the
other
big
one.
A
A
B
A
B
A
Yeah
should
have
done
that
also
by
the
way.
So
that's
on
the
record
fran.
Thank
you
for
jumping
in
on
that
data
dictionary
issue.
For
me
that
has
been
lingering
for
two
milestones
in
the
back
of
my
mind
and
I
have
not
wanted
to
bother
any
of
you
because
you're
all
working
so
hard
and
I
kept
thinking
I
can
do
this
myself.
I
know
I
can,
and
it's
just
I
could
not
do
it
myself.
E
E
A
F
F
So
I
did
the
ones
that
I
caught,
but
a
missed
big
one
in
hindsight,
you'll
remember
that
amy
has
not
discussed
in
the
last
two
milestones.
How
many
pages
actually
mentioned
the
admin
area
she
talked
about
product
over
group
overviews
and
project
overviews
never
talked
about
the
admin
area,
because
I
missed
it
in
screencaps.
So.
F
F
F
I
want
you
all
to
imagine
the
horror
that
comes
when
you're
a
week
out
from
a
release.
You
discover
that
you
have
several
hundred
pages
in
the
you
in
the
docs
that
all
need
to
be
changed
and
you
have
12
people
who
are
about
to
go
all
in
on
this.
How
do
you
do
it?
So
the
answer
is
actually
in
issue
333
265,
which
which
I
linked
in
in
the
q,
a
section
what
we
did
we
broke
it
down
by
stage.
F
We
have
a
standardized
graph
that
we
run
all
the
time
that
starts
with.
Okay.
Just
go
find
me
all
the
pages
for
this
group
and
then
do
something
horrible
with
it
and
grub,
and
that
has
allowed
us
to
do
multiple
types
of
issues
in
in
parallel
in
this
way,
like,
for
example,
master
to
main
changes
across
all
of
our
docs.
That
also
come
and
do
in
14.0.
F
F
H
Yeah,
the
the
number
of
contacts
that
gitlab
has
for
any
feature
is
it's
combinatorially
complex,
yes,
but
there's
actually
a
special,
and
this
actually
shows
up
in
our
top
now.
This
is
what
chad's,
highlighting
and
something
that
we
weren't
totally
aware
of.
We
ran
into
is
there's
a
admin
setting
to
set
that
admins
should
enter
their
password
before
they
do
an
admin
thing.
H
H
F
Yeah
yeah,
you
haven't
met
me,
but
you
you've
met
me
okay,
so
so,
if
you,
if
you
are
aware,
looking
at
you
chad
of
items
that
are
changing
in
140,
that
I
did
not
cover
in
the
issues
that
are
linked
here,
I
need
to
talk
to
you,
because
I
need
to
make
sure
that
our
docs
are
right.
So
we've
got
time,
let's
take
care
of
it.
F
H
I
think
I
think
this
highlights
something
something
that
we
are.
This
is
an
obstacle
that
hits
us
in
engineering
across
engineering,
technical
writing,
but
we
have
some
vague
idea
of
what
each
other
are
doing,
but
in
the
week
we're
not
totally
aware
of
the
changes
in
this
state
that
other
people
are
doing.
Our
weekly
status
updates
are
kind
of
like
here's.
H
What
I
did,
but
it
would
be
really
neat
to,
because
you
know
this
this
small
thing
that
happened
like
I'm
becoming
more
and
more
convinced
that
somehow,
when
everything
is
transparent
and
all
the
information
is
out
there,
then
nothing
is
visible
and
you're
not
going
to
be
able
to
see
anything.
So
somehow
there
needs
to
be
a
level
of
collaboration
where
there's
just
because
it
just
take.
H
I
don't
have
to
collaborate
with
everybody,
but
if
we
do
the
network
right,
then
I'm
only
just
one
node
off
from
any
kind
of
information
that
might
be
relevant
or
something.
So
it's
like,
I
think,
when
we
were
doing
right
now,
we've
kind
of
been
pairing
up
on
issues
which
is
cool,
but
it's
been
chad
and
I've
been
pairing
up
on
this
issue.
H
So
one
solution
to
this
is
which
chad
has
taught
me
the
term
promiscuous
pairing,
namely
that
we
make
sure
we're
always
syncing
up
with
lots
of
different
people,
which
is,
which
is,
I
think,
helpful.
And
I
know
earlier
a
couple
weeks
ago
dennis
and-
and
I
conflicted
on
mr-
where
I
was
pushing
the
startup
css-
that
include
dennis's
old
changes
and
wasn't
aware
of
whatever
it's
gonna
and
there's
no
way.
H
I
would
have
been
and
there's
no
way
that
he
would
have
been
aware
that
this
thing's
getting
merged
just
now,
because
we
do
kind
of
operate
in
silos
that
have
radio
communication
every
once
in
a
while.
So
there
is
an
obstacle
here
and
it
had
been,
and
I
think
it's
highlighted
with
what
amy's
felt
from
the
technical
writing
perspective,
but
even
across
engineering
there
is
some
sort
of
an
obstacle
here.
That'd
be
interesting
to
find
ways
to
address
so
go
ahead.
Try.
G
F
And
I'm
open
to
that
by
the
way,
especially
since,
in
the
last
few
months
as
bless
you
paul,
you
can
attest
I'm
tackling
more
merge
requests
that
are
a
blend
of
docs
ux
in
front
end.
So
what
you're
working
on
is
of
more
interest
to
me
than
you
might
realize,
because
I'm
trying
to
learn
how
to
do
it.
A
So
in
an
office
setting
in
an
organization
that
would
favor
lots
of
meetings,
this
would
be
something
that
where
somebody
would
recommend
we
have
a
daily
stand-up
and
we
say
what
you're
working
on
or
what
you've
completed
yesterday.
What
you're
working
on
today
are
you
blocked
by
anybody,
the
typical,
like
agile
stuff,
so
without
recommending
that
we
do
a
daily
stand-up,
because
nobody
wants
that
and
it
doesn't
work
for
asynchronous
communication,
and
I
certainly
don't
want
more
meetings.
A
H
I'm
muted,
sorry,
I
think
there
might
be
a
small
tweak
we
can
make,
which
would
improve
that.
So
I
I
am
to
my
embarrassment.
I
I
contribute
very
little
to
our
async
stand
up
and
I'm
sorry
about
that,
but
perhaps
if,
instead
of
it
being
on
a
separate
channel,
I've
seen
other
groups
do
this,
where
it's
all
on
the
same
channel.
H
H
G
A
Is
possible
for
for
the
record,
I
think
it
would
have
a
tendency
to
get
lost
in
the
shuffle
and
we
don't
need
everybody
to
see
the
stand-up
updates
unless
we
separate
the
concerns
a
little
bit.
I
feel
like
our
stan.
Our
stand-up
questions
are
a
hybrid
of
how
you
doing,
and
also
like
specific
stand-up
stuff.
So
I
think
maybe
the
iteration
here
is
to
just
get
a
little
more
tight
on
the
purpose
of
those
questions
and
try
and
get
the
information
that
we're
looking
for.
A
G
This
would
be
the
right
tool
to
solve
this
particular
problem,
because
things
would
have
been
said
like
working
on
the
menu
like
maybe
moving
the
admin
button,
or
I
don't
even
know
what
it
would
have
caused
me
to
mention
this.
Maybe
only
the
fact
that
I'm
struggling
with
like
admin
mode
in
the
feature
specs,
but
that's
so
technical.
I
might
not
even
have
mentioned
that,
because
I
did
mention
I'm
working
on
this
as
part
of
my
stand-up
post
anyway.
H
I
think
you're
totally
right
chad
because
I
do
think
something
goes
and
when
you
used
to
have
a
front-end,
department-wide
kick-off
to
catch
conflicts
and
stuff.
But
when
you
have
these
like
announcement
sessions,
the
the
quality
of
information
it
doesn't,
it
doesn't
carry
and
the
quality
of
people
hearing
it
too.
It
doesn't,
it
doesn't
carry,
and
then
it
really
can
just
end
up
being
a
time
sync.
So
maybe.
C
Maybe
we
integrate
the
the
documentation
as
part
of
the
design
process
where,
when
we
are
implementing
the
you
know
any
changes
we
could
from
the
ground
up
like
build
the
list
of
things
that
we
have
to
change,
for
example
like
if
we
are
designing
our
strategy
to
deliver
the
navigation
changes
in
many
nurse
requests.
I
guess
that
we
came
up
with
a
list
of
things
that
we
have
to
change,
so
maybe
in
that
list
we
say
hey
we
have
to
to
make
like
you
know.
C
G
So
we
already
have
a
check
box,
I'm
not
sure
if
it's
on
the
issue,
template
of
the
mr
template
that
says,
are
there
documentation
changes
for
this
as
far
as
this
particular
top
nav,
I
think
that's
like
buried
in
some
parent
issue
that
I
haven't
looked
at
for
weeks,
because
we're
deep
three
leafs
down
on
mr
implementation,
but
there
like
is
a
process
for
this
already.
You
should
be
thinking
about
this
when
you
look
at
that
checkbox
as
part
of
the
issue.
H
But
well
it's
hard.
I
just
tried
to
do
a
search
just
now
through
the
docs
for
admin
mode.
I
didn't
see
anything.
I
saw
maintenance
mode,
but
that
does
still,
I
don't
know
if
we
haven't
documented
it
somewhere
like
like,
so
the
traceability
of
what
we're
changing
to
where
it
lives
in
the
docks
can
be
a
huge
challenge
too.
I
I
should
have
searched
on
google.
That's
that's
what
I
I
should
have
just
been
searching
on
google.
Why
was
I
using
gitlab
search
hang
on?
I
think
I
got
it.
H
F
Well,
and
also
I
I
also
want
to
plant
the
idea
that
it's
not
just
on
the
engineers
you
should
also
be.
You
should
be
expecting
more
of
your
technical
writer
too.
You
are,
you
can
and
should
loop
me
in
on
issues
and
say
hey.
Do
you
think
this?
This
would
change
stuff,
and
you
can.
I
love
being
asked
that
early
you're
not
imposing
I'm
delighted
when
I
see
those
because
sometimes
they'll
say
oh
yeah,
no
big
deal
and
sometimes
I'll
say
and
start
making
a
lot
of
issues
and
that's
my
job.
H
The
reason
why
I
mention
a
label,
as
I
know,
there's
a
huge
motivation
for
like
it
could
get.
It
could
get
a
lot
when
a
mr
is
going
through
multiple
engineering
reviews,
and
then
we
have
database
reviews
and
the
docs
which
technically
can
be
handled
asynchronous
are
like
part
of
that,
mr
being
merged
as
like
a
blocker
to
that
it
would
be
interesting.
H
F
C
F
B
A
It's
your
meeting
too.
This
is
not
no
hijacking
involved.
This
is
great
anything
else
we
want
to
cover,
because
I
want
to,
I
actually
do
have
another
meeting
to
drop
to
get
to,
but
we
are
still
within
our
time
frame
if
you
have
any
other
topics
to
cover
all
good.
Thank
you.
Thank
you.
Thank
you
again,
everyone
for
your
hard
work
over
the
past
few
months
and
forever
you
always
work
hard,
but
specifically
the
past
few
months.