►
From YouTube: GitLab 14.8 Kickoff - Create:Editor
Description
Overview of what's planned for the Create:Editor group in 14.8
Planning issue: https://gitlab.com/gitlab-com/create-stage/editor/-/issues/45
A
Hi
everyone,
my
name-
is
eric
scherter
and
I'm
the
product
manager
for
the
editor
group
here
at
git
lab
and
I'm
excited
to
share
with
you
what
we
have
in
store
for
the
14.8
milestone
as
usual
I'll
link
to
our
planning
issue
in
the
video
description.
So
you
can
click
through
to
our
release
board
and
see
all
the
issues.
But
I
wanted
to
highlight
a
few
things
for
you
on
this
video
today,
starting
with
actually
something
we're
announcing
in
the
14.7
release
post.
A
But
we
are
deprecating,
the
static
site,
editor
feature
and
the
category
itself
will
be
removed
in
an
upcoming
milestone.
But
I
want
to
share
a
little
bit
about
why
and
and
what
we're
doing
in
the
next
couple
milestones
to
sort
of
replace
it.
So
the
static
site
editor
was
started
a
couple
years
ago,
as
a
category
meant
to
encourage
collaboration
on
markdown
content
within
git
lab
by
creating
a
much
more
visual
and
rich
editing
experience.
A
So
you
can
see
that
in
action
here
on
our
handbook,
you
can
click
open
in
static
site
editor
and
we've
got
a
wysiwyg
markdown
editor.
You
can
switch
between
the
raw
source
and
the
wysiwyg
sections
and
you
can
make
edits
inline
right,
so
this
was
a
very
valuable
tool,
but
it
had
some
limitations,
so
we
started
investigating
a
new
editing
component,
a
new
editor
wysiwyg
editor
for
the
static
site,
editor.
Ultimately,
over
the
course
of
that
investigation.
A
We
decided
it
fit
better
with
the
wiki
and
we
could
reach
more
people
with
our
initial
mvc
by
putting
it
in
the
wiki,
but
we
have
a
very
similar
experience
and
as
it's
matured
we've
we've
got
a
very
viable
wysiwyg
markdown
editor
that
actually
has
some
more
features
than
the
static
site.
Editor
ever
had
itself
as
we
looked
to
the
future.
A
What
we
have
figured
out,
though,
is
that,
because
we've
created
such
an
extensible
and
flexible
wysiwyg,
markdown
editing
component,
the
investment
to
have
a
separate
feature
for
editing,
markdown
content
on
a
static
site.
Wasn't
the
right
place
to
to
focus
instead,
what
we
want
to
do
is
bring
this
markdown
editing
experience
across
gitlab,
regardless
of
what
type
of
project
you're
working
on.
So
you
don't
have
to
have
a
middleman
static
site
generator
as
your
as
your
core
project.
A
We
so
in
14
8
we're
going
to
begin
investigation
on
the
technical
implementation
of
the
the
content
editor,
which
is
our
new
wysiwyg
markdown
experience
as
a
as
a
another
option
for
editing
arbitrary
markdown
files.
In
your
repository,
so
any
project
you
have
whether
it's
a
readme
doc
or
a
markdown
file
within
a
static
site
could
be
opened
up
and
edited
just
like
this
wiki
page
in
the
markdown
wysiwyg
environment,
where
you
can
toggle
between
the
source
and
the
more
rich
text
editing.
A
So
we
think
that,
with
this
approach,
we
will
solve
about
90
percent
of
the
same
problems
that
the
static
site
editor
was
solving,
but
for
a
much
much
much
much
wider
audience.
We're
very
excited
about
that
work,
we'll
be
continuing
that
over
the
next
couple,
milestones
and
you'll
hear
more
about
that
later.
A
On
the
topic
of
the
content
editor.
Another
thing
I
wanted
to
highlight
was
we're
always
focused
on
performance
and
reliability.
One
of
the
things
we've
got
to
figure
out
is
making
the
content
editor
load
a
little
faster
when
the
when
the
page
is
first
loaded.
A
So
we
want
to
reduce
the
bundle
size
specifically
on
the
syntax,
highlighting
library
and
potentially
asynchronously
loading
the
languages
that
that
are
highlighted
in
the
document,
so
we'll
be
working
on
that
in
14-8,
the
the
work
itself
might
carry
into
14-9,
but
we're
looking
to
make
sure
that,
as
the
content
editor
spreads
into
different
areas
of
of
gitlab,
it
is
performing
as
as
fast
as
possible.