►
Description
Unfortunately I couldn't get it working and it wasn't obvious what was wrong, but hopefully this is still an interesting real user experience.
https://docs.gitlab.com/ee/user/project/static_site_editor/
https://docs.gitlab.com/ee/user/project/pages/
A
What's
going
on
the
product
record
for
CI
CD,
here
at
Gilliam
and
I
decided
to
record
a
quick
will
be
quick.
Speedrun
of
me,
setting
up
a
static
site
editor
for
moving
my
own
personal
reading.
I
would
I
have
a
readme
what
I'm
working
on
and
so
on,
to
get
live
handbook
today,
but
it's
a
little
heavy
weight
honestly
because
it
has
to
build
up
the
whole
site
every
single
time.
I
update
this
little
page.
A
That's
why
I
decided
to
do
was
move
it
over
into
my
own
core
better
than
what
we
direct
from
the
current
location
and
I
noticed
that
there
was
a
new
template
out
there
for
the
static
site
editor
using
little
man,
so
I'm
actually
going
to
record
myself
trying
to
get
that
working.
So
let
me
share
my
screen.
A
And
yeah,
so
the
only
thing
that
I've
done
so
far
is
this
created
the
project
which
I'll
show
you
how
I
did
so
I
just
click
the
new
project
up
here
I
went
to
create
from
template,
and
this
is
where
I
found
this
static
site
editor
middleman
project.
So
that's
the
template,
I
used
after
I
did
that
I
got
this.
This
project
created
here,
which
has
some
instructions
in
it.
So
it
looks
like
the
first
thing
I
need
to
do
is
edit.
A
The
data
config
Oh,
replace
the
user
name
and
project
name
so
commit
and
push
that
alright.
So,
let's
take
a
look,
this
file.
We
can
open
this
up
in
the
web
IDE,
which
is
what
I
prefer
using
and
I
love
the
new
dark
theme
by
the
way
and
that
data
configurable,
alright
so
easy.
So
this
would
be
J
an
Oscar
and
project
name
and
I.
Call
it
reading
easy,
so
configure
repository.
A
Master
I'm
like
here
and
so
posit
ory
visit
the
CI
CD
pipeline's
page
and
run
a
pipeline,
although
I
think
that
actually
will
automatically
happen
once
I
make
that
commit.
Yes,
it's
running
there,
so
maybe
those
couple
steps
aren't
needed
once
pipeline
is
finished.
I've
been
following
URL
on
your
browser.
Now,
maybe
a
few
minutes
before
yeah
that
happens,
but
maybe
in
the
meantime
we
can
play
with
the
static
site
editor.
We
can't
because
we
need
to
edit
up
this
page
but
okay.
A
So
from
the
moment
this
job
runs
until
the
page
is
live.
It's
actually
pretty
pretty
quickly,
I
think
so.
This
will
either
be.
What's
gonna
get
bad
slash,
don't
know
people
will
be
lowercase
or
uppercase
so
we'll
try.
It
definitely
isn't
done
yet,
so
neither
of
these
links
are
going
to
work.
This
needs
to
finish
so
it
looks
like
it's
grabbing.
A
The
build
environment
now
grabbing
the
the
ruby
gems
that
it
needs
to
to
build
for
middleman,
which
is
a
very
nice
static
site
editor
and
it's
the
one
that
we
used
for
the
give
up
handbook.
Actually,
so
it's
probably
a
little
heavy
weight
for
my
for
my
little
readme
file,
but
but
still
it'll
be
cool
to
play
with
something
if
you're
not
over
complicating
technology.
What
are
you
doing?
I
may
put
any
cut
here
just
to
let
this
finish,
but
it
finishes
in
the
next
couple
of
seconds.
A
A
Although
it's
perhaps
cache
between
the
two,
it
may
make
sense
someday
to
just
combine
these
into
one
build
the
place
step.
Maybe
the
purpose,
though,
is
so
that
if
this
fails
that
it
doesn't
proceed
to
a
deployment,
I
can
figure
out
B.
This
will
have
a
bunch
of
things
in
it
related
to
how
it's
so
short
comparison.
The
gitlab
website
actually
haven't
seen
what
the
default
version
of
this
looks
like
yeah
just
a
little
bit
of
configuration
here,
you
can
get
really
really
advanced
with
that.
A
The
gem
file
will
contain
the
dependencies
and
versions
that
are
needed.
Ruby
version,
a
very
special
version
they're
using
here
to
6/5
all
right
and
then
in
the
source.
Folder
is
where
actually
all
of
your
website
is,
so
they
get
it's
so
crazy
to
see
such
a
small
version
one
after
it
always
working
on
the
get
leg
website
about
Duquette
loved
are
common,
but
still
images
go
in
here.
Javascript's
go
in
here,
layouts
go
in
here,
and
then
style
sheets
can
go
in
here
and
there's
only
one
page
in
here.
A
The
index
that
HTML
by
md,
which
looks
like
it'll
just
have
a
little
bit
of
generic
stuff
in
it
I'm
so
I'm
excited
to
try
it
out.
The
this
source
folder
will
be
the
root
of
the
website.
So
if
you
are
using,
you
know
like,
if
you
want
to
access
one
of
your
images,
you
would
be
slash
images,
slash
and
then
dot
keep
it's
just
a
sample
file
just
to
make
sure
they
get
keeps
the
folder
around,
but
but
yeah.
Let's
see
how
this
thing
is
doing.
A
With
that
extra
unclick
Bowl,
maybe
that's
just
part
of
what
pages?
Doesn't
it's
not
familiar
reason?
So,
looking
at
this,
we
should
be
able
to
reload,
and
one
of
these
should
work,
maybe
not
quite
yet.
It
does
take
a
few
minutes
from
after
the
pipeline
finishes
the
first
time
to
when
things
are
actually
loaded
because
there's
a
background
processing
job
when
I'm
excited
to
see
what
what.
A
Yeah
in
the
meantime,
I
can
actually
go
grab
the
content
that
I'm
going
to
want
to
put
into
the
Reedy
page.
So
that
would
be
in
most
of
the
comm
projects
and
then
this
is
a
very
large
little
map.
Installation
tour
comparison
under
the
same
the
same
structure
is
there
so
in
their
source
and
then
I
think
it's
product
read
knees.
A
That's
where
this
thing
is:
oh
no
it'd
be
under
source
handbook,
because
this
is
where
our
handbook
lives,
then
it
would
be
under
product
and
now
I
think
it's
under
reading
yeah,
all
right,
and
so
here's
the
markdown
for
my
reading
I'm
just
going
to
look
at
the
source
of
this
and
I'll
have
that
available
when
I
start
working
on
the
editor.
Let's
see
if
this
is
done
yet.
A
Double-Check
the
data
that
we
configured
here.
This
was
the
path
to
the
repository,
not
the
path
to
the
website.
So
this
I
think
is
correct,
hello.
It
is
lowercase
here,
even
though
they
chose
uppercase.
Let's
see
if
this
girl
actually
works,
it
does
okay,
it
just
redirects
to
lowercase
eivol.
We
can
at
least
update
that
I'm
sure
it
traverses
the
the
redirect,
but
just
in
case.
A
A
A
A
A
A
A
A
Let
me
make
sure
I'm
not
missing
anything,
so
an
updated,
config
file
and
point
to
the
URL.
That
URL
does
seem
to
be
correct
because
it's
coming
back
written
question.
A
repository
visit,
the
CI
CD
pipelines
page
for
your
product
project
run
pipeline
once
it's
finished,
go
go
to
it
yeah,
so
good
or
page
confirmed
it's
working.
Click
the
edit.
This
page
button
use
the
static
site
editor
and
make
changes
the
content
and
save
the
changes
by
creating
a
merge
request,
emerging
or
quest
to
the
master
branch
man.
Well,.