►
From YouTube: Digital Experience Retro - Mar 10, 2022
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
A
Hi,
everyone
welcome
to
the
digital
experience
team
iteration
retro
meeting
today
is
thursday
march
10th
and
we'll
go
over
what
went
well
and
what
to
improve
on
for
the
last
two
week,
iteration
period.
First
up
for
things
that
went
well,
jess
has
the
first
point
yeah.
So
I
think
this
was
the
first
week
we
actually
merged
a
branch
in
figma
for
our
team
and
no
tina's
saying
no.
I
lied.
Where
did
we
merge
before.
C
Thank
you,
nathan
and
tyler
for
kind
of
making
a
plan
for
this
iteration
just
things
you
can
get
ahead
on
with
the
refresh
project.
I
was
a
little
nervous,
come
sprint
planning
because
I'm
like
I
don't
know
what
to
work
on,
but
that
helped
a
lot.
So
thank
you
looks
like
matteo,
and
miguel
are
also
big
fans,
so.
D
Actually
something
to
add
to
that,
so
I
have
a
giant
list
of
stuff
for
next
iteration.
I'm
gonna
probably
share
it
in
like
the
digital
experience
channel
and
maybe,
if
someone
wants
to
add
on
to
it
or
make
changes
to
it,
also,
how
do
we
do
we
want
to
pick
and
choose
what
we
work
on,
or
do
we
just
want
it
assigned
like?
I
want
everyone,
obviously
to
work
on
what
they
they
want
to
work
on,
but
I
don't
know
the
best
way
to
handle
this.
C
A
A
I
have
the
next
point
here
the
demo
meeting
that
we
just
had
release
meeting
whatever
we're
calling
it
these
days,
I
think,
went
really
well,
I
think
we're
getting
the
hang
of
kind
of
passing
off
to
one
another,
so
yay,
and
then
I
guess
we
can
move
right
on
to
things
to
improve,
on
which
I
have
the
first
point.
So
I
made
an
update
to
the
home
which
broke
some
things
for
seo
and
in
hindsight
I
probably
should
have
tagged
seo
prior
to
merging
that
in
and
maybe
for
future.
A
I
guess,
if
we're
doing
like
important
pages
that
might
affect
seo
and
net
new
pages,
I'm
not
sure,
but
just
kind
of
keeping
them
more
in
the
loop.
I
felt
bad
about
that
and
part
of
what
came
out
of
that
was.
I
was
missing
a
lang
tag
and
that
made
me
think
of
all
the
localization
work
that
brandon
had
done
last
year
and
whether
we
have
a
plan
for
that.
I
think
barker
has
a
point.
E
A
D
D
We
have
to
kind
of
drill
down
and
like
get
all
the
children
and
it
just
it's,
not
the
prettiest
solution,
and
especially
with
localization
and
internationalization,
coming
up
like
what,
if
language
reads
from
right
to
left,
then
we
want
to
wrap
that
text
in
the
typography
component
so
that
we
can
change
like
the
text
direction
and
sometimes
languages
are
longer
than
others.
So
maybe
we
want
to
truncate
stuff.
So
I
don't
know
the
solution
right
now.
D
I
don't
know
if
it's
we
go
away
from
markdown
or
maybe
we
find
a
way
to
play
nicely
with
it.
So
I'm
thinking
maybe
just
start
thinking
of
ideas
and
then
maybe
in
the
ui
to
code
meeting,
we
can
figure
out
how
we
want
to
handle
it.
But
it's
not
super
urgent.
It's
just
something!
That's
going
to
come
on
our
plate
soon,
yeah
john.
F
E
F
B
This
isn't
a
new
problem.
Just
opt-in
has
this
problem
also,
but
getting
assets
and
content
from
our
cross-functional
team
members
is
challenging
for
some
of
the
issues
I'm
working
on,
the
mrs
are
ready
to
go
when
there's
still
no
content
and
they
get
old
and
stale
and
people
are
like.
Why
can't
I
push
this
button
even
with
an
iterative
approach?
It's
still
really
hard
to
get
things
out
and
then,
once
that
content
comes
in-
and
you
know
you
start
talking
to
those
team
members
after
you
haven't
been
on
that
project.
B
A
D
A
A
Yeah
I
tossed
in
the
link
there's
a
handbook
page
about
smartlink,
so
I
think
that's
the
platform
we're
using,
but
I
think
I
think
brandon
had
gone
in
and
like
added
separate,
like
language
tags
to
like
the
demo
page
and
like
a
handful
of
other
pages
that
were
requested,
but
yeah
we'd
have
to
kind
of
go
back
and
then
look
at
how
we
want
to
do
that
moving
forward,
because
that
was
a
band-aid.
I
know
that
brandon
kind
of
pushed
back
on
on
just
manually,
translating
pages
but
yeah
any
last
thoughts.
I
see.