►
From YouTube: Digital Experience Retro Video 03/11/2021
Description
Sprint Retro Doc: https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/edit?usp=sharing
Digital Experience handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
Hello,
everybody
welcome
to
the
digital
experience,
iteration
retro
meeting,
where
we
go
over
what
went
well
and
what
to
improve
on
for
future
iterations.
So
this
is
for
today,
which
is
march
11th.
So
we'll
start
off
with
things
that
went
well,
I
see
that
jess
added
one
she's,
not
on
the
call,
and
she
said
that
using
blocks
tina
put
together
in
slippers,
figma
file
has
improved
the
workflow
workflow
speed,
which
is
awesome
and
then
stephen.
I
think
it's
next.
B
C
I
think
I'm
next
something
that
went
well
for
me
during
this
print
was
collaborating
with
the
search
team
I
put
in
some
requests
for
some
metrics
and
shane,
both
shane
and
niall
responded
very
quickly,
and
so
that
made
me
super
happy.
I
expected
to
be
waiting
weeks
and
not
48
hours
to
get
some
of
this
information.
So
I'm
I'm
grateful
for
that.
D
A
Laura
yeah,
I
I
guess
there
was
a
meeting
that
michael
had
created
for
the
commit
event,
that's
ongoing,
so
we
got
to
align
with
the
brand
team,
the
content,
team
and
digital
experience
team
all
getting
together
to
figure
out
what
the
path
forward
would
look
like
for
creating
events
templates
in
general,
and
I
think
we
figured
out
a
lot
in
that
meeting
and
got
a
lot
of
questions
answered.
So
that
was
nice.
A
Even
though
we
try
to
work
asynchronously,
it
was
nice
to
sync
up
in
person,
and
I
have
the
next
one
also
javi
mentioned
in
one
meeting
that
he
was
adding
slippers
documentation,
and
so
I
reached
out
and
added
some
of
the
gotchas
that
I
had
kind
of
come
across
while
developing
in
slippers,
and
he
was
super
quick
to
add
them
to
the
documentation
for
anyone
else.
That
might
have
been
struggling
with
similar
issues,
and
I
think
tyler
is
putting
one
in
now.
E
Yeah
last
retro
I
had
been
struggling
with
like
waiting
and
like
w-e-I-g-h
like
waiting
issues
and
time
estimation
and
this
past
iteration.
I
feel
much
better
about
that
and
I
feel
like
yeah
throughout
this
iteration.
I
felt
like
this
is
the
appropriate
amount
of
work
and
like
still
a
couple
things
that
were
like
expanded
beyond
scope,
but
like
nothing
that
felt
so
out
of
touch
with
like
what
I
anticipated
at
the
beginning.
F
B
E
Yeah,
I
just
realized,
I
think
I
started
and
collaborated
on
three
or
four
conversations
through
this
iteration,
where
I
just
had
like
the
absolute
wrong
interp
interpretation
of
figma
files,
because
I
was
just
reading
them
totally
wrong
and
I
was
like
no
no.
The
thing
says
like
that's
what
it
says:
laura
literally
posted
like
three
screenshots
of
a
thing
with
a
label,
and
I
was
like
right,
but
the
label
still
says
this.
Other
thing
it
was
like
highlighted
with,
and
I
just
like
did
not
see
it.
E
It
took
me
like
three
or
four
times
so
I
just
like
I
I
I
will
get
better
at
figma
tina
showed
me
the
desktop
app.
I
apologize
for
any
inconveniences
I
caused
from
just
reading
those
things
incorrectly.
I
just
wanted
to
call
that
out
that
that
has
caused
some
of
my
like
miscommunications
there
and
thanks
for
everyone
for
the
patience,
and
I
appreciate
your
supportive
comments
down
here,
everyone
else
and
tina.
I
absolutely
would
attend
a
101
session.
B
E
G
Yeah,
so
it
was
just
the
same
thing
so
everyone
all
in
that
meeting.
I
knew
oh,
my
god
tyler
did
not
get
what
everybody
was
trying
to
say,
but
it's
normal,
because
I
also
ran
through
the
same
thing
when
I
was
working
on
google
analytics
course.
It's
been
a
long
time.
I've
worked
on
google
tag
manager
synchronizing
with
google
analytics,
so
it
was
hard
for
me
to
figure
out
which
target
is
this
guy
using.
So
I
have
to
call
shane
like
come
on.
G
Come
come,
come
and
show
me
whatever
you
have
going
up
there,
and
he
just
explained.
I
could
take
that
another.
So
I
I'm
also
planning
to
pick
up
on
some
other
stuff
like
marketo,
when
brandon
was
explaining
how
it
works.
I
really
love
that
I've
never
played
around
with
it
before
so
I
think
we
can
all
learn
from
each
other
nobody's
an
expert
will
keep
knowing
different
french
stuffs.
I
love
this
team.
This
is
like
family
to
me,
yeah!
That's!
It.
D
I
have
the
next
one,
so
the
brand
messaging
project.
It
wasn't
really
like
built
ready
for
me
to
go
in
there
and
start
building
the
emrs
to
update
all
the
pages.
The
date
got,
pushed
and
pushed,
and
now
it's
next
wednesday
and
it's
still
kind
of
a
fire
drill
there.
There
isn't
like
a
clear.
This
is
what
you're
updating
on
this
page
with
this
language.
D
So
I'm
wondering
how
we
can
get
ahead
of
these,
so
they
don't
keep
reoccurring
because
it's
really
it's
really
stressful,
so
yeah
and
then
the
next
point
I
have
is
process
documentation
for
updating
slippers,
components,
packaging
them
in
a
release
and
then
using
them
in
dub,
dub
dub,
and
I
linked
to
the
the
slack
thread.
I
had
I'm
a
little.
I
there's
there's
probably
a
process
there,
and
so
I
just
kind
of
want
to
know
what
that
looks
like.
E
There
there
isn't
or
like
there
is
there's
a
thing
that
like
javi
and
I
have
done
a
handful
of
times,
but
we
haven't
documented
it
and,
like
I've
kind
of
neglected
to
document
it
purposefully,
because
I
wanted
to
wait
till
the
question
came
up.
I've
got
a
point
here
about
like
what
I
think
we
should
do
with
this
below.
But
the
answer
is
like
yeah
like.
E
D
E
E
But
if
you're
working
like
I'm
working
on
an
mr,
where
I've
got
branch
in
dub,
dub,
dub
branch
and
slippers,
neither
of
these
things
are
ready
for
other
people
to
consume.
So
I
have
an
alpha
tag.
It's
like
0.6.4
dash
alpha
and
I
can
publish-
and
I
can
increment
on
the
alpha
and
like
pull
it
into
www
without
anyone
else
having
like
it.
It
denotes
that
not
only
is
this
unstable
v0,
it
is
like
literally
a
work
in
progress
like
this,
and
then
I've
published
it
like
four
or
five
times.
E
You
know
and
it
publishes
very
quickly,
but
that
is
like
the
the
crux
of
it
and
and
we
should
document
it
like
take
this
question
turn
it
to
an
mr
document
it
and
like
clear
that
up
for
folks
but
yeah,
I'd,
publish
new
package
and
keep
things
unlocked
up
and
at
the
end
of
each
the
nice
thing
is
at
the
end
of
each
generation.
We
get
back
to
clean
slate
where
it's
like
boom
increment,
the
minor
version
we're
back
to
0.7.0.
F
D
F
Item
off
of
this
that
I
want
to
give
all
of
the
developers
here
publish
access
to
npm,
because
I
don't,
I
think,
only
me
and
tyler-
have
it
right
now.
So
if
all
of
you
want
to
make
your
publishes
like
you
would
have
to
talk
to
one
of
us
which
is
like
not
efficient,
so
I'll
I'll
talk
to
you
all
on
the
slack
about
that.
B
B
G
B
System
and
it's
the
most
robust,
so
it's
it's
pretty
cool
and
the
next
one,
the
submission
process
for
the
blog,
so
we
submitted,
but
we
didn't
go
through
the
right
channels.
This
was
a
mistake
on
my
part,
which
then
led
to
the
edits
that
I
showed
you
in
the
draft
earlier
on
how
it
goes
back
through
things
so,
and
it
wasn't
explicitly
clear
how
to
submit
for
a
blog,
like
the
actual
process
of
submitting
for
it
like
going
to
going
to
the
cms
putting
in
your
content,
editing
it
making
it.
B
You
know,
playing
your
hierarchy
and
all
that.
That's
very
that's,
very
easy
to
do,
and
very
succinct,
but
actually
the
process
of
it
going
through
copyright
is
making
sure
that
it's
speaking
the
right
language
and
to
get
a
different
set
of
eyes,
and
if
that
wasn't
explicitly
clear-
and
so
I
wondering
is
there
a
way
that
we
can
kind
of
improve
the
two
of
them
like
they
are
related
in
some
in
some
ways
to
sort
of
save
anybody
that
the
pain
have
gone
through.
B
What
I
had
to
go
through,
which
was
to
put
it,
live,
celebrate
it,
but
then
gets
old
actually
as
edits
and
things
you
have
to
go
back
through
that,
and
so
I'm
wondering
is
there
a
way
to
sort
of
improve
that
process,
bringing
the
tune
closer
together
and
especially
because
my
intention
is
to
have
more
blog
posts
pushed
as
we
go
for
this?
It's
very
good
for
our
team.
B
It
gives
us
a
lot
of
scope
and
visibility
as
we
go,
especially
as
we're
making
improvements
at
the
pace
we
are
and
if
anyone
hasn't
read
the
blog.
Please
do.
Let
me
know
what
you
think,
so
I
can
improve
for
the
next
ones,
but
yeah
that
I
think
the
submission
process
for
the
blog,
where
it's
the
netlify,
but
also
there's
like
a
pre-edit
that
needs
to
happen.
A
Cool,
I
think,
I'm
next
a
small.
I
guess
we
noticed
earlier
today
we
had
a
demo
with
inbound
marketing
and
some
of
the
pages
that
were
shown
were
created
under
the
topics
pages,
but
they
were
using
the
old
way
of
doing
things
instead
of
using
netlify
cms
to
build
those
topics
pages,
so
we
have
new
documentation
around
netlify
cms,
so
hopefully
that
helps
but
just
yeah
getting
the
word
out
a
little
bit
more.
D
C
My
point
relates
loosely
to
lauren's
point
about
the
run
messaging
project.
I
find
that
web
page
requests
are
still
very
nuanced.
I
think
we
need
to
collaborate
on
a
way
of
having
some
kind
of
template
to
collect
like
basic
functionality.
Examples
for
especially
for
cross-functional
requests
like
I
have
a
multitude.
For
example,
I've
been
giving
a
multitude
of
links
to
issues
and
spreadsheets
and
things
that
say
put
a
schedule:
cfp
block.
What's
the
cfp,
oh
call
for
proposals.
C
Well,
how
does
that
work
and
there's
just
like
literally
just
that's
all
that
things
say
and
trying
to
track
down
details
is
extremely
time
consuming
and
really
bogs
down
the
process
if
it's
already
in
somebody's
head,
if
it
could
just
be
documented
before
it
lands
on
ux,
designer's
lap
or
in
engineers.
That
would
be
great.
E
There's
there's
a
heading
in
the
like
get
lab
communications.
I
know
this
guy,
it's
not
it's
like
number
13
in
an
ordered
list
on
the
communications
page
I
think
is
like
avoid
acronyms
so,
like
I
think,
just
like
I,
like
I'm
gonna,
commit
to
like
doing
better
about
fewer
acronyms
and-
and
it
is
like
part
of
the
handbook
so
would
definitely
like
yeah.
I
want
fewer
acronyms
because
I'd
always
get
lost
with
them.
D
I'd
like
to
to
work
with
you
on
that
from
the
engineers
perspective,
I
like
to
know
exactly
what
I'm
doing
to
something
by
the
time
I
get
there
to
updating
it,
and
I
assume
for
you,
if
you're
building
a
template
you
want
to
like
have
the
functionality
and
all
the
information
instead
of
with
the
brand
messaging
problem,
I'm
pulling
from
a
variety
of
sources,
and
I
don't
I'm
making
decisions
like
ooh,
which,
which
line?
Should
I
use
here?
I
don't
know
like
I
shouldn't
be
making
that
decision
yeah
so.
C
B
A
E
A
Sorry,
I
was
just
gonna
say
in
terms
of
the
like
trying
to
collect
more
information.
I
mean
we.
I
think,
we've
all
run
into
this
when
we
get
handed
something
without
enough
stuff.
I
don't
know
how
to
fix
it.
I
know
that
becky
was
making
new
templates
that
for
issues,
but
even
that
was
like
a
whole
process
to
get
people
to
kind
of
fill
them
out
properly
so
yeah,
maybe
maybe
there
is
like
a
working
video.
We
can
do
to
be
like
hey.
I've
just
received
this
issue.
A
E
E
It's
so
like
it's
challenging
to
do
this
in
the
moment,
but
like
if
you're
go,
and
sometimes
it
makes
sense
for
like
informal
communication
on
slack
but
like
if
you've
got
a
question
and
you're
about
to
type
it
into
slack,
like
let's
try
and
like
type
it
into
an
mr
and
then
be
like
all
right.
Here's
my
question:
it's
in
a
blank,
mr
and
then
like
link
it
in
slack
and
be
like
hey.
I've
got
this
question
here.
E
It
is
like
let's
talk
here
and
then
we
don't
have
to
do
like
slack
to
issue
to
mr,
but
we
can
like
like
collapse,
it
all
down
into
one
place
and
be
like
here's.
My
question
and
you
can
even
like
do
like
a
you
know,
code
diff
in
the
handbook
and
be
like
like
to
do
like
answer
this
question
or
whatever,
and
then
people
can
do
it.
E
Specifically
in
those
lines
and
see
very
precisely
like
what
we're
talking
about
and
the
and
when
we
get
the
answers
done,
we
click
approve
and
merge,
and
then
it's
written
down
right.
So
like
yeah,
I
think
just
more
of
that
for
handbook
first
stuff
and
we
can
take
the
same
approach
in
slippers
specifically
too,
as
like
just
do
those
questions.
Mr
first.
A
E
That
is
very,
that
is,
like
super
useful
yeah.
I
love
that
and
related
to
like,
even
if
it's
not
it
doesn't
have
to
be
a
blocker,
you
can
like
tie
it
as
like.
Hey,
like
the
reason
I'm
asking
is
because
I
have
this
epic
that
issue
this,
mr,
that
all
need
to
know
this
answer
and
then,
when
you're
going
back
through
those
things
later,
it's
like.
Oh,
the
reason
we
did
this
or
like
there
were
questions
related
to
it
in
this
other
thread.
Here.
E
I'd
like
to
talk
about
mine
yeah,
at
least
first
one,
so
we
are
like
you
know
a
little
over
halfway
through
like
the
middleman
integration
of
the
slippers
stuff,
and
so
we're
really
starting
to
see
the
rough
edges
of
where
the
css
conflicts
are.
I
know
lauren
javi
and
I
have
been
talking
and
I'm
sure
everyone
else
has
seen
it.
We
talked
about
it
a
little
this
morning.
E
I
wanted
to
flag
this
as
an
action
item
of
like
what
I'm
doing
today
and
tomorrow
is
I'm
trying
to
like
answer
this
question
super
nicely
in
a
way
and
lauren-
and
I
were
talking
about
this-
for
the
upcoming
commit
stuff
is
like
what
can
we
do
to
make
it
so
smooth?
No
one
has
to
think
about
the
thing,
and
so
I've
got
like
two
or
three
different
ideas,
some
of
them
that
are
like
low-tech
css
solutions.
E
But
the
challenge
is
that,
like
I,
don't
actually
think
they're
gonna
solve
our
problem,
there's
an
where,
like,
I
don't
think
specific,
like
the
specificity
calculations,
to
make
this
stuff
work
correctly,
may
just
not
be
worth
the
time
or
may
actually
be
impossible.
Based
on
the
state
of
things,
there's
another
solution:
that's
like
more
like,
like
architecture
in
the
templating
in
a
middleman,
but
that
also
comes
with
complications
about
stuff
that
we
do
need
to
like
keep,
because
we
don't
have
everything
like
rebuilt
and
slippers.
E
Yet
and
then
the
third
option
is
a
little
more
high
tech
and
like
I'm,
not
like,
I'm
like
cautious
about
it,
but
I
think
there's
a
way
where
we
can
do
like
shadow
dom
and
cops
encapsulation
with
like,
like
the
underlying
technology
of
like
web
components,
where
we
can
basically
say
like
here,
is
a
like
div
or
like
here's.
Here's
a
spot
in
the
page
that
gets
its
own.
Its
entire
document.
E
So
I
would
say,
like
the
best
course
of
action
for
all
of
us
is
like
if
you're
working
on
slippers
into
middlemen,
like
just
see
like
like,
do
like
the
exercise
of
try
and
pull
slippers
in
the
middle
man
and
then
be
like
okay.
What's
breaking
and
like
solve
it
with,
like
a
very
like
with
like
a
very
specific
task
at
hand
right,
I
think
that'll
be
the
clear
and
then
like
something
will
bubble
up
to
be
the
correct
solution.
I
don't
know
what
that'll
be
so
yeah.
F
Yeah
I
just
wanted
to
briefly
interject.
I
feel
like
this.
This
is
like
what
I
was
thinking
was
the
solution,
and
I'm
not
super
sure.
If
this
was
like
in
my
head,
like
it
was
like
all
right
like
we're,
using
like
styles
that
are
pulled
everywhere
because
of
a
template
that
we
have
where
the
header
and
footer
is
like,
relying
on
other
styles
and
there's
a
ton
of
other
stuff
that
we
may
not
even
know
about
so
like
if
we
rebuild
these
things
from
the
ground
up
with
slippers.
E
Yeah,
that's
the
like.
I
also
like,
and
that's
that's
where
lauren
and
I
started
on
the
epic
for
the
blog
stuff.
We
started
with
a
blank
template
and
we
turned
off
the
defaults,
so
we
turned
off
all
the
styles
and
stripped
them
out,
and
then
we
had
to
turn
them
back
on
for
reasons
and
then
like,
even
when
we
strip
them
out.
There's
other
problem
challenges
too.
So,
like
yeah.
F
Yeah
so,
like
I
almost
feel
like
it
almost
makes
sense
to
just
like
like
like
make.
I
don't
know
if
this
would
be
possible
but
make
like
attempt
like
a
layout.
That's
just
like
completely
fresh.
That
would
probably
have
to
be
our
course
of
action
like
in
my
head.
That's
like
the
easiest
thing
to
do
because,
like
I
feel
like
everything
else
is
just
like
gonna
get
really
complicated.
I
don't
know,
but
maybe
maybe
I'm
misinterpreting
the
problem,
but
that's
kind
of
how
I
see
it
as.
F
E
Yeah,
I
don't
need
to
vocalize
it
too
much.
I
mentioned
it
before
the
little
generator
thing.
I'm
gonna
add
this,
for
I'm
gonna
add
an
issue
about
it.
I
am
on
pto
two
weeks
from
now,
so
I
probably
won't
take
it
on
for
next
iteration
but
I'll
add
an
issue
so
that
someone
else
can
grab
it
if
they
want,
but
just
action
item.
For
me
to
not
forget
to
do
that.
F
I
might
try
to
do
this.
To
be
honest,
so
this
sounds
like
something,
especially
because
I
was
playing
around
with
like
the
like
a
little
bit
of
the
node
stuff,
like
with
the
with
with
the
timing
function.
I
don't
know
if
you
remember
like
some
of
the
things
yeah,
so
I
think
this
actually
kind
of
like
fits
in
nicely,
even
though
the
other
thing
which
is
like
totally
unrelated
okay.
I
just
have
some
notes
about
like
pinging,
michael
about
making
our
meetings
longer
and
so
then,
in
an
action.
F
My
next
action
item
is
giving
all
the
people
published
access
and
then,
coincidentally
enough
doing
other
things
with
yarn
scripts,
so
that
looks
like
that's
kind
of
stuff.
That's
bubbling
up.
I
have
a
note
about
drop
shadows
that
I
forgot
to
add
in
terms
of
the
ui
to
code,
we're
just
using
tillwin
defaults
right
now,
and
I
think
they
work
fine
but
like
if
we're
trying
to
align
closer
to
like
what
the
figma
files
look
like
like.
We
might
see
slight
differences
between
things,
but
it'll
be
good
enough
for
a
while.
B
B
F
A
Yeah,
I
I
added
an
action
item
that
we
talked
about
to
maybe
see
if
there's
a
handbook
edition
or
something
we
can
do
to
give
people
a
view
into
how
we
handle
issue
and
web
page
requests
and
maybe
that'll
help
with
some
of
the
information
that's
missing
in
them
and
then
also
just
to
the
point
of
meetings.
I
did
just
adjust
the
meeting
calendar
starting
on
monday,
so
monday's
iteration
planning
should
be
50
minutes
and
I
added
all
the
retros
to
also
be
50
minutes
subsequently
on
every
two
weeks.