►
From YouTube: Digital Experience Retro - June 15, 2023
Description
Digital Experience handbook: https://about.gitlab.com/handbook/marketing/digital-experience/
A
Hi
everyone
welcome
to
digital
experience.
This
is
our
iteration
retro.
Today
is
Thursday
June
15th
we'll
go
over
some
of
the
things
that
went
well
this
week
and
some
things
to
improve
on
first
up
for
things
that
went
well
is
Justin
he's
async,
so
I'll
read
for
him.
Four-Star
and
Gardner
releases
were
hectic
and
took
coordination
for
multiple
teams
to
get
everything
at
the
door.
Thank
you.
Mateo
Trevor,
Javi,
Nathan,
Tina,
Lauren,
yeah
I.
Think
I
got
everyone
there
and
Lauren,
plus
one
on
that
as
well.
B
Yeah,
just
really
great
job
team
that
that
came
in
on
Thursday
and
we
had
to
ship
it
at
a
specific
time
and
we
did
it
got
it
out
the
doors.
It
was
great
and
it's
a
big
deal.
We
created
a
new
category
of
Gartner
and
now
we
lead
it
and
we
we
get
to
feature
it
on
our
site,
so
it's
huge
gitlab's
been
working
for
that
for
10
years.
So
it's
a
big
big
deal
pass
back
to
you,
Laura.
A
C
Thanks,
sir
there's
there's
so
many
tag
names
in
there
I'm
getting
lost,
yeah
point
three:
the
SRA
team,
I,
don't
know
if
you
noticed
in
the
digital
experience,
team
slack
gonzola
and
their
team
has
been
pretty
much
migrating
us
from
fascinated
cloudflare
and
it's
been
going
extremely
fast
and
knock
on
wood
super.
Well.
So
a
huge!
Thank
you
actually
right
now.
All
of
our
review
apps
are
going
through
cloudflare.
So
just
some
positives
that
we're
going
to
get
out
of
this
is
like
no
more
limit.
C
We're
gonna
have
unlimited
redirects,
so
we're
not
gonna
have
to
do
that
like
every
two
months
go
in
and
have
to
delete
some
old
redirects
and
then
it's
gonna
be
the
same
redirects
file
in
review,
apps
and
prod.
So
there's
going
to
be
no
discrepancy
now
between
the
two
of
them.
So
we're
gonna
get
a
lot
of
good
stuff
out
of
this.
Unfortunately,
some
of
us
are
losing
our
admin
access
to
fastly.
So
it's
probably
a
good
thing,
which
means
we.
D
E
C
No
but
yeah
it's
going
extremely
well
just
for
some
transparency,
I
think
they're
gonna
leave
it
for
two
three
weeks,
just
to
make
sure
everything's
good
and
then
they're
gonna
flip
the
switch
to
prod
super
exciting.
That
also
means
all
that
redirects
code,
that
Ruby
scripts
and
www
are
gonna,
get
deleted,
but
yeah
lots
of
exciting
news.
That's
probably
why
I'm
reading
this
week,
Lauren
I
think
you
got
the
next
one
yeah.
B
B
B
You
know
two
versions
of
the
nav
that
we
had
to
keep
synced
to
make
sure
everything
was
working
and
you
really
handled
that
well
and
we
did
a
ton
of
nav
releases
so
you're
a
pro
now,
which
is
cool
and
then
third,
great
job
TMA,
you
just
slayed
through
all
of
those
human
content
translations
that
we
got
and
we
we
got
all
of
that
content
on
to
production
before
we
released
our
language
selector
yesterday.
So
that's
great
instead
of
people
looking
at
machine
translation,
which
is
good
but
not
perfect.
B
D
I
just
want
to
shout
out
Miguel
for
his
awesome
work
on
the
code,
suggestions,
animation,
really
bringing
it
to
life.
We
don't
get
to
do
a
ton
of
Animation
work,
so
it's
just
cool
to
see
it
kind
of
go
from
something
in
my
mind
to
Miguel
actually
like
implementing
it
and
making
it
real.
So
great
job,
I,
don't
know
teen
or
hobby
want
to
add
on,
or
else
it's
back
to
Barker.
B
All
right
back
to
me,
I
just
want
to
give
props
to
Megan
you
really,
you
really
dug
into
Marketo
and
their
email
templating
system
and
delivered
the
Marketo.
Intelligent,
nurture,
email,
template
and
funny
enough
I've
actually
been
getting
some
git
Lab
sales
emails.
Now,
like
the
the
nursery
Mills
on
my
personal
account
and
I,
am
so
excited
to
see
this
new
template
get
implemented.
A
Yeah
for
things
to
improve
on
Justin
has
the
first
point
here
as
well,
so
he
says
events
Pages
seem
to
still
cause
stress
and
take
up
a
lot
of
context.
Switching
by
constantly
updating
copy
times,
headshots
Etc.
We
need
to
make
sure
we
communicate
often
and
early
about
what
we're
missing
Bobby.
Do
you
want
to
have
your
sub
point
in
today?
Oh.
G
F
Oh
yeah
sure
well
listening
to
all
of
the
pain
points
and
friction
points.
I
was
thinking.
Maybe
we
can
just
create
an
issue
template
specifically
for
events
that
kind
of
outlines
must
haves,
one
of
which
is
being
a
single
source
of
Truth
document,
because
I've
been
hearing
that
engineers
and
designers
have
had
to
reference
several
documents
to
figure
out
nmrs
and
issues
and
to
figure
out
copy,
also
a
point,
maybe
a
single
Dri
from
their
team
just
to
make
sure
there
aren't
too
too
much.
B
Yeah
I
have
the
next
one.
This
one
caused
me
a
lot
of
stress:
consideration:
I
have
a
few
more
gray
hairs
things
kept
happening
that
broke
our
site
that
we
did
not
know
about
because
of
changes
in
the
www
repository
such
as
the
home
page
going
down,
and
then
also
our
blog
page,
black
home
was
broken.
B
A
I
think
I'll
just
say
it
I'll
say
it
again
out
loud
I
think
we
talked
about
it
every
retro
recently,
but
I
think
hopefully
implementing
the
staging
site.
That's
a
perfect!
You
know.
Carbon
copy
of
prod
is
going
to
help,
maybe
catch
some
of
these
issues,
because
right
now,
I
have
trouble,
trusting
our
review,
apps
and
they're
being
hosted
by
completely
different
service.
A
Now
so,
like
you
know,
we
might
even
see
more
discrepancies,
oh
yeah,
just
again,
I,
don't
know
that,
like
we've
had
a
lot
of
fires
this
week
here
this
Sprint
and
I,
don't
know
that
that
would
have
caught
all
of
them,
but
it
may
have
helped
us
catch
some
of
them
because
we
did
see
strange
Behavior
between
staging
and
prod.
At
least
when
I
was
working
on
the
blog
site.
I
saw
that.