►
From YouTube: Create:Static Site Editor — Direction overview
Description
A narrated overview of the current direction for the Static Site Editor feature within GitLab.
A
Hi,
my
name
is
Eric
sugar
and
I'm.
The
product
manager
for
the
static
site,
editor
group
here
at
get
lab
I
wanted
a
voiceover
a
bit
of
a
guided
tour
of
this
diagram.
I
created
as
I,
was
sketching
out
some
ideas
for
the
potential
direction.
Our
feature
could
take
and
sort
of
a
one
to
two
year
time
frame
and
to
highlight
a
few
potential
directions.
We
could
go
so
the
current
static
site
editor
right
now,
is
configured
to
work
with
a
static
site
that
passes
in
markdown
content
to
a
single
page
editor.
A
So
that's
where
we
are
right.
Now
we
have
a
WYSIWYG.
What
you
see
is
what
you
get
mode
we're
iterating
on
that
to
make
it
compatible
with
the
handbook
and
we're
working
on
making
sure
that
we
have
a
really
solid
single
page,
editing
experience.
We
have
a
pretty
clear
line
of
sight
into
iterations
in
that
editor
itself,
having
the
ability
to
edit
the
site
frontmatter
and
configure
the
page
behavior
a
little
bit.
A
We
also
have
a
pretty
good
sense
of
work
that
needs
to
be
done
to
handle
some
more
complex,
multi-page
workflows
and
we're
doing
some
UX
research
currently
to
validate
some
solutions
around
editing,
multiple
pages,
having
draft
workflows
where
you
can
return
to
pick
up
work
on
on
pages
that
you
may
have
edited
the
prior
day
or
or
weeks
before,
even
and
then
monitor
the
status
of
the
resulting
MRR
from
within
the
static
site.
Ender
experience,
so
you
don't
have
to
push
over
to
the
merge
result.
Page
a
little
further
down
the
line.
A
We
have
some
other
enhancements
that
we're
pretty
sure
we're
going
to
need
to
do
or
might
explore,
including
the
ability
to
have
more
of
a
block,
editor
or
page
builder
experience
within
the
editor
being
able
to
reorder
content,
insert
different
types
of
content.
Maybe
even
have
the
ability
to
create
custom
content,
block
types
like
an
image
carousel
or
something
along
those
lines,
and
then
a
really
fast,
real-time,
almost
real-time,
even
preview,
using
the
production
styles
would
be
another
thing
that
we
are
pretty
sure
we
need
to
do
from
there.
A
A
You'd
have
your
production
site
that
has
an
edit
link
somewhere,
whether
it's
visible
or
not.
We
would
handle
authentication
because
the
data
is
still
stored
in
the
get
web
repo,
so
anybody
with
access
to
the
data
would
would
be
able
to
make
edits,
and
then
we
would
sort
of
embed
our
editor
into
the
live
production
site.
There's
a
lot
of
hand
waving
going
on
there.
There
might
be
projects
static,
site
generators
that
are
architected
in
ways
that
would
prevent
this
from
working.
A
We
might
need
to
to
pave
a
path
with
just
a
few
approved
more
modern
JavaScript
static
site
editors
down
the
line.
We
might
also
introduce
the
ability
to
work
on
multiple
pages
within
this
sort
of
live
development
environment
on
the
production
server,
so
they
bility
to
navigate
between
multiple
pages
or
create
new
pages
preview.
Those
changes
in
a
draft
form
and
then
create
and
monitor,
merge
requests
from
that
experience.
A
Another
completely
unrelated
direction
would
be
to
take
the
editor
work.
We
have
and
tie
it
very
closely
with
the
web
IDE.
We
can
see
a
future
where
maybe
this
visual
editor
is
actually
just
something
where,
if
the
file
format
supports
it,
it's
a
it's
a
visual
editor
mode
within
the
web
IDE
for
lack
of
a
better
phrase,
but
we
could
have
it
either
side-by-side
as
an
explicit,
separate,
editor
or
maybe
a
mode
within
the
web
ID
itself,
and
then
all
it
would
take
to
integrate
with
your
product
is
linking
to
the
editor
from
your
site.
A
So
the
third
direction
is
somewhat
of
a
hybrid
or
headless
CMS,
and
if
we
imagine
that
coming
into
the
gate
lamp
product
for
the
sake
of
argument,
what
I've
done
is
just
sort
of
co-opted
the
concept
of
pages
here.
But
if
we
promoted
the
concept
of
pages
to
a
top-level
concept
within
the
the
left
sidebar,
you
could
imagine
an
experience
where
a
user
goes
and
creates
a
project
to
be
used
on
pages.
They
choose
what
it
would
generator,
what
static
site
generator.
They
want
to
work
with
whether
that's
Jekyll
or
Gatsby
or
middleman.
A
Maybe
we
have
a
few
that
we
can
install
for
you
or
you
can
choose
one
that
is
already
installed
in
the
project
and
then
we'd
offer
some
level
of
configuration.
We
would
map
the
data
and
the
template
syntax
and
the
frontmatter
that
we
identify
within
the
templates
and
choose
your
data
sources
and
all
that
stuff
within
the
get
lab
interface
and
then
probably
every
time
a
pipeline
builds
we'd,
be
able
to
extrapolate
information
about
what
pages
and
what
templates
and
what
data
and
even
what
assets
are
available.
A
So
we
could
build
a
lightweight
CMS
within
the
gate
lab
product
and
allow
people
to
navigate
across
their
published
pages,
maybe
create
pages
from
templates
fairly
easily,
and
then
embed
that
editor
experience
that
we've
been
working
on
since
a
few
months
ago,
right
within
the
git
lab
product
and
and
have
it
really
be
sort
of
a
pages,
editor
there's
a
lot
of
directions
we
could
take
moving
forward.
We
could
have
closer
ties
with
some
of
the
other
products
within
get
labs.
A
Other
features
within
get
lab
like
bringing
in
the
the
Monaco
editor,
so
edit
code
inline.
If
that's
necessary,
we
could
have
a
way
to
visualize
data
and
sort
of
like
a
table,
spreadsheet
kind
of
way
and
even
build
out
like
image
and
asset
libraries
based
on
what's
stored
in
the
in
the
project
or
or
even
connect
to
CBN's
and
then
and
then
further
out.
There's
a
lot
of
other
possibilities,
but
I
did
want
to
highlight
that
I,
don't
think
that
option
one
and
three
or
a
and
C
are
necessarily
mutually
exclusive.
A
A
So
the
long
term
vision
would
potentially
be
to
converge
some
of
these
concepts
together
and
offer
even
further
features
like
editorial
workflows
for
blogs,
versioning
of
Doc's,
using
sort
of
a
branch
system,
or
something
like
that,
so
that
you
can
support
documentation,
site
type,
workflows
and
then
potentially
down
the
road
like
live,
collaborative
editing
on
on
documents
and
pages.
So
there's
a
lot
of
possibilities
once
we
get
this
an
all
in
place.