►
Description
Update Issue: https://gitlab.com/gitlab-org/incubation-engineering/jamstack/meta/-/issues/17
All Weekly Updates: https://gitlab.com/gitlab-org/incubation-engineering/jamstack/meta/-/issues/5
A
A
A
A
It's
the
one
you
use
if
you
want
to
self
host
on
site
now,
follow
me
for
a
quick
thought
experiment
if
we
think
about
jamstack
applications,
let's
mentally
reduce
the
concept
to
front-ends.
For
now,
if
we
break
down
the
concept
of
the
scale
of
an
application,
there's
an
axis
of
pageviews
going
from
a
small
scale,
app
with
a
couple
of
hundred
to
large-scale
distributed
applications
with
millions
of
patreons.
A
A
A
A
A
A
One
I
want
to
improve
the
user
experience
around
gitlab
pages
pages.
Is
such
a
well-made
app
there's
been
so
much
thought
put
into
the
code
base
and
yet
the
front
end
is
currently
basic.
It's
hidden.
The
templates
are
old,
it
just
doesn't
look
like
it's
getting
a
lot
of
love
from
us
and,
let's
be
honest,
the
ui
is
the
first
thing.
The
users
make
their
judgment
on
whether
or
not
to
use
the
feature.
A
A
A
My
idea
would
be
to
pick
out
one
frame,
front-end
ssr
framework
and
figure
out
how
to
create
an
open
protocol
for
deployment
platform
and
framework
to
work
together.
I
was
eyeing
swelter
kit
for
this.
I
think
it's
an
ultra
promising
framework
still
in
an
early
stage
of
its
evolution,
but
seeing
how
excited
the
community
is
about
it.
I
think
it
may
be
an
incredibly
promising
potential
successor
to
next
year
four
serverless
functions.
A
A
A
A
A
In
any
case,
the
understanding
I
have
of
incubation
engineering
is
that
there's
a
loose
coupling
of
results
and
milestones.
If
I
see
an
opportunity
to
create
value,
that's
not
linked
to
an
area
specific
milestone.
I
will
still
pursue
that
path.
For
example,
the
pipeline
editor.
That
only
has
little
value
that's
specific
to
drumstick,
but
it's
super
useful
for
other
parts
of
the
organization.