►
From YouTube: Digital Experience Retro - Feb 23, 2023
Description
Digital Experience Handbook: https://about.gitlab.com/handbook/marketing/digital-experience/
A
B
Thanks
you're
so
good
at
that
intro.
This
is
why
you
have
to
do
it
all
the
time
yeah
after
two
years
of
complaining
about
content
being
a
blocker
and
we
need
more
content,
support
and
yada
yada.
It's
been
going
great.
This
quarter,
working
with
Chandler
and
Christina
Andrew
hickey's
team
they've
content
has
no
longer
been
a
blocker
for
my
project,
so
I
just
wanted
to
call
that
out
and
I
hope,
I
hope,
they're
watching
and
I
want
to
say
thanks
to
them.
Next
up
is
Miracle.
C
Oh
sorry,
I
wasn't
aware:
my
name
was
in
there
thanks.
Lauren
I'm
really
excited
because
there's
a
new
login
marketing,
cookie,
that
is
in
the
process
of
getting
merged
into
the
product
site,
so
we'll
be
able
to
see
if
users
are
logged
in
on
the
marketing
site
and
then
have
like
personalized
nav
stuff
going
on
Miguel.
D
E
Right
yeah
that
first
sort
of
like
they
were
props
a
miracle
but
yeah
made
her
congratulate
herself
on
that
one.
So
got
this
one
right,
just
props
to
Laura
we
cracked
the
door
open
in
personalizing,
our
navigation
for
Enterprise
and
SMB
users.
So
now
that's
going
back
to
our
product
designers
to
do
the
research
of
like
okay.
E
F
F
So
I
was
updating
a
page
and
you
know
kind
of
a
page.
We
don't
touch
too
often
and
I
was
just
thinking
about
like
okay,
like
I,
was
trying
to
get
a
header
to
look
like
something
else
on
a
different
part
of
the
site,
like
Solutions
header
in
particular,
actually
the
one
that
we
use
pretty
much
everywhere
on
the
site
and
I
got
in
that
process,
like
you
know,
trying
to
delete
old
code
and
then
adding
new
one
I
saw
like
pretty
much
like
how
complicated
some
of
the
you
know.
F
Dependency
chain
is
like
look
almost
can
be
so,
for
example,
like
copy
resources,
uses
solutions,
video
card
which
is
used
in
like
all
of
these
random
pages,
and
so
it's
like
I
guess
it's
interesting
because
it's
you
know,
I
think
a
product
of
moving
fast
makes
us
and
then
I
guess,
like
the
unintended
consequence
of
moving.
That
really
quickly
is
like
you
know.
F
If
we
change
something
on
that
part,
we
might
end
up
changing
parts
elsewhere
that
we
don't
know
of
or
don't
think
of,
checking
when
reviewing
that
Mars
and
it's
a
kind
of
a
hard
problem,
because
there's
not
really
an
easy
solution.
I
was
thinking
of
some
in
my
head
about,
like
you
know,
maybe
like
we
could
have
this
go
down
to
Common.
F
Maybe
we
can
have
like
perspective
component
full
folder,
slash
directories
for
each
group,
but
then
that
also
introduces
other
problems
so
kind
of
just
like
a
brain
dump
of
what's
going
on
and
then
like
kind
of
like
adjacent
point
like
I.
Just
did
like
find
how
many
View
files
are
in
the
components
directory
and
we
have
413
View
files
in
there,
which
is
like
a
lot.
G
Helps
to
counter
into
something
similar
I
think
it
I
tried
looking
for
it,
while
you're
talking
better
at
the
time,
I
think
it
was
like
a
carousel
or
something
and
I
saw
it
was
made
for
a
different
page
and
I
needed
like
the
exact
same
thing.
So
I
just
put
a
comment
in
that
component,
because
I
think
it's
under
like
a
page,
specific
folder
and
I
was
like
hi
I'm.
Also
using
this
on
this
page.
F
F
Keep
those
like
kind
of
like
Tech
debt
mitigation,
like
tasks
like
within
the
scope
of
the
issues
like
don't
make
it
its
own,
like
you
know,
Hercule
Hercules
Hercules,
like
Herculean
tasks,
to
like
try
to
fix
something.
That's
like
outside
of
the
scope
of
the
Mr,
because
I
think
that'll
just
really
slow
us
down
and
I.
Don't
think
that's
what
we
want
either
it's
just
like.
H
Can
we
do
like
we
have
right
now
on
Epic
for
the
health
of
the
project?
Maybe
we
do
not
have
time
to
make
it
a
generic
component
or
something
to
be
able
to
use
it
in
multiple
modules,
but
if
we
leave
a
track
or
an
issue
or
something
that
this
component,
that
is
under
solutions,
is
being
used
in
resources
and
features.
For
example,
we
can
leave
an
issue
saying
that
we
can
promote
this
component
to
the
common
folder
and
we
can
spend
some
time
doing
that.
D
E
Kind
of
carries
into
number
two
here
and
I
I
just
wanted
to
give
everyone
like
the
I,
can't
think
of
the
word
like
you're,
the
technology
experts.
You
work
with
the
repo
every
day
or
you
know
the
our
ux,
like
everyone
works
with
the
website
and
if
you
notice
something
on
one
of
our
tier
one,
Pages
like
pricing
or
the
home
page
or
a
nav
that
you're
like.
Oh,
that's,
bad
fix.
It
just
go
ahead
and
do
it.
You
know
and
I
trust.
E
Your
judgments
of,
like
you,
know,
use
the
the
rice
model
like
results.
There's
I
forget
what
the
I
is
but
effort
and
then,
like
the
influence,
the
scope,
that's
Something's,
Gonna
Have.
If
you
know
it's
going
to
reach
a
lot
of
people
and
it's
going
to
make
their
experience
better,
it's
going
to
be
high
value
then,
and
it's
only
going
to
take
like
10
minutes
to
fix,
go
ahead
and
do
it
example.
E
I
Thanks
yeah
I
think
we
talked
about
this
recently
about
kind
of
prefixing
issues
with
ends
or
content
or
ux
or
whatever,
but
are
we
still
using
the
labels?
I
think
we
should
be
just
for
filtering,
because
I
was
just
doing
some
backlog
trimming.
Sorry,
if
you
got
the
emails
but
yeah
a
lot
of
them
didn't
have
labels.
So
if
we
can,
maybe
just
try
and
I
don't
know,
can
we
set
up
automation
for
this
I,
don't
know
if
that's
even
possible
or
like
when
you're
creating
the
issue.