►
From YouTube: GitLab 15.7 Kickoff - Create:Editor
Description
Planning issue: https://gitlab.com/gitlab-com/create-stage/editor/-/issues/127
A
Hi
everyone,
my
name-
is
Eric
shurter
and
I'm.
The
product
manager
for
the
editor
group
here
at
gitlab
and
I'm
very
excited
to
share
with
you
what
is
turning
out
to
be
quite
an
important
15.7
milestone
for
us,
so
I
will
link
to
our
planning
issue.
As
always
in
the
video
description,
please
feel
free
to
click
through
and
view
all
the
issues
that
we
have
planned.
It's
quite
a
bit
of
great
work.
A
The
team's
going
to
be
doing
I
want
to
highlight
a
few
things
across
three
different
work
streams
here
for
you
today,
though,
first
starting
with
Pages
we've
been
focused
a
lot
on
behind
the
scenes.
Resiliency,
reliability,
performance
and
the
page
of
service
has
come
a
long
way
and
will
pass
four
to
six
months.
A
We
are
going
to
be
establishing
a
Syntax
for
that,
and
that
will
be
the
central
place
where
you
can
have
a
number
of
different
configuration
options
like
redirects
and
mime
types
and
namespace
configuration
now
the
and
we
see
here,
the
the
proof
of
concept
in
our
iteration
plan
towards
an
MVC
will
be
just
establishing
what
we
want,
that
that
configuration
file
to
look
like
and
how
the
syntax
will
be
handled
so
more
on
the
full
iteration
plan
in
the
coming
Milestone
or
two,
as
we
build
out
our
proof
of
concept
and
come
up
with
a
firm
Direction
here,
but
we're
very
excited
to
be
providing
that
functionality
in
the
near
future.
A
Next
I
want
to
talk
about
the
content
editor,
which
is
our
wysiwyg
markdown
editor.
Now
the
wiki
has
had
this
editor
in
place
for
quite
some
time
and
we
have
been
maturing
it
over
the
past
year
or
so.
If
you
are
a
gitlab
team
member,
you
may
have
seen
the
slack
message,
but
we
last
Milestone
turned
on
the
feature
flag
that
enabled
the
content
Editor
to
be
used
in
the
issue
and
epic
edit
views.
A
So
now
you
can
edit
your
issues
in
epics
with
a
wysiwyg
markdown
editor,
and
you
can
use
it
very
much
like
you.
Could
the
the
wiki
editor
now
the
feedback
we've
been
getting
has
been
really
helpful.
There's
a
few
performance
tweaks
that
we
already
are
in
the
process
of
merging,
but
one
of
the
big
things
that
we
want
to
address
is
how
the
the
content
editor
handles.
Markdown
comments,
which
we
use
liberally
in
our
issue
and
epic
templates,
and
it
right
now
will
just
completely
ignore
and
delete
comments
in
those
markdown
content
blocks.
A
Lastly,
and
potentially
the
most
impactful
one
that
we
are
working
on
right
now
is
our
remote
development
MVC,
which
is
on
track
to
be
delivered
by
the
end
of
15.7,
and
what
that
means
is.
We
will
have
a
brand
new
web
IDE
in
a
Beta
release,
that's
running
vs
code
and
it
is
fully
functional.
You
can
open
up
files,
make
edits,
commit
those
back
to
the
branch
and
have
an
end-to-end
editing
experience
in
vs
code
running
on
gitlab
and
from
there.
A
You
are
also
able
to
connect
to
a
remote
development
environment
directly
from
the
web.
Ide
that
you
have
a
that.
You
have
running
on
a
on
your
own
cloud,
sort
of
a
bring
your
own
remote
development
environment
situation
right.
So,
if
you
have
a
remote
server
running
vs
code
server
and
you
want
to
connect
to
it-
you
will
be
able
to.
A
A
On
this
kickoff,
video
I
will
show
exactly
what
this
looks
like
as
soon
as
I'm
able
to
demo
an
end-to-end
flow
and
get
my
GDK
running
again,
but
we're
very
excited
to
be
delivering
this
in
15
7
and
look
forward
to
the
feedback
that
we
get
from
our
public
Beta
release
of
the
web
IDE
so
keep
an
eye
out
for
that
and
I
will
see
you
next
month.
Thank
you.