►
From YouTube: GitLab 15.3 Kickoff - Create:Editor
Description
Overview of the work that the Create:Editor group has planned for 15.3.
Planning issue: https://gitlab.com/gitlab-com/create-stage/editor/-/issues/92
A
Hi
everyone-
this
is
eric
schroeder
and
I
am
the
product
manager
for
the
editor
group
and
I'm
here
once
again
to
share
with
you
what
we
have
planned
for
the
upcoming
milestone
this
time.
It's
the
15.3
milestone
and
I
will
link
the
planning
issue,
as
always
in
the
video
description.
So
you
can
see
all
the
issues
that
we
are
working
on
and
I
will
highlight
a
few
major
themes
for
you
today.
A
First
of
all,
we
have
something
a
little
bit
exciting
going
on
in
the
beginning
of
the
milestone,
we're
doing
an
internal
editor
team,
hackathon
focused
on
the
content,
editor
and
the
goal.
There
is
to
build
a
proof
of
concept
and
round
out
some
features
related
to
the
content,
editor
that
will
enable
it
to
be
used
in
the
issue.
Editor.
It's
not
something
that's
imminently
going
to
ship
widely,
but
it
is.
We
are
nearing
the
end
of
our
journey
to
complete
maturity
in
the
content.
Editor
as
we
understand
it.
A
The
life
cycle
of
the
wysiwyg
editor,
as
well
as
rounding
out
some
work
on
the
autocomplete
and
suggestion
ui,
and
that
will
enable
things
like
slash,
commands
and
auto
complete
of
issues,
references
and
at
mentions,
and
things
like
that
in
the
editor.
So
that's
a
lot
of
great
work
for
the
content.
Editor,
this
milestone
and
shifting
focus
over
to
the
web.
Ide
we're
continuing
our
effort
to
replace
the
current
web
ide
with
a
client
only
implementation
of
vs
code.
A
So
we
are
hopefully
wrapping
up
work
on
our
custom
source
control
model
that
will
handle
the
file
system
and
tracking
of
changes
across
files
and
putting
the
the
new
web
ide
behind
a
feature
flag
in
the
main
gitlab
project,
after
which
we
will
be
focused
on
building
out
a
custom
module
for
creating
commits
and
from
there
we'll
be
able
to
start
inviting
the
select
few
people
to
test
it
out
and
see
what
other
gaps
we
might
have
before
we
roll
it
out
in
a
more
widespread
fashion.
So
keep
your
eyes
peeled.
On
that
I
know.
A
In
conjunction
with
the
vs
code
web
ide,
we
are
beginning
to
investigate
some
technical
directions
for
our
remote
development.
Offering
the
remote
development
environments
would
enable
the
web
ide
to
be
a
little
more
of
a
complete
solution
for
development
and
the
the
details
of
the
remote
development
category
are
all
on
our
direction
page
and
this
milestone.
A
We
are
focused
on
investigating
the
bridge,
the
connection
between
the
web
ide
and
these
remote
development
environments
and
what
technical
approach
we'd
like
to
take
there
and
we'll
have
more
on
that
in
the
in
the
coming
weeks
as
we
wrap
up
our
initial
research
spikes
last,
I
want
to
focus
on
pages
pages,
has
an
ongoing
effort
to
implement
some
internal
api
caching
so
that
the
inevitable
spikes
in
traffic,
especially
on
some
of
our
more
frequently
visited
pages,
don't
bring
the
performance
and
reliability
of
pages
down
globally.
A
So
the
the
caching
effort
will
hopefully
be
wrapping
up
in
the
coming
milestone,
we'll
probably
keep
that
behind
a
feature:
flag,
roll
it
out
and
measure
the
effectiveness
before
shipping
it
defaulted
to
on
so
keep
an
eye
out
on
pages
and
hopefully
over
the
coming
milestone
or
two,
it
gets
a
little
more
reliable
and
a
lot
more
performant.