►
From YouTube: GitLab 13.7 Kickoff - Create:Editor
Description
Overview of the Create:Editor group's key efforts planned for the GitLab 13.7 release.
Visit our planning issue for more details and to leave feedback: https://gitlab.com/gitlab-org/create-stage/-/issues/12771
A
Hi
this
is
eric
schurter,
I'm
the
product
manager
for
the
newly
aligned
editor
group,
which
is
part
of
the
create
stage
of
the
devops
lifecycle
here
at
gitlab.
This
group
is
being
formed
by
combining
the
former
static
site,
editor
group
and
the
existing
editor
group
into
a
single
group.
That's
focused
on
all
of
the
editing
experiences
across
gitlab,
so
the
group's
in
a
bit
of
a
transition
phase.
A
While
we
wrap
up
some
of
the
work
in
progress
before
the
realignment
13.7
is
going
to
focus
mostly
on
that
as
but
as
we
move
forward,
we're
going
to
be
working
to
more
clearly
define
a
cohesive
strategy
for
the
editing
experience
both
of
code
like
in
the
web
ide
and
snippets
and
single
file
editor
and
of
pros,
whether
that's
in
the
wiki
or
static
site,
editor,
even
in
merge,
request
and
issue
description
boxes.
So
we're
really
excited
about
that
and
more
of
more
on
that
in
the
coming
milestones.
A
But
for
now
I
want
to
highlight
a
few
things
related
to
13.7
I've
linked
our
planning
issue.
In
the
video
description.
It
has
a
link
to
our
release
board,
so
you
can
see
all
of
the
issues
we
intend
to
tackle
this
release,
but
I
want
to
highlight
just
a
category
by
category
a
few
things.
The
web
id
is
not
our
primary
focus
for
this
release,
but
we
do
have
a
few
bug
fixes
and
ux
improvements
on
on
our
planning
board.
We
want
to
just
make
sure
that
we're
we're
focused
on
cleaning
those
up.
A
Similarly,
there's
a
a
few
ux
issues
and
and
bug
fixes
related
to
the
multiple
file
snippet
work,
some
follow-on
work
that
we
want
to
wrap
up
related
to
that,
and
also
with
snippets
we're
going
to
implement
recaptcha
to
improve
security
and
spam
protection
as
part
of
the
view
refactor
and
and
make
sure
that's
nice
and
secure
for
everyone
and
moving
on
to
static
site
editor.
As
a
category,
we
will
continue
to
work
on
the
proposed
static
site,
editor
re-architecture,
albeit
under
a
new
lens.
A
We'll
also
be
working
on
limiting
the
formatting
changes
when
editing
using
the
static
site.
Editor
specifically,
the
gitlab
handbook
has
very
large
pages
that
have
mixed
formats
of
markdown
and
when
you
edit,
those
with
the
wysiwyg
editor.
You
end
up
with
a
lot
of
lines
of
code
that
have
changed
just
for
simple
formatting
consistency.
We.
A
What
we
want
to
do
is
our
mvc,
for
this
is
really
just
to
split
those
formatting
changes
into
a
single
commit
when
the
when
the
static
site
editor
is
loaded,
we'll
commit
those
changes
if
they're
necessary
and
then
any
intentional
changes
that
the
user
makes
we'll
we'll
put
in
a
second
commit
on
that
merge
request.
So
when
sharing
the
merge
requests,
you
can
isolate
the
intentional
changes
from
the
formatting
and
and
hopefully
make
it
a
little
easier
to
get
feedback
on
your
changes.
A
A
Similarly,
we've
been
working
on
some
some
work
for
the
wiki
to
to
bring
the
design
into
a
more
consistent
experience,
with
the
editing
issues
and
and
mrs
page,
so
the
design
language
is
a
little
outdated.
On
that
page,
we've
been
working
to
bring
it
up
to
the
current
standards
and
and
so
we'll
wrap
up
that
work
in
this
milestone.
A
Gitlab
docs,
the
documentation
website
is,
is
another
area
of
focus
for
us,
and
we've
been
working
over
the
past
couple
milestones
to
implement
some
some
changes
that
allow
it
to
work
offline.
So
there's
instances
of
gitlab
installed
where
there
might
not
be
an
internet
connection
or
the
the
connection
is,
is
blocked
for
external
urls,
so
they
can't
load
the
gitlab
docs.
A
We
want
to
include
those
in
omnibus,
but
the
the
size
of
the
the
generated
documentation
was
four
to
six
hundred
megabytes
and
some
some
really
great
work
that
we
did
in
thirteen.
Six
got
that
package
size
down
to
about
18
megabytes,
which
is
plenty
small
enough
to
include
an
omnibus,
and
so
we're
going
to
be
working
on
on
landing
that
in
13.7.
A
Our
hope
is
that,
as
we
get
a
couple
of
these
under
our
belt,
we'll
be
able
to
move
a
little
bit
faster
and
then
have
a
repeatable
pattern
for
the
rest
of
those
that
aren't
behaving
consistently
with
with
everything
else
also
related
to
settings.
One
of
the
larger
initiatives
we
want
to
do
is
is
to
bring
the
ability
to
search
within
settings
views.
So
if
you're
in
your
project,
settings
and
you're
not
quite
sure
which
sub
menu
your
feature,
your
settings
is
contained,
you
can
just
search
for
it.
A
We're
still
doing
some
design
and
solution
validation
here,
but
in
137
we'll
be
doing
some
technical
discovery
as
well,
alongside
that
to
make
sure
that
we're
ready
to
go
when
when
the
design
is
approved
and
with
that
that's
what
we
have
planned
for
13.7
again
take
a
look
at
our
planning
release
board
and
feel
free
to
leave
comments,
questions
feedback
in
the
issues
themselves,
and
I
will
look
forward
to
doing
this
again
for
13.8.
Thank
you.