►
From YouTube: Digital Experience Retro: Feb 9 2023
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/digital-experience/
A
Hi
everyone
welcome
to
digital
experience.
This
is
our
iteration
retro
meeting
today
is
Thursday
February
9th
and
we'll
be
going
over
some
of
the
things
that
went
well
over
the
last
two
weeks
and
some
of
the
things
to
improve
on
I've
got
the
first
couple
points
here
so
a
bit
of
tough
news
this
morning,
but
otherwise
we
kicked
off
our
quarter
and
we
kicked
off
our
year
the
other
day
and
that
meeting
was
I.
Think
informative
and
I
appreciate
the
leadership
kind
of
making
it
fun.
A
We
had
some
new
kind
of
challenges
and-
and
you
know,
off-site
type
things
that
were
a
lot
of
fun.
I
also
for
sure
won.
The
scavenger
hunt
I
enjoyed
it
a
lot,
and
you
know
I'm
hoping
we
can
deliver
on
on
those
things
this
year
and
then
the
other
thing
is
amas,
which
we've
been
doing
for
like
a
year
now,
which
have
been
like
the
highlight
of
our
experience,
are
coming
to
an
end
like
I.
A
Think,
we've
got
a
couple
more
weeks
of
them
and
I'd
still
I'd
love
to
get
everyone's
opinions
on
keeping
that
time
blocked
and
either
starting
the
list
of
amas.
Again
or
you
know
just
doing,
team
games
or
stuff
like
Drop
in
casual
type
games
or
whatever,
but
yeah
so
maybe
thoughts
on
that
before
it
ends.
B
Yeah
I
just
wanted
to
give
a
shout
out
to
Miracle
for
brainstorming.
You
know
ways
that
we
could
recognize
a
logged
in
user
on
the
marketing
site.
There's
many
ways
we
could
do
it
and
kind
of
just
putting
some
some
thinking
around
that
and
then
coming
up
with
a
plan
of
attack
for
one
of
the
ways
which
we
might
do
that.
C
Yeah,
it
was
it's
great
work.
It's
like
so
cool
to
see
that
it's
like.
Oh,
this
could
happen.
It's
really
exciting.
A
And
then
I've
got
the
next
section
things
to
improve
on
this
iteration
we
had
a
couple
of
incidents,
kind
of
stemming
from
some
work.
Security
was
doing,
making
our
buyer
experience,
repo
private,
which
is
fair
and
and
valid.
A
This
kind
of
I
guess
got
communicated
higher
up
the
chain
and
never
really
made
its
way
down
to
us.
Since
you
know
they
didn't
think
it
would
have
an
engineering
impact
and
then
it
did-
and
you
know
kind
of-
took
us
down
and
it
leads
to
a
loss
of
credibility.
You
know
if
it
looks
like
digital
experience
broke,
something
or
buyer
experience.
A
Repo
broke
something
it's
not
a
great
look
for
us,
so
hopefully
we
can
improve
that,
like
end-to-end
communication,
they're
top
to
bottom
communication
going
forward
next
is
Megan.
D
D
First,
is
just
like
think
about
the
use
of
the
if
versus
V
show,
if
there's
something
that
you
need
to
render
on
a
page
that,
like
we
need
analytics
for
on
page
load,
it's
not
gonna
work,
if
you're,
using
the
show
or
via
on
something
just
yeah,
be
mindful
when
you
use
those
second
I'm
still
catching
some
uses
of
rendering
markdown
in
the
typography
component,
I've
kind
of
mentioned
this,
like
two
or
three
times
in
the
past
year.
D
I,
don't
really
think
it
breaks
anything,
but
when
I
have
to
go
in
a
page
and
like
in
the
dev
tools
and
troubleshoot
something-
and
it's
just
like
screaming
a
bunch
of
Errors
at
me
and
I'm
like
it's,
not
fun
and
like
we're
moving
so
fast,
sometimes
to
make
these
Pages
like
I,
know
things
happen,
but
we're
even
missing
these
in
the
code
reviews
to
help
hope
some
of
these
reminders
to
kind
of
slow
down
and
look
through
these
will
help
and
the
final
one
is
if
you're,
making
a
card
for
your
page
or
section
and
the
card
is
clickable,
and
you
also
have
a
button
component
in
there.
D
That's
to
the
same
link.
It
does
not
work
out
great.
You
don't
use
a
button
inside
a
a
tag.
What's
happening
is
if
the
card
has
an
analytic
tag
on
it,
then
the
button
does
and
someone
clicks
on
that
button.
The
analytics
are
firing
twice.
I've
learned
so
be
mindful.
I
know
the
the
button
component's
nice
because
it
has
all
the
Styles
in
it,
but
it's
not
having
the
HTML,
syntax
and
functionality.
We
think
it
is
so
don't
have
an
a
tag
and
an
a
tag.
Event
bubbling
happens,
but
cool.
E
Yeah
I
was
just
gonna,
bring
up
that.
We've
talked
about
like
reviewer
guidelines
for
us,
like
for
this
team
over
the
course
of
the
maturity
of
this.
You
know
sort
of
deal
I
feel
like
it
would
make
sense
to
kind
of
like
revisit
those
at
some
point,
because
I
think
after,
like
a
passing
of
time,
it's
I
find
that
it's
sometimes
unclear
to
know
what
I
should
be
looking
for
in
terms
of
a
review,
so
I
think
it'd
be
a
good
idea
to
like
I.
Don't
know
have
all
of
that
be
updated.
D
Oh
yeah
I
was
gonna
mention
so
like
when
I
was
spreading.
All
these
this
stuff
down
Dimension
today
I
was
like
man
I
wonder
if
I
like
we
can
just
automate
something
like
I've
mentioned,
the
markdown
and
the
typography
thing
so
many
times,
but
if
I
make
like
an
eslint
custom
thing,
I've
never
done
that
before
and
I
looked
into
it
and
I
was
like
this
is
really
hard
and
it's
gonna
be
a
lot
of
work.
I,
don't
know
if
it's
worth
it,
but
I
can
keep
looking
into
it.
D
C
Just
a
quick
ask:
we
discussed
this
in
our
design
meeting
this
week,
but
I'm
doing
a
terrible
job
at
this,
but
if
you
see
issues
that
say
like
ux
or
design
and
like
the
top
part
of
it,
can
you
just
rename
them
to
like
brackets
ux
and
then
also
brackets
in?
So
it's
all
like
consistent
I'm
doing
a
very
bad
job
with
it.
So
we
love
you
all
help
everyone's
help
to
do
this,
I!
Don't
care
what
it
is
for
engineering
Lauren
Justin,
if
you
all
have
an
opinion
on
it.
C
Let
me
know,
but
just
for
the
ux
one
in
particular,
just
keep
it
a
square
bracket.
It's
ux.
C
No
Laura
I
think
it's
like
on
an
Laura's
question
and
the
doc
was
am
I
still
reviewing
all
the
customer
facing
changes
with
the
q1
plan.
C
It's
a
little
bit
easier
now
because
it's
like
we
know,
what's
getting
pushed
so
the
designers
make
sure
they
get
overview
and
as
long
as
it's
in
the
q1
plan,
and
we
have
designers
approval,
I'll
I'm,
obviously
like
looking
at
the
designs
before
they're
going
into
engineering,
but
as
long
as
it's
in
the
q1
plan,
it's
okay,
that
the
designers
have
approval
rights
on
that.
If
it's
anything
beyond
that
and
not
within
that
scope,
then
please
take
me.