►
From YouTube: Digital Experience Iteration Recap - Feb 25 2021
Description
Iteration Recap/Release Video Doc: https://docs.google.com/document/d/1I9Th3Q-AakOkE_-pmNtEzwwMDSqYKF5Je2etGdPTovk/edit?usp=sharing
Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
B
Sure
so
I
released
the
devops
platform
topic
page
for
agency
day,
which
is
not
the
devops
topic
page.
So
we've
got
that
all
set
up.
I
push
out
a
an
error
fix
for
some
500
errors
that
happen
on
our
api
calls
in
our
build,
deploy
or
at
the
very
least.
If
it
doesn't
fix
them,
we
should
start
to
fail
faster.
B
So
in
the
past
there
were
basically
there's
a
caching
behavior
in
our
deployment
pipeline
where,
if
the
api
response
returned
to
500,
we
cached
an
empty
array
and
then
on
a
future
job.
After
that
caching
happened.
The
pipeline
would
break
because
it
was
trying
to
read
out
of
an
empty
array,
and
it
was
unclear
when
that
happened,
because
it
was
cached
from
a
prior
job.
B
So
now,
if
we
get
the
500
response,
it
just
fails
and
we
have
an
exponential
back
off
algorithm
set
up
too
so
that,
like
it's
less
likely
that
a
500
error
will
break
the
whole
job.
So
that
was
great
and
it
should
be
helping
our
deployment
pipeline
anecdotally.
It
seems
that
the
handbook
escalation
has
fewer
of
these
500
errors
in
it.
So
we're
feeling
good
there.
This
morning
I
helped
rebecca's
get
back
her
local
dev
server,
which
had
broken
sometime
in
the
last
couple
of
weeks.
Yep.
B
B
I
clicked
merge
and
did
some
troubleshooting
on
the
roll
up
to
webpack
migration.
So
we
now
just
have
one
bundler
in
the
entire
www
repo,
so
things
can
be
handled
uniformly
there,
which
has
been
a
blocker.
I
think
for
handbook
to
do
some
migration
work
that
they're
working
on
and
then
finally,
this
has
been
sort
of
the
biggest
ticket
item.
B
Is
I
created
an
mr
I've
put
it
back
in
draft
because
I
don't
actually
think
it's
yet
ready,
but
there's
an
mr
for
the
blog
template
that
tina
designed
in
slippers
and
javi.
I
have
a
show
link
underneath
nested
in
there.
If
you,
if
you
want
to
show
the
review
app
there,
you
go.
This
is
it
so.
This
link
here
is
the
review
app
for
this,
mr
and
as
you'll
see
it's.
B
I've
got
the
components,
and
I
think
next
steps
here
are
so
tina's
done
some
initial
review.
I
resolved
those
issue,
those
items
and
then
I
think
that
there's
still
some
engineering
review
I'd
like
to
do
in
terms
of
some
implementation
things
and
some
naming
have
javi
brought
up
a
good
question
about
categorization
of
these
components
and
like
where
they're
intended
to
go.
So
I've
marked
that
back
into
draft,
and
today
I
will
be
getting
to
the
other
part
of
this,
which
is
making
it
work
with
middleman.
B
So
I
think
we
are
a
little
I'm
a
little
off
track
in
terms
of
like
getting
that
like
actually
out
the
door,
but
I
am
on
track
for
having
it
like
complete
and
reviewable
and
I'll
be
talking
with
michael
or
whoever
else
needs
to
talk
about
that.
To
make
sure
we
don't
miss
anything
super
critical
on
it
and
see
what
I
can
do
to
pitch
in
on
it.
So
thank
you
up
next
is
lauren.
Is
she
on
the
call?
I
don't
think
so,
because
she's
absolutely.
C
Great
yeah
she's
out,
I
put
that
one
in
there,
knowing
that
she
had
done
that
work
kind
of
at
the
start
of
the
sprint
before
the
ceo
shadow,
and
I
just
thought
it
was.
You
know
worth
mentioning
because
in
particular
the
blog
category,
page
pagination,
is
something
they've
wanted
for
a
while
and
something
that
we
had
a
contractor
starting
work
on
that
wasn't
able
to
finish
and
it's
more
complicated
than
it
seems
because
of
the
way
middleman
works
and
collections
work
and
whatnot.
C
So
yeah
in
that
show
example
link
there's.
Basically
you
scroll
to
the
bottom
of
the
page,
and
you
know
you
can
see
that
there
are
pagination
numbers,
as
one
might
expect,
instead
of
a
really
long
list
to
scroll
through
so
better
for
performance
and
user
experience
and
all
that
kind
of
stuff
and
linkability
so
yeah.
That's
that
the
next
item
up
is,
I
have
a
couple
things
in
there.
One
of
them
is,
you
know,
just
a
quick
handbook
link
that
I
added
for
the
question
came
up
in
slack.
C
You
know
this
merged
request
is
taking
a
long
time
and
I
realized
you
know.
I
was
one
of
the
only
people
on
the
team
that
knew
about
the
merge
trains
and
that
there's
a
solution
out
there
to
fixing
them
if
they
get
stuck
or
even
that
they
get
stuck.
Sometimes
I
hadn't
communicated
that.
So
I
just
added
that
link
to
the
handbook.
C
I
know
it's
already
in
the
handbook
in
other
places,
but
I
figured
it
would
be
good
to
have
in
our
own
team
documentation
and
it's
rather
than
copy
pasting
from
this
issue,
how
to
do
it
into
the
handbook.
It
just
made
sense
to
link
to
that
issue
which
was
already
there
then
the
second
item
I
have
that
I
worked
on
this
sprint,
which
was
the
larger
item.
This
was
kind
of
a
you
know,
last
minute
time
box
sort
of
request.
C
You
know
they've
been
waiting
on
this
for
a
while,
so
we
created
a
template.
We
were
planning
to
use
our
localization
platform,
smart
link
for
this.
However,
the
tool
wasn't
in
a
state
where
we
could
use
it
within
the
you
know
expected
time
periods.
So
we
built
a
quick
template
at
middleman
using
some
of
the
design
system
work
we
have
done
and
thanks
to
tina
for
volunteering,
to
design.
C
This
really
quick
and
you
know,
obviously
still
put
a
lot
of
thought
into
it
and
I'm
happy
with
how
it
turned
out
and
everyone
else's
too.
You
know
they
weren't,
expecting
this
amount
of
design,
so
yeah
really
really
happy
that
we
were
able
to
get
that
out
and
that
the
foreign
language
support
worked
better
than
I
was
expecting
so
yeah
thanks
for
that
and
looks
like
next
is
tina.
I
don't
know
if
you
had
any
words
about
that
template
that
you
wanted
to
share,
but
yeah.
I
think
it
turned
out
well.
A
Yeah
so
yeah,
the
page
is
opening
up.
There
should
be
merged
in
shortly.
We
have
a
really
nice
kind
of
header
design
that
we
can
use.
This
is
kind
of
a
global
template
that
we
can
use
for
a
lot
of
these
pages,
which
is
really
great.
So
we
have
a
version
of
the
header
that
just
has
title
and
call
to
action
and
yeah.
We've
got
some
really
nice
graphics
in
here.
Some
split
layout
stuff
happening,
so
it
works
really
well,
there's
a
watch
and
learn
video
section
that
will
show
up
in
production.
A
E
D
Thanks
emmy,
so
I've
created
a
block
library.
If
you
can
show
the
slippers
file
javi.
That
would
be
great.
So
I
basically,
what
I've
done
is,
did
a
roundup
of
all
of
the
blocks
that
digital
experience
has
designed
since
our
existence,
all
the
ones
that
we
felt
are
usable
and
reusable,
because
slippers
and
storybook
is
still
a
work
in
progress.
This
is
really
just
for
right.
D
Now,
a
figma
application,
it's
a
place
where
content
creators,
designers
and
engineers
can
select
from
when
building
out
new
pages
and
we've
put
it
into
slippers
as
a
single
source
of
truth.
Instead
of
its
own
figma
file,
we
also
created,
I
also
created
a
google
doc.
I
didn't
create
this
google
doc.
D
D
As
you
all
know,
we
also
did
a
handoff
workshop
I'll
just
be
working
on
some
first
iteration
low
hanging
fruit
recommendations
that
we
addressed.
I
identified
some
common
problems
that
we
were
having
and
in
the
spirit
of
as
little
change
as
possible,
we'll
just
implement
a
few
very
simple
checklists
to
make
our
lives
easier
for
design
to
engineering
handoffs.
A
Yeah,
so
a
little
one
there
that
has
to
do
with
the
events
page.
The
events
page
look
wise,
has
not
changed,
but
under
the
hood
it's
operating
a
little
bit
differently
with
how
the
dates
are
being
sorted.
There
was
a
bug
where
dates
that
spanned
kind
of
across,
like
the
end
of
december
to
the
beginning
of
january,
that
were
two
different
years,
would
be
parsed.
In
correctly
it
wouldn't
show
up.
So
we
kind
of
refactored
how
events
are
shown,
which
was
my
first
time
writing
ruby
code.
A
Tyler
is
slowly
converting
me,
so
yeah
there's
really
not
much
to
see.
It
should
look
the
same
as
how
it's
always
looked.
It's
just
working
a
little
bit
more
efficiently
by
separating
start
date
and
end
date
for
an
event,
and
then
the
install
page
I
did
on
the
last
agency
day
got
merged
in
so
that
is
a
little
bit
updated
got
a
new
little
header.
A
The
new
card
designs
there
will
be
showing
as
soon
as
we
kind
of
hammer
those
out,
but
so
the
the
existing
existing
cards
are
still
there.
But
the
page
looks
a
little
bit
cleaner
and
has
our
slippers
design
elements
and
that
kind
of
automatically
updated
some
of
the
pages
that
it
links
to
which
is
great
and
then
lastly,
I've
been
doing
some
work
on
slippers.
A
The
grid
component
is
a
working,
mr,
so
I
didn't
link
that,
but
it's
getting
there
it's
just
a
little
bit
more
abstract,
but
the
I
linked
a
review
app
of
radio
buttons,
which
is
part
of
the
radio
and
check
box
item.
So
these
are
still
you
know
in
progress,
but
there's
you
can
click
and
hover
and
whatever,
and
they
will
be
there
kind
of
in
a
functional
state.
So
yeah.
So
that's
me
and
next
is
sunmi.
Yes,.
E
Migration,
migration,
migration.
So
during
this
the
last
part
of
this
sprint,
I
was
migrating
the
child
topics
on
our
netflix
siemens,
so
I
had
to
migrate
30
of
them
and
they
are
all
ready
for
much
request,
but
because
we
have
a
lot
of
work
on
brandon
and
lauren.
So
I
want
to
take
it
slow
and
steady
so
throughout
next
year,
they're
going
to
be
helping
me
to
submit
them
to
match
demand
requests
so
that
everything
can
go
live.
E
A
You
know
jj
if
you
can
open
the
figma
file
for
the
partners
overview
page,
that
is
a
design
we're
able
to
finally
get
closed
out.
It's
just
a
way
to
kind
of
we're.
Gonna
have
like
six
featured
partners.
Come
to
this
page.
You
can
see
who
they
are
kind
of
explains
how
our
partnerships
work
with
them.
And
then,
if
you
go
into
the
second
figma
file,
I've
linked
in
there,
that's
something
actually
stephen
who's,
not
on
the
call
helped
me
with,
and
it's
just
the
template
right
now.
A
You
can
click
on
that
and
basically
we're
using
this
company
optimal
workshop,
who
helps
with
the
tree
testing.
If
you
scroll
down
a
little
bit,
you
can
see
we've
like
asked
like
10
or
12
questions,
and
if
it's
green,
that
means
people
have
like
answered
them
correctly.
They've
gone
through
our
navigation
and
found
it
easily.
If
it's
red
or
orange,
then
it's
was
difficult
to
find
and
that
just
gives
us
some
insight
into
like.
C
F
F
D
F
Like
these
take
time,
I've
committed
myself
to
releasing
this
monday,
just
in
the
sake
of
their
own
timelines
and
also,
in
the
sake
of
like
what
they've
released,
but
also
just
like
taking
note
like
making
making
sites
off
up
the
ground
is
a
lot
of
work
so
get
that
out
there.
Something
really
simple
but
really
helpful
for
us,
was
just
getting
yarn
start
to
work
for
our
repo.
F
I
listed
in
the
issue
that
the
instance
of
storybook
was
just
like
hijacking
the
build
process,
so
that
like
it,
would
only
generate
the
updated
css
file
when
you
run
yarn
start,
but
never
after
that,
and
I
was
trying
to
find
like
the
issue
that
I'd
linked
somewhere
in
github,
where
they
talk
about,
why
it
does
that,
but
essentially
I
just
added
a
package
that
lets
us
figure
all
of
that
stuff.
Out
similarly
noted
now,
we
have
linting
for
slippers,
which
is
really
nice.
F
It
essentially
just
yells
at
us.
If
we're
spacing
our
things
really
weirdly,
that's
that's
about
it,
and
this
is
done
on
commit.
So
it's
not
so
much
as
like.
We
push
up
to
a
review
app
and
then
the
revamp
fails
because
of
a
limiting
issue.
It's
more
so
like
the
like
on
commit
kind
of
kind
of
situation,
which
is
really
interesting
shout
out
to
yo,
who
figured
that
out
for
us
and
kind
of
linked
us
in
a
in
a
route
of
another
team
that
does
it
that
way
buttons
I
have
somewhere
here.
F
I
listed
the
issue,
but
not
the
thing,
but
I'm
waving
my
my
hand
and
saying
I
added
more
states
to
the
button.
Essentially
what
we
have
is
on
a
mobile
break
point.
The
button
contain
is
contained
to
like
the
width
of
the
thing
of
the
container,
so
that's
step.
One
step
two
is
adding
the
underlying
links
to
make
sure
that
when
you
have
a
link
you
can
underline
it
now.
Instead
of
having
to
use
the
button
styles.
F
Quick
note
about
that,
I
made
it
a
separate
view
component,
but
it's
really
functioning
as
a
button
that
just
looks
differently,
so
I
wasn't
sure
whether
to
have
it
set
up
so
that
it's
essentially
a
button
but
is
looking
differently.
I
wasn't
really
sure
how
to
go
about
that.
I
figured
that's
not
a
big
deal.
We
can
iterate
on
that
further.
F
Finally,
finally,
finally
trying
to
get
slippers
to
function
with
about
gitlab
in
general,
there's
base
2020,
which
is
like
its
own
separate
environment,
but
there's
also
when
we're
not
using
base
2020.
What
does
these
styles
look
like
and
trying
to
make
sure
that,
when
we're
working
in
slippers,
that
output
actually
looks
like
what
it
should
on
about
gitlab?
F
F
I
believe
we
it
it
will
look
close
enough
and
there's
things
again
with
about
gitlab.
I
think
we
have
to
change
that
will
affect
other
pages,
and
so
I
think
we
have
to
figure
out
a
path
forward.
I
know
people
have
brought
up
like
normalization
having
a
normalization
process
that
happens
in
one
place,
that's
something
that
could
help
with
that,
but
it's
more
so
we
don't
know
what
we
don't
know
for
that
so
yeah,
I
think
that's
kind
of
that's
kind
of
it.
Does
anyone
else
have
any
closing
thoughts
on.
C
Stuff
thanks
everyone,
it's
been
a
good
sprint,
really
excited
to
see
all
the
progress
we've
been
making,
and
I
know
it
has
felt
slow
at
times,
but
you
know
over
the
past
many
months,
but
it's
building
to
a
place
that
we
can
use
and
get
these
design
system
pages
out
and
built
quickly
and
so
yeah.
Just
I
wanted
to
say
thanks
for
all
the
hard.