►
From YouTube: GitLab 13.3 Kickoff - Create:Static Site Editor
Description
GitLab 13.3 kickoff for the Static Site Editor group.
Planning issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12712
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
and
I,
want
to
talk
to
you
today
about
what
we
have
planned
for
the
13.3
milestone.
It
was
very
much
a
continuation
of
the
work
we
were
doing
in
13.2
and
in
here
we're
really
focused
on
making
the
static
site
editor
solid
as
possible
in
an
effort
to
make
it
available
on
the
git
LEM
Handbook,
for
collaboration
across
the
team
and
for
everyone
to
contribute.
A
The
list
of
issues
we
have
on
our
plate
is
in
our
planning
issue,
which
I'll
link
in
the
video
description.
I
want
to
highlight
just
a
few
of
the
more
prominent
ones
and
again
we're
really
focused
on
getting
the
static
site
editor
available
within
the
git
lab
handbook,
and
our
approach
has
been
to
do
what
we
need
to
do
to
configure
the
project
to
use
the
static
site
editor,
which
is
complete
and
make
it
available
in
the
product
pages
of
the
handbook.
A
A
One
of
the
more
critical
and
impactful
changes
that
we're
looking
to
implement
is
limiting
the
number
of
changes
that
get
introduced
in
a
merge
request
by
simply
entering
the
WYSIWYG
mode
of
the
static
site
editor.
So
when
you
open
up
the
static
site
editor
in
order
to
present
the
WYSIWYG
mode,
we
need
to
do
a
round
trip
through
markdown
to
HTML
converter,
and
that
requires
a
very
consistent
markdown
syntax
and
when
it
writes
it
back
out,
it
uses
a
document
instead
of
preference
stylistic
preferences.
A
So,
for
example,
it
used
asterisks
instead
of
hyphens
for
unordered
lists,
or
it
doesn't
increment
or
does
increment
numeral
lists
and
ordered
lists
the
numerals
in
those
lists,
and
what
we
found
is
are
that
those
defaults
that
came
with
the
the
editor
or
were
not
consistent
with
the
get
lab
markdown
style
guide.
So
we
introduced
a
whole
bunch
of
extraneous
edits
into
the
file
and
the
merge
requests
were
rather
noisy
in
order
to
make
it
a
little
more
consistent.
A
This
will
require
a
little
bit
of
pre
formatting
and
some
of
these
initial
merge
requests
are
likely
to
involve
some
some
markdown
cleanup,
but
actually
the
the
cleanup
will
be
in
order
to
bring
it
up
to
standards,
rather
than
anything
necessary
to
make
it
work
with
the
editor
itself,
and
so
the
end
result
will
be
a
much
more
consistent,
markdown
style
in
our
code
base
and
something
that
will
work
very
well
with
the
static
site.
Editor.
A
A
This
is
an
extension
and
iteration
on
our
feature
where
we
display
images
in
the
WYSIWYG
editor,
you
can
add
an
image,
that's
hosted
elsewhere
already
using
a
URL
and
it'll
show
up
in
the
editor,
but
if
you
don't
have
an
image
hosted
on
a
CDN
or
within
your
project
already,
this
feature
will
allow
you
to
upload
from
your
desktop
right
into
the
static
site
editor
and
then
that
asset
will
be
included
in
the
merge
request
and
been
saved
in
your
project.
Most
of
the
work
is
done.
A
You
can
see
in
the
issue
there's
some
merge
requests
that
are
already
merged,
but
we
have
one
final,
merge
request
to
finish
up
and,
lastly,
in
in
order
to
enable
the
get
lab
handbook
to
be
efficiently
edited
and
people
to
work
really
well.
With
the
static
site
editor,
we
found
that
there
were
enough
pages
that
used
YouTube
videos
in
the
content
that
we
wanted
to
create
a
feature
in
the
toolbar
to
quickly
embed.
A
A
video
is
as
possible
by
switching
over
to
the
markdown
view,
the
source
code
and
writing
an
HTML
figure
tag
and
including
the
iframe,
but
we're
looking
to
introduce
a
toolbar
item
that
would
pre
format
it
for
you.
Basically,
and
this
would
allow
people
creating
content
in
the
static
site,
editor
WYSIWYG
mode
to
quickly
drop
a
youtube
link
into
a
modal
and
have
a
correctly
formatted
iframe
using
the
right
player
and
the
right
settings
for
for
fullscreen
and
and
all
those
things
and.