►
From YouTube: GitLab 14.6 Kickoff - Create:Editor
Description
Overview of what's planned for the Create:Editor group in 14.6
Planning issue: https://gitlab.com/gitlab-com/create-stage/editor/-/issues/37
A
Hi
everyone,
my
name-
is
eric
schroeder
and
I'm
a
product
manager
for
the
editor
group,
which
is
part
of
the
create
stage
of
the
devops
lifecycle
here
at
git
lab
and
I'm
excited
to
share
a
little
bit
about
what
we
have
planned
for
the
14.6
milestone,
as
always
I'll
link
to
the
planning
issue
in
the
video
description.
So
you
can
click
through
to
our
release
board
and
see
all
the
issues
we
have
planned.
But
I'll
highlight
a
few
things
for
you
today.
A
There's
a
few
back
end
efforts
that
I
want
to
highlight
going
on,
and
the
first
is
that
our
backend
team
is
focused
on
overall
security
and
reliability,
not
just
on
the
editor
categories,
but
across
the
dev
section
and
git
lab
as
a
whole.
So
we'll
continue
focusing
on
those
areas
in
14,
6.
A
we've
also
been
working
and
collaborating
as
a
team
on
the
source,
editor
extension
architecture,
which
is
getting
some
improvements
and
building
a
great
foundation
for
for
future
feature
development
and
extension
development
there.
So
we'll
continue
to
work
on
that.
In
the
background,
the
other
thing
I
want
to
highlight
is
that
you'll
notice,
on
our
release
board
that
our
fantastic
designer
michael,
has
assigned
himself
a
bunch
of
ui
and
ux
polish
issues.
A
So
you'll
see
some
improvements
there,
specifically
in
the
web,
ide
and
wiki,
so
keep
an
eye
out
for
those,
but
the
other
two
things
I
want
to
highlight
are
related
to.
One
thing
is
related
to
some
feature,
work
that
we
worked
on
several
milestones
ago,
but
we'll
be
rolling
out
to
everyone
in
14.6
and
that's
the
consolidated
edit
button
right
now.
A
We
have
two
editing
options
or
three
in
this
case,
because
I
have
the
get
pod
integration
installed
or
configured,
but
the
web
id
and
the
single
file
editor
are
two
different
editing
experiences
and
they're,
two
different
editing
buttons
and
call
calls
to
action
on
the
on
the
file
view.
This
consolidated
button
lets
you
choose
which
editor
you
want
to
be
your
primary
call
to
action,
but
quickly
toggle
between
the
two.
So
I
can
click
through
here
in
the
web
ide
and
then
every
time
I
open
up
a
new
file.
That
is
the
editor.
A
A
It's
a
great
usability
improvement,
but
as
we
make
that
available
to
everybody,
we
expect
to
see
increased
usage
in
the
web
ide
and
just
a
little
more
streamlined
editing
experience
in
general
and
the
second
one
is
actually
something
I
highlighted
in
the
last
update
in
the
last
kickoff,
but
we'll
be
wrapping
it
up
in
this
14
6
release,
which
is
improving
the
experience
between
toggling
the
experience
toggling
between
the
raw
markdown
source
editor
in
the
wiki
and
the
new
wysiwyg
content
editor.
A
A
This
was
on
purpose,
but
we
no
longer
need
to
do
that.
So
we
are
working
on
streamlining
that
and
making
the
ability
to
toggle
back
and
forth
between
the
two
editors,
much
more
seamless
and
all
of
that
in
service
of
making
the
wysiwyg
editor
a
much
more
first-class
and
production-ready
editing
environment.
A
A
That's
it
for
today.
As
I
mentioned,
the
planning
issue
will
be
linked,
feel
free
to
ask
questions,
provide
feedback
and
and
engage
in
any
way
on
the
issues
linked
in
there
and
I'll
see
you
next
month.
Thanks.