►
From YouTube: Create:Static Site Editor MVC Overview
Description
Overview of the user journey that the Static Site Editor group is working toward for the GitLab 12.10 release.
Epic referenced in the video: https://gitlab.com/groups/gitlab-org/-/epics/2784
A
Hi
everyone,
my
name-
is
Eric
sugar
and
I'm.
The
product
manager
for
the
static
site,
editor
group
here
at
gate,
lab
and
I
just
wanted
to
walk
you
through
our
end
and
user
journey
that
we're
working
on
in
this
this
epoch.
This
feature
that
we're
building
our
first
contribution
to
the
git
lab
product,
which
is
the
ability
at
a
single
middleman
page
using
a
static
site.
A
Editor
we're
starting
really
small
and
I,
want
to
highlight
what
you
will
be
able
to
do
at
the
end
of
this
release,
but
also
a
few
things
that
we
are
looking
to
do
later.
So
to
do
that,
I'm
gonna
load
up
the
mock-ups
that
we
have,
and
we
can
imagine
that
you
have
a
site
that
has
been
created
using
middleman
as
your
static
site.
Generator
in
this
cases
is
our
git
lab
blog.
Any
project,
though
that's
created
using
our
new
project,
template
that
is
configured
with
the
static
site.
A
That's
set
up
to
send
markdown
content
to
the
static
site,
editor
clicking
that
edit
link
you'll
authenticate
with
git
lab
through
the
normal
methods,
if
you're
already
signed
in
you'll
bypass
this
step
and
be
brought
to
our
static
site
editor
so
we'll
load,
the
content,
we'll
take
a
look
at
the
the
production
page
and
we
will
make
the
connection
with
the
source
code
and
find
the
markdown
content
that
is
associated
with
that
page
and
loaded
into
the
static
site
editor.
If
there
is
no
content
found
or
there's
an
error,
we'll
have
a
view
there.
A
But
in
this
case
is
the
blog
post
it's
written
in
markdown,
so
we
can
load
that
into
it's
dioxide
editor
inside
the
editor
right
now
we're
keeping
it
really
small.
This
is
the
title
of
the
page,
a
link
back
to
the
production
site
and
then
all
the
markdown
content
in
one
big
block
of
text.
You
can
click
in
and
edit
that
text
once
you've
made
an
edit,
the
submit
changes.
Button
is
active
and
what
that's
going
to
do
is
behind-the-scenes.
A
It's
going
to
create
a
new
branch
automatically
create
a
commit
for
with
your
changes
and
then
generate
a
merge
request
on
your
behalf.
If
there's
any
errors
will
notify
you,
but
assuming
it's
successful
you'll
get
this
page
where
you
can
either
return
to
the
production
site
and
keep
working
or
you
can
go
to
the
merge
request
page
and
provide
additional
context,
tag,
reviewer
or
otherwise
tweak
the
messaging
there
on
the
merge
request
and
that's
it
for
now.
That's
what
we're
focused
on
delivery,
we're
looking
forward
to
our
next
iterations.
A
Where
will
we
bring
in
WYSIWYG
editing,
maybe
some
more
detail
around
branch
management
and
merge
request
details
when
you
need
to
do
submit
your
changes
as
well
as
committing
multiple
changes?
/
merge,
requests
on
multiple
files,
so
look
forward
to
sharing
more
about
that
as
we
launch
our
new
feature
in
git
lab.
Thank
you
very
much.