►
From YouTube: Digital Experience Team Retro - June 17, 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
Hi,
everyone
welcome
to
the
digital
experience
teams,
iteration
retro
meeting,
so
we'll
go
over
things
that
went
well
and
things
to
improve.
On
from
the
last
two
weeks
today
is
june
17th
and
I
believe
for
things
that
went
well.
Jess
has
the
first
point
yeah.
I
just
had
a
few
coffee
chats
this
week
that
were
very
productive.
All
people.
A
I
never
had
a
coffee
chat
with
some
completely
random
and
again
it's
like
a
good
reminder
for
me
that
not
everything
has
to
be
asynchronous,
and
sometimes
it's
actually
better
to
like
have
a
chat
with
someone
in
person
so
to
speak,
and
it
felt
a
little
bit
like
slowing
down
to
speed
up
like
sometimes
I
feel
like.
I
don't
have
the
time
for
a
coffee
chat,
but
actually
by
having
that
coffee
chat,
I
get
more
done
or
more
productive
or
whatnot.
A
So
I
had
a
really
great
chat
with
brie
one
of
our
content
strategists
and
she
was
able
to
produce
a
new
template
for
us
to
use.
We
want
to
request
a
content
resource
for
them,
so
that's
great,
and
there
was
a
lot
of
confusion
around
who
were
supposed
to
ask
before
that.
So
I
got
a
lot
of
clarity
on
what
was
going
on
there
and
then
I
had
a
great
random
chat
with
bruno
one
of
our
sales
team
members.
A
That
kind
of
led
me
to
remember
that
we
have
other
users,
not
just
external
but
internal
as
well,
and
I
have
a
couple
issues
produced
from
that
and
also
chatted
with
dylan
mourinho,
who
had
great
ideas
about
the
install
page.
I
like
looked
at
that
page
and
I
was
like
I
don't
know
what's
going
on
here
and
I
felt
like
really
unsure
about
what
I'm
supposed
to
do.
B
C
B
Yeah
that
gives
funny,
so
I
want
more
of
this
cross-functional
teams
using
gitlab
to
collaborate
and
continuously
build
digital
products
and
we're
like
the
perfect
use
case
for
that
and
helping
make
that
happen
and,
for
example,
siri
patel
and
lisa
rom
contributed
content.
Changes
to
the
gcp
partner
page
merge
request
using
the
get
lab
web
editor
wow
like
you,
could
track
the
commit
what
they
change
word
for
word.
It
is
the
single
most
efficient
way
to
add
content
and
edit
content
on
our
website,
and
it
always
will
be
period.
Netlify
cms
super
awesome.
B
E
I
just
wanted
to
bring
up
a
point
that
nathan
brought
up
a
good
point
about
eslint
rules
and
so
in
an
mr
for
the
nav
work
that
I've
been
working
on,
and
I
said
that
we
should
consider
like
adding
to
them
editing
them
doing
stuff.
Like
that.
I
also
added
like
an
extra
side
point,
because
you
know
I've
been
struggling
with
this
one
for
a
while
and
I
actually
haven't
like
ever
vocalized
it.
E
But
when
you're
trying
to
run
the
job
locally,
one
of
the
lint
jobs,
it
will
run
on
the
known
modules.
And
we
don't
want
that
locally.
And
I
think
it
has
to
do
with
like
the
way
that,
like
the
order
in
which
the
pipelines
work
on
the
gitlab
config,
where,
like
those
files,
don't
exist
yet
in
the
way
that
it's
set
up
anyway,
yeah.
D
A
D
Want
to
add
on
to
that,
that's
okay,
yeah,
I
think
just
coming
up
with
a
standard,
it
doesn't
have
to
be
strict.
It
doesn't
have
to
be
just
to
have
something
I
know
like
airbnb
has
a
good
like
default
kind
of
starting
point
and
then
also
just
to
start
a
conversation
on
what
what's
the
end
goal
of
like.
What
do
we
want
this
repo
to
look
like
at
the
end?
Do
we
want
to
be
viewed?
D
We
want
jquery
out
of
here,
like
what
can
we
be
doing
in
our
day-to-day
work
to
get
ourselves
in
a
better
direction,
so
what
I've
been
doing
is
if
I
have
like
a
page
that,
for
example,
the
events
page,
it
was
written
four
years
ago
a
lot
of
jquery
a
lot
of
old
js,
so
I
kind
of
rip
it
out
and
redo
it.
But
I
don't
know
if
that's
necessarily
the
best
thing,
because
I
don't
know
the
end
goal
is
so
maybe
we
just
start
that
conversation
now
that'd
be
great.
E
E
It
might
be
a
little
stale
now
now
that
we've
been
here
longer
and
our
thoughts
may
have
evolved
since
that,
but
like
I
can
direct
you
to
some
of
the
issues
where
we
have
those
conversations,
because
I
think,
like
it's
really
interesting,
to
look
back
and
to
see
like
what
decision
like
what
has
changed
since
then,
I
would
link
them
to
you
right
now.
If
I
just
didn't
go
and
cook,
but
like
yeah
yeah,
I
can
link
that.
A
I
think
just
to
add
on
there
was
like
so
in
terms
of
like
the
old
rickety
dub
dub
repo,
when
I
first
joined,
is
right
when
brandon
had
kind
of
started,
this
initiative
of
naming
all
of
our
css
files,
2020
whatever
css
like
there's
20
20
base,
but
then
like
there
would
be
like
20,
20,
home
page
or
like
20
20.
I
have
about
like
you
would
know
which
pages
had
been
at
least
css.
A
Their
css
had
been
updated
because
it
was
2020
at
the
time
and-
and
so
it
was
a
really
quick
way
to
like
see
what
was
updated
versus
what
hasn't
been
touched
in
the
last
like
four
years
and
and
like
know
that,
if
it
didn't
have
that
2020
css
file
that
it
probably
was
like
old
stuff
that
we
could
just
rip
out,
who
knows
what
spaghetti
was
cooking
up
was
boiling.
You
know,
but
yeah.
So
I
did
like
that
convention
of
just
like
a
quick
way
of
like.
A
B
Javi
brought
up
a
a
side
project
he's
building
see
if
he
can
just
dump
a
next
instance
in
our
repo,
and
this
is
something
michael's
talked
about
too.
It's
like
what,
if
we
built
you,
know
another
project
within
it
with
a
different
static
site
generator
and
slowly
migrated
parts
of
the
site
over
to
it,
and
that
would
be
really
interesting
to
explore,
see
if
it's
feasible
and
then
we'd
always
know
where,
where
our
new
stuff
is.
If
we
did.
B
F
I
think
we're
done
on
that
item
yeah.
I
have
a
small
bit
for
the
last
one
that
I
just
put
in.
I
discovered
during
our
design
101
session
that
the
figma
type
stack
labeling
versus
the
tailwind
labeling
are
not
aligned,
which
is
confusing
engineers,
so
body
one
is
called
something
completely
different
in
tailwind.
F
You
know
my
instincts
are
the
path
of
least
resistance
is
to
update
the
figma
file
I'll,
create
an
action
item
for
that,
but
that
definitely
needs
to
be
improved
because
I
think
a
lot
of
time
is
wasted
there,
not
only
you
know
through
the
coding,
but
then
in
in
review.
I'm
like
this
is
not
the
right
thing
and
now
I
understand
why
it's
not
the
right
thing:
it's
because
it's
not
labeled
the
same.
It's
very
confusing!