►
From YouTube: Digital Experience Retro - Sept 21, 2023
A
B
Just
shout
out
to
the
legal
team
Brown
and
Eugene
I
collabed
with
them
in
a
git
lab
issue
and
got
their
thumbs
up
on
extending
our
marketing
cookie
and
adding.
What's
here,
a
user
is
to
it,
which
is
just
really
nice
to
have
that
thumbs
up
before
we
move
forward
with
that
work
and
then
also
shout
out
to
the
growth
team
and
collaboration
with
creating
a
lining
on
our
first,
a
B
test
and
product
with
the
free
trial
form.
So
that
is
our
rollout
experiment
issues.
B
D
D
D
D
C
B
And
another
shout
out
to
our
translated
team,
their
fresh
eyes
on
their
site
are
helping
us
catch
things
and
Patch
them
up
that
we've
overlooked
and
an
example
of
this
is
our
English.
Privacy
page
was
using
an
old
template
in
the
dub
repo,
while
our
translated
versions
were
in
the
be
which
is
great,
but
the
different
templates
made
it
hard
to
review
and
update
that
content.
So
it's
just
nice
to
have
fresh
eyes
on
the
site,
I'm
looking
it
over
because
we're
so
so
in
it
and
in
the
weeds.
C
B
C
C
D
I'm
sorry
Kale's
walking
by
so
I
turn
on
the
camera
yeah.
So
this
one
might
not
actually
be
under
control
or
maybe
cover
the
solution,
but
Laura
brought
up
a
good
point
and
that
we
can't
really
find
and
replace
stuff
anymore.
So
say
you
want
to
go
in
and
change.
I,
don't
know
event
or
like
a
phrase
that
we
use
across
the
site
sure
there's
a
search
under
the
content
section
of
the
CMS.
But
it's
not
the
best.
It
does
like
partial
matches.
D
It's
not
as
great
as
you
know,
searching
repository
and
just
finding
eight
instances
and
doing
a
final,
replace
so
I'm
a
little
nervous
that
we're
going
to
reach
a
point
where
maybe
we
have
to
change
the
word.
I,
don't
know,
monitor
or
a
stage
name
and
I
know
we're
trying
to
reuse
text
across
the
site
and
reuse
content
and
entries.
But
we're
going
to
run
to
this
at
some
point
where
you
know
we
need
to
update
something
100
times
and
we
can't
so
just
something,
maybe
for
us
to
think
about
and
I
don't
know.
B
D
D
Can
but
then
it
gives
you
a
list
of
entries
and
in
that
list
of
entries,
it'll
give
you
partial
matches
it'll
give
you
either
go
find
what
field
that
the
match
is
in
like
it's,
not
as
nice
as
being
like
hey
online
for
character,
eight.
This
is
where
it's
used.
It's
like
somewhere
in
this
entry.
It
is.
B
A
Like
well,
we
changed
everything
from
devops
to
devsecops
that
that
sort
of
thing
is
going
to
be
tough,
but
even
just
like
the
the
content.
Editors
like
I
know,
like
the
events
team
are
like
people
changing
the
resources
page,
because
that's
top
of
mind
for
me,
like
they
will
often
like
just
control
F,
to
find
where
it
says,
like
Gardner
report
2022
and
then
change
it
to
2023.
But
now
they're,
just
gonna
have
to
like
yeah.
It's
just
going
to
take
some
use
to
like
navigating
contentful
and
figuring
out.
A
What's
an
entry
versus
a
content
type
and
where
yeah,
where
the
thing
is
that
you're
trying
to
change
but
yeah,
it's
tough
to
not
have
the
foresight
to
know
like
we
can
make.
What
do
they
call
it
like?
Like
the
pricing,
you
know,
set
our
pricing
to
99
as
like
a
variable
whatever
and
use
that
throughout
the
site.
But
we
don't
know
for
words
like
devsecops,
that
that
should
be
like
a
universal
variable,
that
we
should
be
able
to
change
all
the
time.
B
Seems
like
something
to
keep
an
eye
on
as
we
roll
this
out
to
our
our
stakeholders.
People
creating
content
documentation
once
we
figure
it
out,
I'll
jump
to
three
I
was
just
curious.
What
are
contentful
release
plan
is,
and
if
that
is
documented
anywhere,
for
example
like
when,
are
we
using
the
contentful
branch?
And
when
are
we
not.
D
D
C
D
D
D
There
was
one
just
with
I
think
when
we're
the
SEO
content
type
I,
don't
know
if
there's
a
title
missing
or
if
we
need
to
add
a
title
but
yeah
the
page
title
didn't
show
up
on
the
CE
versus
EU
page,
so
it
could
have
just
been
an
oversight
on
that
specific
page.
But
it's
one
thing
just
to
remember
like:
let's
make
sure
we
look
at
the
metadata
to
make
sure
it's
it's
working
properly,
yeah.
A
B
D
I
would
say
once
the
first
batch
goes,
I
think
we're
good
to
go
straight
to
Maine.
The
only
reason
that
we're
bundling
this
stuff
up
is
that
there's
potentially
going
to
be
John's
changes
which
is
going
to
implement
the
services
we've
added,
some
more
like
backendy
stuff,
like
we've,
had
content
types
and
all
sorts
of
static,
globals,
so
I
think
once
this
batch
is
good,
we're
good
to
go
straight
to
Maine.
I
think
this
is
kind
of
like
the
big,
the
first
hump.
B
D
C
Solutions
might
be
another
prime
example.
If
we
were
to
feel
like
this,
the
scope
of
work
feels
too
much
and
we
want
to
make
sure
we
do
some
more
testing.
We
could
spin
up
the
branch,
merge
all
the
solutions
into
that,
but
I
think
that's
we'll
play
that
by
either
this
early.
This
next
iteration
as
people
start
diving
into
Solutions,
because
that's
the
the
next
iteration
is
like
all
the
solution
pages.