►
From YouTube: Digital Experience Retro - Oct 20th, 2022
Description
Digital Experience Handbook page: https://about.gitlab.com/handbook/marketing/digital-experience/
A
B
B
I
took
advantage
of
updating
the
ux
on
those
templates,
so
I
unnecessarily
added
that
in
and
you
did
it,
SEO
updates,
and
you
know,
as
I
wrote
you
took
it
on
with
Grace
and
professionalism,
and
I
was
really
impressed
by
how
you
were
managed
to
update
those
create
those
three
pages
and
update
all
of
the
solutions.
Pages
Without
Really
any
complex
that
I
could
see.
So
thank
you
for
that
and
there's
a
plus
one
from
Justin.
C
Yeah
definitely
speak
for
filza
she's,
not
here
I
know
we
had
questions
on
both
burn
down,
charts
and
like
when
does
an
iteration
end,
because
we
have
our
release
on
Thursdays,
but
then
Friday's
the
end
of
the
week.
But
then
technically
it
seems
like
our
Sprint
ends
on
Sunday
so
like
which
one
is
it,
and
then
we
also
just
kind
of
have
questions
about
how
burn
down
charts
actually
work
in
like
yeah?
Is
it
the
moving
it
to
the
next
iteration?
D
E
Yeah,
especially
if
like
burn
down
charts,
are
getting
more
visibility
from
leadership
like
something
we
should
think
about
and
then
make
sure
that
we're
able
to
communicate
accordingly
like
one
way
or
the
other
I
think
historically,
even
though,
like
big
changes
didn't
usually
go
out
on
a
Friday
like
sometimes
people
are
closing,
like
the
small
issues
Friday,
but
if
people
are
pulling
right
now,
charts
early
Friday
or
even
in
a
day
Thursday,
it
looks
off
so
just
something
to
think
about.
That's.
A
I
brought
this
up
in
our
team's
Sprints
demo,
retro
that
we
had
demo
that,
like
you
know,
if
we
do
close
things
out
like
end
of
day
Thursday,
that
does
kind
of
leave
Friday.
As
a
like
a
question
mark
day
of
you,
don't
want
to
pick
up
extra
issues
and
leave
them
hanging
open,
but
you
also
don't
want
to
not
do
work,
so
you
know.
Are
we
creating
our
own
issues?
D
B
I've
worked
with
Chandler
on
the
security
and
compliance
lightning
strikes,
and
it
was
amazing
how
working
with
somebody
who
is
focused
on
content
can
really
move
a
project
along
and
make
everyone's
life
easier,
including
the
engineers
and
you
know,
javi's
been
working
on
the
AWS
project
and
has
finished
the
kubecon
project
and
the
all
the
content
is
coming
in
in
his
Mr.
There's
contact
changes,
lots
of
conversations
in
there
it's
pretty
messy
and
hard
to
follow
and
I'm
I'm.
B
Just
thinking
that
we
need
some
kind
of
process
change,
because
the
nature
of
events
are
just
like
that.
It's
not
the
events
team's
fault
in
any
way.
They
don't
really
know
what
speaker
is
going
to
speak
when
and
at
what
time
and
which
day
and
where
Logistics
are
always
changing
and
I
saw
your
note
Justin
about
revisiting
the
events
in
the
Box.
You
know:
we've
been
down
that
road
before
and
it's
it's
hard
to
get
the
events
team
to
use
it
a
template,
because
each
event
is
so
unique
from
one
another.
E
I
think
like
that
is
your
that's.
The
hardest
part
is
like:
if
we
do
something
like
this,
it
is
then
it
needs
to
be
communicated
up
to
like
here
is
the
templates
or
the
possible
components
that
can
be
used
on
the
page
with
here
are
the
style
options
that
can
be
adjusted
and
that's
generally
it
and
then
also
making
the
components
making
that
the
data
files
easy
enough.
I
know
Megan
try
to
do
this
with
a
commit
page.
We
had
that
rest
in
peace.
E
E
G
Yes,
my
this
is
a
weird
one,
because
technically
it's
something
that
went
well
because
it's
working,
but
it's
not
going
well.
The
404
Checker
got
added
like
a
couple
weeks
ago
and
I
just
noticed
we're
up
to
like
12
broken
links
again
so
I,
don't
know,
I
know
the
easiest
way
for
us
to
action
them
like.
G
Originally
it
was
blocking,
but
then
it
was
a
pain
in
the
butt
and
then
I
also
realized
that
if
any
of
those
sync
files
so
like
features
yaml
or
categories
yaml
have
a
broken
Link
in
them.
Then
we
have
to
go
to
double
dub
fix
it
and
it's
just
like
it's
a
big
hassle,
so
I
like
it
not
being
blocking
I,
just
don't
know
like
what
would
help
us
action.
The
broken
links
and
Justin
I
think
you're.
The
first
point
to
that.
E
E
A
Yeah
I
like
the
idea
of
it,
creating
an
issue
because
yeah,
it's
I,
see
the
exclamation
point.
I'm
like
I,
didn't
change
any
links
so
I.
You
know
ignore
it,
but
like
yeah,
I,
I'm,
never
kind
of
keen
on
going
in
and
fixing
those.
So
having
an
issue
that
yeah
becomes
one
of
the
Friday
Health
day
things
it
might
be,
might
be
worth
doing.
H
My
question
is:
like
I
mean
I've,
seen
those
errors,
but
I
guess
I,
don't
know
what
I'm
supposed
to
do
about
that
because
it's
I've
noticed
it's
like
external
sites
like
404ing.
So
it's
like
do
I
just
go
in
there
and
delete
the
link
and
then
there
could
be
like
a
chunk
of
content.
That's
missing
a
link.
Do
I
delete
the
entire
card
like
What's.
Do
we
tag
the
content
team?
What's
I
guess?
What's
the
expectation.
G
But
yeah
there's
some
like
there
was
one
the
other
day,
I
think
Laura
and
I
were
talking
through
that
we
had
to
remove
a
section
of
the
Enterprise
page,
because
we
had
like
one
of
the
stages
as
a
camera
what
it
was,
but
we
had
to
remove
that
because
that
link
doesn't
exist
anymore.
So
I
think
it's
just
Case
by
case
I
noticed
now
like
a
lot
of
them
are
due
to
support
pages.
G
E
E
G
A
I
had
one
thing
that
I
forgot
to
add
to
the
agenda,
just
to
note
that
our
new
Mr
template
is
live
where
you
have
probably
seen
it
if
you've
spun
up
an
MR
and
buyer
experience,
and
it
shows
labels
based
on
different
levels
of
approval.
So
level
one
is
like
a
typo.
Anyone
can
improve
emerge
level.
Two
is
someone
on
our
team
and
I've
put
a
note
that
just
goes
to
our
handbook
page.
That
shows
all
of
our
team
members.
A
So
if
you
start
getting
tagged
as
a
reviewer
on
random
things,
it's
intentional
and
it's
working
and
pleased
to
review
it
and
if
it,
if
you
see
it
as
something
that
is
like
more
of
a
big
change,
that
people
are
trying
to
sneak
in
and
feel
free
to
go
up
to
leadership
and
tag
them
for
review
or
whatever
use
your
best
discretion,
but
but
yeah.
If
you
start
getting
tagged
as
reviewers
on
things,
it
means
it's
working
and
I.
Think
we'll
make
some
improvements.
A
A
If
it's
a
big
change,
I
feel
like
I,
mean
we're
trying
to
put
Phil's
eyes
on
most
things
anyway,
but
I
mean
for
our
workflow.
I
did
make
a
note
of
this
somewhere
for
our
workflow.
Most
of
our
changes
have
been
approved
by
our
team.
Right
like
this
is
we're
not
just
coming
up
with
stuff
on
our
own
map
changes
just
because,
like
most
of
this
stuff
has
come
from,
you
know
the
design,
team
and
or
Justin
Lauren
Michael,
so
I
think
we're
pretty
safe
to
make
our
own
changes.