►
From YouTube: GitLab 13.4 Kickoff - Create:Static Site Editor
Description
The Static Site Editor group's kickoff for the GitLab 13.4 release.
Planning issue can be found here: https://gitlab.com/gitlab-org/create-stage/-/issues/12727
A
Hi
everyone,
my
name,
is
eric
shorter
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
gitlab.
I
want
to
talk
to
you
today
a
little
bit
about
some
of
the
great
features
we
have
planned
for
the
13.4
release
and
I'll
link,
this
planning
issue
in
the
video
description.
A
So
you
can
learn
more
ask
questions,
provide
feedback
directly
in
the
issues,
but
I
want
to
highlight
a
few
and
I
want
to
start
with
front
matter
so
front
matter
is
json
or
more
often,
yaml
formatted
metadata,
that's
included
in
the
top
of
a
markdown
file
that
ends
up
being
the
data
source
for
the
static
site
generator.
So,
within
this
block
of
yaml,
you
can
define
any
kind
of
metadata
that
you
want
to
pass
into
the
page
template
when
the
the
page
is
getting
generated.
A
It's
it's
very
powerful
and
very
flexible,
but
it
also
was
a
was
a
challenge
when
it
came
to
loading.
The
content
into
our
wysiwyg
editor
in
the
static
site
editor.
So
when
we
tried
to
bring
that
the
content
into
the
wysiwyg
editor,
the
yaml
would
be
parsed
into
regular
html
text
and
we
had
the
option
to
just
display
that,
but
maybe
not
make
it
editable.
A
Basically,
a
simple
form:
that's
going
to
have
a
field
for
every
ammo
field
defined
in
that
file
and
you'll,
be
able
to
edit
things
like
the
title.
The
the
layout
template
or
anything
else
that's
been
defined
in
the
file
itself.
You'll
be
able
to
edit
that
just
like
a
form
field
and
click
update
and
that
would
get
saved
and
committed
just
like
your
markdown
content.
A
It
took
a
little
longer
for
us
to
wrap
up
work
on
our
custom,
renderers
for
the
static
site,
editor
handling,
non-markdown
content,
and
so
this
issue
is
getting
carried
over
to
13.4,
but
we
should
be
able
to
wrap
it
up
right
now.
All
that's
left
is
being
able
to
preview
the
resulting
image
in
the
wysiwyg
editor
after
you've
uploaded
it.
A
A
And
this
is
really
important
because
there's
a
lot
of
pages
in
the
gitlab
handbook
that
have
videos
embedded
and
this
workflow
will
allow
you
to
quickly
add
those
videos
into
your
content.
In
line
with
your
markdown
and
the
last
issue
I
want
to
talk
about,
which
is
something
I
don't
usually
talk
about
on
these
kickoff
videos,
because
it's
very
handbook
specific
but
there's
an
exciting
new
project
called
frontman.
A
It's
a
project
that
was
created
by
a
team
from
the
algolia
documentation
group,
so
they
were
also
using
middleman
as
their
static
site
generator
for
their
documentation
and
they
ran
into
some
performance
bottlenecks
very
similar
to
ones
that
we
have
run
into
at
that
scale.
When
we
have
over
a
thousand
pages
in
our
handbook-
and
we
are
running
into
long
build
times
and
in
other
bottlenecks
like
that,
frontman
was
designed
as
more
or
less
a
drop
in
replacement
for
middleman.
A
It's
also
a
ruby
based
static
site
generator,
but
it's
optimized
for
performance,
and
so
we've
been
doing
a
little
bit
of
research
on
this.
It's
an
early
open
source
release
and
we've
been
working
with
the
algolia
team
to
provide
some
feedback
and
get
more
information,
we're
going
to
take
a
stab
at
integrating
the
front
man
project
into
our
handbook
or
replacing
middleman
with
frontman
rather,
and
do
some
benchmarking
and
profiling
and
make
sure
that
everything's
running
fine,
it's
an
opportunity
for
us
to
drastically
improve
our
the
performance
of
our
our
build
times.
A
We
don't
have
a
real
good
sense
of
exactly
what
to
expect,
but
it's
possible.
We
see
up
to
500
or
more
improvement
in
build
time.
So
it's
something
we're
very
excited
to
investigate.
It
isn't
likely
to
wrap
up
in
13.4,
but
when
it's
ready,
we
should
see
on
the
development
side
and
both
with
local
development
and
our
pipeline
build
times
drop
pretty
significantly
so
very
excited
about
that,
and
there's
an
epic
and
related
issues
for
this
linkedin.
The
planning
issue.