►
From YouTube: Rich text editor / Wiki edit page Vue weekly catch up
Description
In this call, Himanshu and Enrique talk about the cost of implementing Gitlab Flavored Markdown support in the content editor. They also review the current status of the projects before the end of the milestone.
A
A
A
A
We
are
now
two
days
before
the
end
of
this
medicine,
and
I
don't
think
that
I
I
like
we
will
be
able
to
to
deliver
the
the
the
complete
the
complete
goal
of
the
scaffolding
that
was
setting
up
this
test
framework
setting
up
the
directory
structure,
how
we're
gonna
organize
all
of
the
code
for
the
component
and
also
adding
some
basic
documentation
describing
all
of
those
artifacts.
So
that's
not
happening
on
on
this
medicine,
because
it's
like.
C
A
A
However,
that
goal
we
have
that
goal,
but
I
I
feel
that
the
requirements
or
the
scope
of
the
nbc
is
not
clear
and
it's
difficult
to
to
determine
if
we
can
achieve
that
goal.
Since
I
don't
know
exactly
what
an
nbc
means
in
the
content
in
the
context
of
the
content
editor,
I
have
three
questions
that
I
feel
that
that
that
could
help
us
to
actually
find
the
embassy
the
npc,
the
the
first
one
is.
A
A
B
B
A
When,
when
I
say
about
when,
when
I
talk
about
displaying
account
a
content
and
not
providing
18
tools,
I
don't
I
don't
mean
that
data
will
be
read
only.
What
I
mean
is
that
we
can
display,
for
example,
a
table
in
the
in
the
content
editor,
and
we
don't
provide
a
specific
table.
Specific
editing
tools,
like
the
user,
can
still
edit
the
text
within
the
table
because
prospector.
A
Tools
for
editing
text,
so
that's
more
or
less
the
idea.
Another
example
would
be,
for
example,
the
the
summary
html
tag,
that
is
pro
that
is
supported
by
by
gfm,
like
we
are
displaying
a
some
content
that
is
hidden
in
a
in
a
collapsible
drop
down
like
we
are
gonna
display
that
in
the
content
editor.
A
B
B
A
What
do
we
do
with
that
html
without
link
like
how
do
we
treat
it
within
data?
I
think
that
for
links
is
a
simpler
answer,
because
because
we
can,
for
example,
allow
the
user
to
to
edit
the
text
during
the
link
the
user
can
edit
their
they
link
href
attribute
where,
in
the
case
of
dimension,
it
will
be
something
else
like
they.
They
shouldn't
be
able
to
do
that,
but
in
the
case,
in
the
case
of
of
attack,
like
summary,
like
what
do
we
do
like?
A
B
B
B
A
Yes,
I
I
completely
agree,
I
think
that
I
mean
it
is
technically
yeah
fiasco
to
do
that.
We
can
do
it
like
brush
different,
provides
first,
for
example,
in
the
case
of
the
of
the
summary
tag
of
the
or
you
know
of
the
details,
tag
we
can
tell
transmitter
to
identify
the
tag
and
convert
it
into
a
specific
node
type,
and
then,
in
that
node
type
we
can
specify
that
is
read.
A
B
I'm
not
sure
if
we
can
do
that,
but
in
the
end,
like
the
eventual
end
goal,
is
to
support
all
of
these
tags
right.
So
maybe
we
can
start
off
with
making
these
placeholder,
like
it's
kind
of
like
scaffolding,
where
you
define
all
of
these
mock
types
that
gitlab
flavored
markdown
should
support
and
they
just
they
are
just
read
only
and
empty
right
now
and
later
on.
We
go
and
add
the
implementation.
A
Right
like
like
that's
the
the
most
basic
construct
that
we
are
dealing
with
most
of
the
time
in
the
case
of
the
memory,
diagram
is
not
the
case,
but
perhaps
we
can
say
that
if,
if
we,
for
example,
don't
support
adding
new
columns
to
a
table,
the
user
can
still
edit
the
con
the
text
putting
that
within
the
table.
So
they
are,
they
don't
have
to
be
like
fully
freed
only
like
we.
B
Them
to
edit
the
text
within
the
so
there
are
two
things
that
you're
talking
about:
one
is
gitlab
flavored
markdown,
and
so
this
is
something
that
get
lab,
extends
on
top
of
markdown
already
and
now
you're
also
talking
about
tables
which
is
already
there
in
markdown.
It's
not
something
that
so.
I
think
we
can
treat
both
of
those
things
separately.
B
A
B
B
A
B
A
A
That
is
already
you
know.
In
existing
wiki
pages,
we
have
to
support
at
least
like
displaying
and
editing
those
type
of
content.
Tiptup
artwork
provides
notes
for
for
those
type
of
content.
So
I
think
that
we
can.
We
can
actually
do
that.
The
only
thing
that
we
have
to
do
is
to
implement
support
for
con
converting
those
notes
back
to
marker.
B
A
A
Yes,
I
guess
like
that
we
could.
We
could
start
like
with
marks
like
both
italics
and
strikethrough
etc,
and
then
we
can
continue
with
more
advanced
type
of
content,
but
that's
still
like,
like
that,
it's
clear
how
we
we
have
to
progress
in
the
implementation
of
the
ether.
But
what
is
not
clear
to
me
is:
what
is
the
scope
of
the
nbc
like
you
know,
we
can
continue
iterating,
but
where
do
we
got?
B
Yeah
with
mvc,
I
think
it
would
be
something
like
we
can
display
stuff
and
just
a
few
tags
are
working.
I
think
that
should
be
good
enough
for
mvc,
because
the
m
in
mbc
stands
for
medium,
so
I
think
we
definitely
do
not
want
to
support
everything
gives
us
in
the
embassy,
but
we
still
need
to
figure
out
how
much
what
exactly
we
want
to
support.
A
Cool
well,
I'm
gonna
probably
try
to
refine
these
questions
and
make
them
more
make
them
clearer
and
and
they
ain't
gonna,
I'm
gonna
slack
or
I'm
gonna
ask
eric.
If
we
have
an
issue
where
we
can
discuss
this
asynchronously,
perhaps
we
can
even
meet
later
in
the
week
to
keep
talking
about
it,
okay,
cool
so
yeah,
that's
a
that
will
be
everything
on
my
part
regarding
the
the
concentrator
okay.
B
Yeah,
so
for
view
migration,
I
still
like
I
didn't
get
a
chance
to
like
work
further
on
it,
but
I
wish
I
did
make
some
progress
here
and
like
it's
just
complete
and
it
works
for
the
most
part
still
need
to
like
cover
a
lot
of
tests
and
everything
is.
It
was
quite
a
big
issue,
but
yeah
it
should
be
good
once
it's
converted,
it
should
be
a
good
thing.
B
Like
initialize
it
we
need
to
be
sure
of
what
the
order
of
execution
is
like
the
gitlab
form.
This
form
needs
to
be
rendered
first
and
after
that
you
need
to
render
the
error
and
all
those
things
yeah,
and
it's
also
quite
a
bit
of
messy
code,
because
the
errors
appear
on
other
pages.
Also,
so
for
those
pages
you
need
to
initialize
it
beforehand,
whereas
it's
pretty
and
we
cannot
really
initialize
it
two
times.
B
A
I
see
that
like
do
you
think
that
we
should
break
this,
mr
or
break
all
of
that
working
in
smaller,
blessed
quests,
because
I
see,
for
example,
that
the
wiki
forum
doesn't
have
specs
yet,
and
it
already
has
like
a
big
code,
difference
a
big
amount
of
of
changes
in
the
in
the
mr.
So
perhaps
we
can
we
kind
of
start
like
just
to
to
start
emerging
according
to
master
and
make
it
more
iterative.
A
Maybe
you
can
have
a
separate
message
request
where
you
can
merge
the
wiki
form
component
with
suspects,
and
in
that
way
we
know.
At
least
you
know
that,
like
the
form
implemented
in
this
working
and
then
we
can
create
some
another
nurse
request
for
the
cleanup
and
another
immerse
request
for
for
implementing
effort
handling.
B
It
will
be
okay,
yeah,
like
like
I'll,
try
it.
I
don't
think
it's
more
than
like
500
lines,
but
it
will
get
there,
but
I
think
it
should.
I
should
be
able
to
like
push
it
in
a
single
merge
request.
I
know
it's
not
ideal,
but
it's
it's.
I
have
seen
many
much
differences
that
do
migration
sort
of
thing
like
this
and
and
it's
it's
usually
faster
to
get
it
done
in
a
single
mushroom.
B
B
A
Cool
yeah-
I
I
I
saw
now
it's
just
a
matter
of
getting
this
over
at
that
review.
That's
I
feel
like
that.
The
delivering
search
is
also
a
bit
risky
because
I
don't
know
it's
like
we
are
at
the
end
of
the
milestone
and
contributes,
are
not
like
going
very
fast
at
this
time,
but
let's
try
to
actually
do
as
much
as
possible,
also
together
to
get
it
over
the
line.