►
From YouTube: GitLab 15.2 Kickoff - Create:Editor
Description
Planning issue: https://gitlab.com/gitlab-com/create-stage/editor/-/issues/80
A
Hi
everyone,
my
name,
is
eric
schurter
and
I'm
the
product
manager
for
the
editor
group
here
at
gitlab,
and
I'm
excited
to
share
a
little
bit
about
what
we
have
planned
for.
The
15.2
milestone,
as
always
I'll
link
to
our
planning
issue
in
the
video
description,
and
you
can
click
through
and
see
our
milestone
board
and
follow
along
all
the
issues
that
we're
working
on.
A
But
I'll
highlight
a
few
for
you
today,
starting
with
pages
and
one
of
our
larger
efforts
as
we've
taken
over
the
pages
category
is
to
improve
the
performance
and
reliability
of
the
page's
service
and
we've
identified
an
approach
after
a
research
spike
in
1501
for
caching,
the
internal
api
endpoints
and
those
events
will
each
get
cash
independently
and
we
are
working
on
iterating
through
those
in
15
2..
It
will
likely
take
us
into
15
3
and
be
behind
a
feature
flag,
so
we
can
measure
the
impact
and
make
sure
there's
no
unintended
consequences.
A
A
Moving
over
to
the
content
editor.
I
just
wanted
to
highlight
a
couple
things.
First
off
this,
this
animated
gif
here
has
an
example
of
what
we've
been
working
on
for
the
past
two
or
three
milestones,
which
is
the
preservation
of
unchanged
markdown.
So
you
can
see
as
it
loops
around
that
I'm
working
in
raw
markdown
and
I
have
a
task
list
defined
in
three
different
markdown
syntaxes
and
as
I
change
and
edit
each
one
independently
and
then
save
the
page
and
switch
back
to
the
source.
A
The
preference
for
the
syntax
is
preserved,
switching
between
the
editors
or
after
saving
the
file,
and
this
is
huge
because,
as
we
move,
the
content
editor
into
more
visibly
version
controlled
scenarios
like
into
the
web
ide
or
in
any
context
where
you
might
view
the
diff
of
a
page.
You
will
appreciate
the
lack
of
reformatting
of
the
markdown
even
more,
because
your
diffs
will
be
a
lot
more
focused
on
the
the
content
that
has
actually
changed.
A
This
is
a
huge
step
and
something
that
we
have
been
working
really
hard
towards,
so
that
we
can
refine
the
the
content
editors
and
its
application
across
gitlab,
so
very
excited
about
that.
There
are
a
few
more
node
types
like
this
is
for
checklist
items,
and
this
was
actually
completed
in
15.1,
we'll
be
focused
on
a
handful
of
others
related
to
get
lab
flavored
markdown
in
15
2.
This
will
likely
carry
into
15
3
or
15
4
before
it's
turned
on
and
by
default
for
everyone.
A
A
A
So
we're
really
excited
about
that
effort
and
hopefully
have
some
some
progress
in
15
too,
but
the
majority
of
our
time
will
be
spent
continuing
to
work
through
the
replacing
of
the
web
id
e
with
vs
code,
and
this
I've
talked
about
a
couple
times
already,
but
we
are
taking
the
monaco
based
web
ide
and
replacing
it
with
the
vs
code
project
and
an
instance
that's
running
in
the
browser.
This
doesn't
require
any
infrastructure
on
gitlab's
behalf
or
on
your
behalf.