►
Description
Issue link: https://gitlab.com/gitlab-org/incubation-engineering/jamstack/meta/-/issues/41
A
Hi
everyone
welcome
back
to
the
jumpstack
incubation
engineering
update
so
great
to
have
you
back
just
a
quick
note
on
the
format.
I've
now
returned
to
doing
these
pre-recorded
updates,
as
opposed
to
live
meetings
mostly
because
I
can
be
much
more
concise
here
still,
I
did
appreciate
the
feedback
I
was
able
to
get
during
these
live
meetings,
so
I
think
this
will
still
be
a
similar
format,
but
it's
going
to
be
less
frequent
and
yet
I
think
these
weekly
updates
here
just
are
in
place
for
this.
A
A
A
The
first
time
I
visit
this
page
I'll,
be
not
just
presented
with
an
empty
state.
Gitlab
knows
that
I
haven't
set
up
pages
for
this
project
before
so.
Let's
see
this
guide
on
how
to
do
it
straight
away.
It
was
super
important
for
me
to
make
this
look
as
easy
as
possible.
I'm
guiding
the
user
through
the
complex
setup
of
building
that
yamaha
file
step
by
step.
A
Now
the
last
step
is
to
commit
this
new
gitlab
crm.
Here's
where
put
in
most
of
my
work
these
last
couple
of
weeks,
because
when
I
hit
this
commit
button,
it
doesn't
mean
my
page
is
immediately
live.
First,
there
are
two
jobs
that
need
to
be
completed:
one
the
page's
job
that
builds
the
html
pages
of
my
app
and
second,
a
somewhat
hidden
job
added
by
gitlab
when
it's
when
it
sees
a
job
named
pages
that
one
will
take
those
build
files
and
put
them
where
the
gitlab
pages
server
can
deliver
them.
A
A
Here's
a
page
that
says
yes,
you're
done
configuring
pages
now
we're
waiting
on
something
else
to
happen
with
a
nice
little
link
to
the
pipelines
where
the
user
can
monitor
the
status,
and
here
we
have
the
opportunity
to
start
the
on
boarding
over.
So
if
we
made
a
mistake,
we
can
generate
a
completely
new
gitlab
ci
jumble
again
in
the
future.
I
can
imagine
that
can
give
the
user
some
pages
settings
that
don't
depend
on
pages
being
actually
deployed
here,
so
they
can
start
configuring
without
waiting
on
the
initial
deployment
to
succeed.
A
A
This
way
we
can
gather
feedback
before
rolling
it
out
to
a
wider
audience,
see
if
there's
something
we
missed
and
at
the
same
time
we
can
use
this
partial
rollout
to
measure
the
effect
on
gitlab
pages
usage
right.
This
was
all
for
today's
update
as
usual.
If
you
have
some
direct
feedback,
there's
the
issue
link
below
it's
open
for
anyone
to
comment
until
then.
I
hope
to
see
you
again
next
week
and
enjoy
your
day
bye.