►
From YouTube: GitLab 13.1 Kickoff - Create:Static Site Editor
Description
13.1 Kickoff for the Static Site Editor group.
Planning issue referenced in the video: https://gitlab.com/gitlab-org/create-stage/-/issues/12676
A
Hi
everyone,
my
name-
is
Eric
shredder
and
I'm.
The
product
manager
for
the
static
site,
editor
group,
which
is
part
of
the
create
stage
of
the
DevOps
lifecycle
here
at
gate,
lab
I,
want
to
talk
to
you
a
little
bit
about
what
we
have
in
store
for
a
13.1
and,
as
you
can
see
from
our
planning
issue,
we
have
a
pretty
fully
loaded
month
ahead
of
us.
A
The
first
improvement
I
want
to
highlight
is
actually
a
bit
of
feedback
that
came
from
our
MVC
over
the
past
couple
releases,
and
that
is
that
in
the
editor
itself,
there's
a
button
on
the
bottom
of
the
screen
that
allows
you
to
return
to
the
website
that
you
came
from
and
this
action,
if
you
have
not
submitted
your
changes,
is
fairly
destructive.
So
we
want
to
make
sure
that
that's
a
very
intentional
action.
A
We're
gonna
make
that
a
two-step
confirmation
make
sure
that
you
understand
that
any
changes
that
you've
made
in
the
editor
that
have
not
already
been
saved
will
be
lost
if
you
navigate
away
from
the
site.
We're
gonna
be
working
on
improving
this
experience
and
using
local
browser
storage
and
things
like
that
to
ensure
that
no
data
gets
lost
even
in
the
event
of
a
browser
crash,
but
for
now
we're
just
going
to
make
sure
that
that
that
button
that
we
provided
is
a
very
intentional
action
now.
A
The
next
one
is
a
little
bit
bigger
and
the
the
static
site
editor
in
the
last
milestone
we
introduced.
What
you
see
is
what
you
get
rich
text:
WYSIWYG
editor,
but
one
of
the
challenges
there
is
that
there's
some
content
in
a
markdown
file.
That's
not
really
parsed
well
by
WYSIWYG
editor,
the
most
noticeable
type
of
content.
That's
almost
universally
included
in
all
markdown
pages
that,
like
are
part
of
a
static
site
generator
is
frontmatter.
So
that's
the
metadata
up
top
in
the
very
first
few
lines
of
the
markdown
file
that
lets
the
static
site.
A
Generator
know
things
like
the
title,
or
what
categories
or
tags
it's
a
fairly
loosely
structured
area
for
this
content,
but
when
you
apply
the
formatting
rules
in
the
WYSIWYG
editor
it
sort
of
takes
away
the
meaning
there.
So
what
we
would
like
to
do
is
just
strip
that
content
out
so
that
when
you're
in
the
WYSIWYG
editing
mode,
all
you
see
is
the
content
of
the
page,
and
so
what
that
would
look
like
if
I
switch
over
here
is
when
you're
in
the
WYSIWYG
editing
mode.
A
So
it's
important
to
note
that
we're
not
actually
removing
the
frontmatter
we're
just
hiding
it
from
the
WYSIWYG
editor.
Obviously,
as
you
save
changes
to
the
file,
we
want
to
keep
that
frontmatter
in
place,
so
that
I
can
continue
to
do
its
job
and
when
you're
static
site
generator
is
compiling
the
page.
A
The
next
issue,
I
want
to
talk
about,
is
somewhat
related,
but
this
extends
beyond
the
front
manner
and
into
markdown
pages
that
contain
non
markdown
content.
So
a
lot
of
times
this
means
embedded
HTML,
just
raw
HTML
tags
that
are
necessary
to
extend
the
layout
or
the
formatting
and
and
take
the
the
page
contents
beyond
what's
available
in
markdown
syntax.
A
But
sometimes
this
is
extensions
to
mark
down
like
diagrams
or
embedded
videos
or
iframes
and
you've
even
got
some
static
site
generators
that
allow
you
to
write
code
in
line
with
the
markdown
that
it
will
parse
allowing
you
to
iterate
over
data
files
or
pull
in
collections
and
things
of
that
nature.
So
bringing
that
into
the
what-you-see-is-what-you-get
editor
would
present
a
problem
because,
obviously
it's
not
marked
down
it's
not
gonna,
translate
well
into
a
visual
format
and
editing.
It
could
be
challenging
as
well.
A
So
what
we're
gonna
do
is
is
work
on
our
strategy
here,
where
we're
going
to
well
got
the
actual
contents
of
the
markdown
page
and
instead
of
just
blindly
presenting
them
in
the
WYSIWYG
editor
we're
going
to
parse
out
what
we
know.
We
can
format
and
what
we
can't
we're
going
to
encapsulate
and
make
sure
that
it's
clear
that
there's
content
on
the
page
but
just
make
it
so
that
you
can't
edit
it
as
we
iterate
on
this,
we'll
make
that
content
editable.
A
This
is
a
really
important
feature,
especially
as
we
look
towards
adding
the
static
site
editor
into
our
own,
get
lab
handbook
which
utilizes
images
in
various
ways
across
multiple
pages
being
able
to
represent
these
images
in
the
WYSIWYG
editor
and
upload.
New
images
is
critical
to
a
fully
featured
editing
experience.