►
From YouTube: Content Editor weekly catch up
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi
everyone
this.
B
A
Quantitator
weekly
catch
up,
and
this
week
we
have
two
two
items
in
the
agenda.
A
First,
one
is
going
through
a
welfare
in
in
the
commentator,
toolbar
merge
request
and
the
second
one
is
very
similar
and
it's
about
going
through
the
continuity
or
integration
in
the
wiki,
mr,
where
we
just
include
date
or
based
on
the
on
whether
a
feature
plug
is
enabled
or
not.
A
So,
in
my
show,
I
want
to
to
take
some
notes
based
on
on
your
feedback.
While
we
go
through
the
through
the
first
mark.
In
that
way,
like
you
know,
I
can
take
advantage
of
like
we
are
here
together
and
and
after
the
meeting
I
kind
of
started
like
making
changes
very
soon
on
your
thoughts.
B
Yeah
you
wanted,
like
you,
want
to
look
at
the
mr
right
now.
A
B
B
A
Do
a
little
bit
of
sync
on
it
and
and
hear
your
your
thoughts
about
it.
I
know
that
eventually,
you
will
do
a
code
review,
but
I
wanted
to
take
a
little
bit
of
time
and
giving
you
a
lifetime
of
it.
A
So
I
have
loaded
the
the
branch
before
in
my
local
environment.
So
here
is
a
data
with
a
toolbar
pretty
much.
I,
the
the
december
is
not
focused
on
adding
all
of
the
the
possible
features
that
that
the
toolbar
could
have
it
just
like,
creates
a
basic
structure
for
having
buttons
and
having
the
basic
interface
and
highlighting
the
the
toolbar
button,
based
on
the
on
the
current
selection,
where
the
the
cursor
of
the
editor
exists.
A
So
now
we
have
like
when
they
when
they,
when
you
put
that
it
takes
the
the
text
cursor
on
on
on
a
code
snippet
like
it's
gonna,
highlight
the
the
the
button.
That
applies
a
format
if
you
put
it
in
a
list,
it
highlights
that
and
so
on,
and
if
you
go
here-
and
you
start
like
a
new
paragraph,
this
is.
A
It
does
like
you
know
it
works
like
I
suspected
that
in
you
know
their
haters.
You
know
that
don't
have
a
toolbar
like
there's
nothing
surprising.
A
There
are
some
elements
here,
like
the
blood
quote
that
if
I
do
this,
you
will
notice
that
it
doesn't
have
any
style
like
it's
a
blog
quotes
and
it's
like
it
doesn't
look
different
at
all
from
from
other
from
a
normal
paragraph.
So
the
problem
with
that
is
that
if
you
go
here,
you
see
that
there
is.
Actually
you
know
the
the
text
that
I'm
writing
is.
A
B
Yeah,
you
can
actually
do
if
you
just
go
to
the
gl
markdown
class
above
here
you
just
just
add
md
class.
That
should
maybe
do
things
for
you.
Oh
let.
A
A
Oh,
that's
really
cool
yeah,
so
it's
like
those
styles
are
already
implemented
in
there.
So
what
I
would
like
to
do,
like
the
reason
that
I,
that
I
use
the
the
lg
markdown
and
lg
compact
markdown,
is
that
these
classes
implement
the
the
pajamas
markdown
type
scale
and
what
I
wanted
to
what
I
think
that,
like
it
would
be,
a
good
contribution
is
to
to
use
the
type
the
margin
type
scale
that
conforms
with
the
with
the
design
system.
A
A
In
gitlab
pri
and
I
implemented
a
upload
quote,
the
advantage
of
doing
that
is
that
it
is
actually
it
started
a
discussion
in
the
foundation
foundations
team,
where
they
noticed
that
there
are
made
several
elements
that
are
that
are
not
documented
in
the
design
system.
A
Also,
I
got
like
some
feedback
from
from
the
product
designers
in
the
in
the
in
the
foundations
team,
where
they
told
me
like
hey,
probably,
you
should
use
a
different
type
of
color
that
is
like
it
has
a
good
contrast
to
make
it
to
make
it
accessible
and
conform
with
those
with
those
specifications.
A
Also,
I
noticed
that,
like
here
there
is,
there
are
other
people
in
the
product
design
team
that
are
creating
issues
for
a
studying,
blog
quotes
or
creating
like
well
fixing
accessibility
issues
by
by
working
on
these
styles
and
implementing
those
elements,
styles
in
the
in
gitlab
ui,
we
are
pretty
much
helping
the
foundation
team
to
to
regrow
on
to
write
like
correct
styles,
for
all
of
the
meltdown
type
scale.
B
Yes,
but
in
my
opinion,
if
you
just
that
would
kind
of
be
different
from
what
the
markdown
tv
shows
you,
because
it
uses
the
old
style.
So
so
you
might
be
right
in
like
using
proper
pajama
styles
for
everything,
but
it's
not
a
right
thing
to
do
for
for
the
end
users,
because
they
see
something
in
the
the
content
editor
and
they
would
see
something
else
when
actually
do
the
page.
B
So
as
long
as
we
can
be
consistent
with
what
you
see
is
what
you
get.
Basically,
when
you
actually
view
the
page,
then
also
it
should
be
using
the
tl
markdown
spell.
A
But
why
don't
we
use
these
transition
period
to
implement
and
to
increase
like
the
the
whole
implementation
of
the
market
on
timescale?
If
we
finish
the
implementation,
we
can
even
deprecate
the
markdown
styles
that
exists
in
gitlab
and
replace
it
with
the
with
the
correct.
You
know.
B
My
point
was
that
we
should,
if
we
are
taking
care
of
the
markdown
style,
we
should
do
it
at
both
places
in
the
editor
and
in
in
the
preview
as
well,
because
we
don't
want
people
to
use
the
editor
and
you
when
they
are
using
the
editor.
They
see
something
and
when,
when
they
actually,
let's
say
they
see
something
right.
A
Yes,
I
I,
I
think
that,
having
that
consistency
between
the
display,
markdown
and
eating
it
in
the
vicinicator
is
is
very
important.
We
definitely
should
like
have
that
consistency,
but
that
you
know
yeah
like
I.
I
think
that,
like
it's
a
like
during
this
transition
period,
perhaps
at
the
end
of
the
of
the
implementation
of
the
of
the
of
the
quantitative
nbc,
we
may
consider
to
to
also
use
the
the
margin
type
scale
for
displaying
markdown
in
the
wiki.
A
B
I
think
I
agree
with
that
as
well.
You
can
also
consider
it
as
a
stretch
pole,
but
but
yeah
we
can
go
in
the
other
direction.
A
Yeah,
I
think
that's
something
that
that
can
be
useful
is
to
to
determine
which
other
styles
we
have
to
implement.
I
know
that
we
don't
have
a
stylus
for
tables
yet,
and
we
could
like
on
the
gitlab.
Ui,
still
doesn't
implement
the
styles
for
lists,
so
something
that
that
I
was
thinking
about
last
week
is
to
talk
with
eric
and
well,
not
only
with
eric.
I
actually
have.
B
A
Once
we
have
a
new
meeting
where
we
determine
what
we
are
gonna
be
spending
time
in
in
13.12
and
unfortunately
0.0
we
can
determine
if
we
want
to
expand
some
resources
on
implementing
those
styles.
You
know
when
we
start
like
implementing
the
tables,
extension
or
or
other
type
of
extension.
We
could
dedicate
some
time
to
implement
the
you
know
like
the
actual
styles
that
are
documented
in
pajamas.
A
Cool
so
yeah,
that's
like
pretty
much
the
the
the
toolbar
what
what
the
toolbar
does
now.
What
do
you
think
about
the
the
styles
here?
What
we
could
like
change,
or
something
that
I
noticed
last
week
when
you
were
talking
sharing
with
me
about
the
the
focus
that
you
implemented.
I.
B
A
Here
in
the
in
the
mercy
quest,
I
think
that
the
the
most
important
highlight
is
the
is
a
the
toolbar
button
component.
So
what
I
did
here
was
like
every
toolbar
button
that
that
executes
like
that
executes
a
command
or
applies
some.
I
apply
some
form
with
like.
A
B
I've
already
seen
the
voice
request
so
yeah.
I
I
understand
that
it
has
a
youtube
command
and
it
has
a
way
of
knowing
the
state
as
well
like
it
is
attractive
or
not,
and
I
think
that's
really
great.
A
B
Now
I
was
actually
going
to
approve
it
already,
but
I
did
not
do
it
because
I
wanted
to
have
a
look
at
it
once
again,
but
yeah
the
the
merge
request
looks
really
good.
The
only
thing
I
would
like
to
talk
about
is
maybe
focusing
like
we
are
adding
some
classes
to
the
the
frozen
component
element
and
I
also
want
to
add
some
classes
to
it.
B
So
I
you
me,
I
mean
as
someone
who
is
consuming
and
contemplative,
we
would
want
something
that
we
can
pass
to
the
editor.
A
great
editor
function.
B
Well,
whenever
I
like
you,
I
don't
want
my
classes
to
override
your
classes.
We
want
to
combine
the
process
together,
so
adding
that
functionality
would
be
would
be
interesting.
B
Yeah,
and
also
basically,
what
I
was
doing
was
I
was
adding
classes
to
make
it
look
like
a
form
element,
but
but
we
need
those
classes
on
on
the.
B
Container,
but
we
need
to
figure
out
how
to
do
that.
I
think
it's
it's
okay.
We
can
do
it
right
iteratively.
As
soon
as
we
get
the
integration
out,
we
can
then
focus
on
the
toolbar.
A
Yeah
yeah,
like
once
I
I
know
that
I
saw
in
in
the
in
new
mercy
quest
like
we're.
Gonna
go
we're
gonna,
see
it
again
now,
but
I
noticed
that
you
even
regrow
the
the
element
that
the
view
the
view
component,
that
that
provides
tip
tap
to
attach
the
transmitter
view
to
two
of
your
components.
B
A
Well,
I'm
gonna
then
stop
sharing,
so
you
can
share
your
your
screen.
B
Oh
well,
in
terms
of
my
mr.
B
Last
with
you,
but
there
are
a
couple
of
important
army
like
I
wrote,
a
lot
of
tests,
so
actually
we
don't
really
need
to.
We
don't
I
mean
I
finished,
writing
all
the
tests
so
and
they're
all
passing.
We
don't
need
to
have
a
pairing
session
for
tests,
at
least
after
this.
B
Yeah
so
I
rewrote
this,
but
but
my
idea
was
doing
two
things,
so
I
wanted
to
destroy
the
old
editor
whenever
you
reset
it
towards
something,
but
I
didn't
realize
that.
B
And
I
don't
think
we
should
actually
create
a
like.
Why
do
we
even
need
to
create
a
init
content
editor
every
time?
B
Can
we
not
just
like
make
it
free
render
again?
B
I
don't
know,
but
I
think
it
makes
sense
to
create
a
new
editor
every
time,
because
it
is
not
really
a
an
operation
that
people
would
do
again
and
again
right.
A
That's
right,
we
just
need
like
we
just
need
one
editor,
and
then
we
can
set
the
content
and
update
the
content.
B
Now
my
point
was
that
it's
okay
to
create
an
editor
every
time
you
create
content
later,
because
switching
between
editors
is
not
something.
People
would
do
very
often
like
it's
not
like
you're
going
to
switch
between
the
markdown
and
content
later
again,.
A
Makes
sense
like
you,
you
don't
switch
between
views.
Well,
let
me
see
if
I,
if
I
understood
what
I,
if
I
understand
what
you're
saying
you're
saying
that
we
don't
need
like
to
run
this
line
of
code.
A
A
B
That
that
sounds
great.
So
if
I
I'm
sharing
my
screen
and
yeah,
I
don't
think
that
you
can
be
able
to
see
my
vs4
yeah.
You
can
see
it.
B
You
can
see
vs
code,
yeah,
okay,
great.
B
I
mean
it's
not
showing
a
border
around
it,
so
it's
weird.
So
what
we
need
to
do
is
yeah,
create
the
editor
and
all
that.
But
let's
say,
if
I
don't
pass
it
content,
oh
yeah,
you
can
actually
get
consequences.
A
When
do
we
call
init
contentator.
B
B
Because
we
we
don't
really
know
that
people
want
to
use
the
editor.
So
as
long
as
we
don't,
we
just
don't
import
anything
or
don't
do
anything
with
it
at
all.
B
So
yeah,
I
think
this.
This
is
a
great
idea
that
you
just
played
the
editor
once
that
way,
what
I
can
do
is
I've
been
worrying
about
destroying
the
editor,
and
I
actually
don't
need
to
do
that
anymore.
A
B
Yes,
that
that's
what
I
am
doing
and
let
me
just
show
it
to
you:
if
we
go
to
the
wiki,
I
don't
know
why
that
was
not
working.
Let
me
just.
B
B
B
Yeah,
the
only
difference
now
is
that,
instead
of
the
data
element
we
had
earlier
now,
we
are
actually
passing
later
and
we
are
adding
all
these
classes
to
the
closure
object,
which
I
believe
we
can
do,
which
I
believe
we
can
actually
pass
today.
Objectives
here,
right.
A
B
Classes,
I
think
I
think
we
should
not
provide
the
classes
here,
because
it
does
not
make
sense
since
it
we
should
actually
provide,
since
we
are
already
getting
the
editor
object
here,
I
think
mirror
should
should
give
you
an
option
to
provide
the
classes
after
the
item
has
been
created.
B
So
instead
of
doing
this,
I
would
just
do
this.
Dot
editor
dot,
some
set
some
classes,
and
then
I
would
add
these
classes
instead
of
the
five
line
code.
It
would
be,
it
would
be
a
one
line
code,
but
yeah.
I
would
still
want
that.
The
code
exists
here,
not
anywhere
else.
B
B
A
Yeah,
it's
very
it's
very
simple.
In
the
in
the
toolbar
merch
request,
we
have
more
tests
because
we
are
including
the
toolbar
we
are,
including
like
we
are
passing
the
properties
to
the
to
several
components,
but
at
the
other
stage
is
probably
not
necessary.
B
Okay,
so
I
think
for
now
I
can
go
and
just
delete
this
file.
What
do
you
say.
B
Foreign,
I
was
going
to
show
you
what
exactly
is
happening
in
the
content.
Editor.
B
Looks
like
I
can't
show
you
anything
yet.
In
the
meantime,
I
think
I
can
go
and
while
gdk
is
doing.
A
B
A
Yes,
but
I
don't
think
that
the
prosmeter
eter
class
exposes
an
api
for
it.
The
tab,
like
the
the
internal
tip
tab,
view
object.
Interview,
object,
provides
a
method
to
play
the.
A
Actually,
those
it
has
a
a
set
method
that
we
can
use
for
it.
Okay,
and
that's
that
I'm
gonna
send
you
the
link
to
it.
B
And
then,
or
what
was
the
property
called?
It's
called.
A
Yeah,
that's
it
that's
the
name.
I'm
gonna
send
you
the
they
sack,
they
sack
syntax
for
doing
it.
B
Await
a
prop,
so
if
you
have
other
stuff
in
edited
file,.
A
A
B
Yoga,
it's
not
going
to
merge
the
classes.
I
know
that
for
sure,
but
I
just
want
to
make
sure
it
merges.
B
I
think
twice
so
I
think
you
should
merge.
I
think
I
think
it
should
be
obvious,
but
yeah
some
things
are
not
very
obvious.
B
B
B
A
A
B
B
Let's
look
at
our
test.
It
is
still
failing
that
will
destroy
same
child.
B
B
Because
because,
yes,
it's
very
slow
in
the
watch
mode,
it's
gonna
screw
up
everything
my
cpu
and
everything,
and-
and
I
don't
want
to
watch
all
the
tests
you
just
want
to
watch
whatever
is
whatever
code.
I
have
seen.
B
Yeah,
I
don't
want
to
watch
it
because
it's
going
to
slow
down
my
computer,
I
know
like
because
I'm
going
to
make
a
lot
of
changes.
Probably
so
I
don't
want
to
keep
on
running
tests
for
every
change
I
make,
and
especially
now,
when
I'm
streaming
on,
zoom
and
and
also
trying
to
run
gdk
and
just
at
the
same
time
so
and
it's
already
everything
is
already
very
slow.
I
don't
want
to
talking
about
further.
B
That's
why
I
just
manually
run
tests
whenever
I,
whenever
I,
whenever
I've
actually
written
them,
yeah
I'll,
just
give
you
a
demonstration
of
what's
going
on
here.
So
there
are
a
couple
of
changes
that
I
have
done
from
since
I
last
showed
it
to
you
so
use
new
editor
and
then
you
see
a
markdown
editor.
B
Here
yeah
it
took
it
took
a
while,
but
yeah
the
content
shows
up,
and
you
can
add
more
content
here
and
when
you
switch
between
rdof
and
markdown.
So
you
can
see
that
the
old
content
that
I
typed
it
shows
up
here
as
well.
B
B
I
just
changed
this
code
right
now,
so
that
is
why
the
behavior
is
a
little
different.
Now
I
don't
really
want
to
do
that.
Actually,.
A
They
yeah
we
should.
We
should,
as
like
the
random
breakdown,
accepts
a
parameter,
an
argument
that
is
like
the
the
markdown
that
will
be
converted.
So
we
should
be
passing
that
mark
down
to
the
to
get
content
html
instead
of
providing
the
instead
of
using
the
components
state.
A
B
A
Because
that's
when
we
use
the
the
markdown
serializer
in
other
contexts
like
based
in
markdown,
the
markdown
won't
be
coming
from
the
component
state.
B
B
So
sets
realize
content.
My
question
to
you
is:
does
sexualized
content
actually?
Does
it
return
your
promise?
Yes
great,
so
I
can
actually
do
an
await
on
it.
So
the
issue
that
we're
seeing
right
now
that
that
there
is
a
flicker,
like
you
see
in
all
the
old
content
for
a
while,
and
then
it
automatically
updates
the
new
content
that
should
not
happen
anymore,
so
that
should
be
resolved.
B
B
So
if
you
are
making
any
changes
between
the
process,
your
changes
will
be
transferred
to
the
new
editor
and
then,
when
you
switch
back,
it's
again
transferred
back
to
the
old
editor.
Although
we
don't
really
recommend
you
doing
all
of
this,
but
nowhere
in
the
process
you
are
going
to
lose
your
lose
whatever
data
you
have
entered
in
the
input.
A
Yes,
that's
that's
pretty
good,
I
think.
That's!
That's
that's
aligned
with
the
with
the
user
expectation
it
doesn't
matter
if
they,
you
know
they're
using
a
different
format.
At
least
they
know
that
when
you
go
back
from
the
content
editor
to
to
our
doc
or
something
like
that,
if
they
get
mark
down,
it's
because,
like
they've,
never
had
the
expectation
of
getting
something
different
right,
like
converting
the
something
in
the
content,
data
to
a
different
format.
B
Yeah
and
also
like,
let
me
just
try
that
again,
let
me
just
go
ahead.
B
I
think
I've
screwed
up
but
yeah
I've
written
tests
for.
B
B
Yeah,
I
just
wanted
to
show
you
that,
like
you're
persisting
the
content
when
you're
switching
between
the
format
and
that's
it,
let's
go
ahead.
A
So
in
my
in
my
case,
I'm
going
to
to
update
the
focus
state,
the
styles
that
the
editor
has
now
and
I'm
gonna
put
it
around
the
toolbar
to
make
it
more
similar
today
to
the
coordinator
and
then
and
if
like,
if
I
should
do
that
before
you
you,
I
don't
know
before
you
take
a
second
look
at
the
at
the
tool.
Narrator.
What
do
you
think
or
should
I
do
it
in
a
or
should
we
wait
or
to
to
another
iteration?
B
Yeah
we
can
deliver
the
mr
as
it
is.
I
think
it
looks
really
good
iteration
and
we
don't.
We
can
worry
about
how
it
looks
and
and
all
those
things
you
know
in
a
different
direction.
Maybe
you
can
create
an
issue
for
that
as
well.
That
would
be
better.
B
A
I
completely
agree
cool
in
that
case.
Let's
merge
it
as
series.
My
next
step
would
be
to
create
a
drop-down
component
where
the
user
can
switch
between
headers.
Now
we
don't
have
like
a
like
multiple
hidden
icons
like.
A
B
Because
the
use
case
of
wikis
is
someone
who
is
a
much
more
advanced
user
for
documentation.
So
I
think
you
people
would
easily
have
more
than
three
heading
styles.
So
having
an
option
of.
A
Sounds
good,
so
that's
gonna
be
my
first,
my
next
step,
then
that
and
I'm
reviewing
the
the
quick
integration
one
yeah.
Oh
so
I'm
gonna
stop
the
recording.
Now.