►
From YouTube: GitLab 13.2 Kickoff - Create:Static Site Editor
Description
13.2 Kickoff video for the Static Site Editor group.
Planning issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12695
A
A
So
we're
very
excited
here,
there's
a
little
bit
of
work
to
be
done
then.
So
first
thing
we're
gonna
do
is
iterate
on
an
issue
that
we
were
working
on
in
13.1.
We
defined
an
architecture
and
started
work
on
this,
but
we're
gonna
bring
it
home
in
13.2
and
that's
the
ability
to
display
non
markdown
content
in
the
WYSIWYG
mode
of
the
static
site.
Editor
it's
easier
to
explain
than
it
is
to
read
so
I'll
show
you
what's
going
on
here
in
the
markdown
mode
of
the
static
site.
A
Editor
here,
I
have
some
cramdown
syntax,
which
is
an
extension
of
markdown.
That
allows
me
to
identify
the
the
preceding
paragraph
and
include
a
class,
so
this
class
would
be
applied
to
the
rendered
output.
Our
WYSIWYG
editor,
that
what
you
see
is
what
you
get
editor
has
no
idea
what
to
do
with
that,
because
it's
not
regular
markdown
syntax.
So
it
just
thinks
it's
text.
A
A
So
we're
going
to
be
working
through
that
and
bringing
that
across
the
finish
line
at
13.2
and
what
we'll
end
up
with
is
the
ability
to
in
the
WYSIWYG
editor
show
that
this
content
is
part
of
the
page,
but
it
just
won't
be
editable
it'll
be
kind
of
set
aside
and
and
greyed
out
in
a
box
so
that
you
know
what's
there
and
if
you
want
to
edit
it,
you
can
switch
back
into
the
raw
source
mode.
The
markdown
editor
view
here.
A
A
This
releases
to
configure
the
get
lab
handbook
to
use
a
static
site
editor,
as
I
mentioned,
there's
a
little
more
complexity
there
than
then
the
static
site
editor
is
is
currently
configured
to
support.
For
example,
a
lot
of
the
pages
have
the
extension,
dot,
HTML
and
DD
RB,
so
they
have
embedded
Ruby
code
or
at
least
have
the
ability
to
parse
embedded
Ruby
code.
A
This
is
a
convention
of
middleman
and
the
static
site
editor
currently
doesn't
support
those
types
of
pages
we'll
need
to
include
support
for
those
pages
so
that
we
can
edit
the
handbook
using
the
static
site
editor
once
we
do
that
and
configure
the
project,
we'll
be
adding
it
to
the
product
pages
in
a
more
visible
way.
So
when
you
go
to
get
lab
about,
Doug,
get
lab,
comm,
slash,
handbook,
slash
product
and
any
of
the
pages
underneath
that
directory,
we
will
be
surfacing
a
link
to
edit
the
content
in
the
static
site.
Editor.
A
The
reason
we're
not
making
it
available.
All
handbook
pages
is
because
we're
trying
to
roll
this
out
slowly
and
make
sure
all
the
pages
are
compatible
and
to
put
our
best
foot
forward.
We've
also
prioritized
a
few
UX
changes
to
the
static
site
editor
and
to
the
handbook.
A
few
of
them
are
here
in
this
epoch
and
they're
all
linked
in
our
planning
issue,
but
specifically,
we
just
want
to
make
sure
we
clean
up
some
of
the
styling
of
that
markdown
view.
Here
you
can
see
when
I
switch
to
markdown
we're
kind
of
incorrectly
styling.
A
We're
gonna
tweak
the
success
screen
once
you're
done
submitting
changes
to
make
it
a
little
more
clear.
What's
going
on
and
then
on
the
handbook
side,
we're
going
to
be
working
on
making
sure
that
there's
a
very
obvious
and
very
prominent
place
for
the
static
site
editor
to
live
for
the
action
to
launch
the
static
site
editor
and
along
with
some
other
UX
improvements
to
the
handbook
pages
themselves,
and
that's
it.
So.