►
From YouTube: Content Editor Weekly Catch up
Description
This is a very short Content Editor catch up where we discuss the status of the current milestone’s goals.
A
B
B
B
A
A
I
I
had
a
start
on
on
that,
but
I
don't
know
if
that's
like,
if
I
should
do
that
before
finishing
the
the
deliverables
that
we
have
for
for
13.11,
which
takes
to
my
next
point.
That
is
that
we
have
a
make
progress
in
including
the
feature
flag
and-
and
I
was
wondering
if
like
if
I
could
help
with
anything
in
that
area.
B
A
B
Yeah,
so
I
need
to
update
a
few
things
there,
because
I
think
it
should
be
become
easier,
I'll
actually
be
pushing
the
merchant
I
may
already
had
implemented
the
feature.
Flag
thing
is
not
very
like
it's
quite
straightforward,
just
have
to
add
an
if
condition
and
push
the
feature
flag
from
from
the
back
end,
along
with
all
the
content
with
the
password.
B
A
That's
right,
like
we
could,
like
perhaps
like
michael,
will
refine
the
work
well
a
little
bit
more,
but
we
can
start
to
conditionally
display
the
eight
or
based
on
if
the
user
decides,
to
use
it
or
to
hit
markdown
like
there
is
a
lot
of
work
that
we
can
do
that
doesn't
require
a
product
design
like
a
specific
design.
For
this,
like
the
workflow,
is
very
simple
like
we
just
need
to
display
the
editor.
A
If
the
user
decides
to
use
it
for
the
markdown
format,
and
then
we
can
continue
refining
that
maybe
we
can
save
that
setting
like
persisted,
and
so
the
the
editor
is.
The
competitor
is
a
default
option
for
markdown,
but
none
of
that
matters
I
feel
like.
We
can't
focus
on
just
defining
the
fixture
flag
and
then
displaying
that
button
on
that
warning.
When
the
user
chooses
to
the
content
data
for
18
martin.
B
A
B
A
B
B
A
B
B
A
Let's
not
persist
it
like,
let's
just
like,
like
turn
later
on,
like
every
time
that
the
user
wants
to
use
it.
They
have
to
turn
it
on
and
after
we
deliver
that
we
can
create
a
follow-up
issue
where
we
decide
if
we
want
to
persist
it
or
not.
We're
having
that
discussion
in
the
in
the
deliverable
about
handling
switching
between
content
formats
and
what
I
thought
I
did
was
like.
A
We
don't
have
enough
data
to
make
that
decision,
at
least
for
me
like
discussing
it,
feels
very
subjective,
and
it
feels
like
any
idea
that
I
provide
is
based
on
my
own
preferences.
So
I
think
that
we
have
to
to
to
do
it
like
to
to
make
the
first
step
that
is
just
like
allowing
to
enable
the
competitor
and
after
we
receive
feedback
from
users
or
from
our
internal
team.
We
can
decide
to
persist
it
or
not.
B
Yeah
because
people
would
intentionally
have
to
turn
on
the
feature
flag
and
then
use
this
feature,
and
we
also
have
a
warning.
So
that's
like
two
steps
they
have
to
go
through
and
if
you
have
the
button
in
place
and
if
you
click
on
button
every
time,
just
like
three
steps,
I
mean
you're
already
warning
people
two
times.
I
think
it's
three
times
a
little
bit
too
much.
A
Oh,
I
we
have
plenty
of
time
to
to
iterate
on
this
if
it
makes
sense
like
to
to
do
it
within
the
context
of
the
npc.
That's
what
I
really
don't
have
any
strong
opinion.
I
was
just
like
highlighting
that
we
can't
throw
it
on
it.
You
know
if
we
can
do
it
like
we're
in
the
same
phase
of
development
or
another
one
it's
like
for
me.
I
don't
have
like
any
opposition
to
it.