►
From YouTube: Product Marketing DEX | Iteration Release 2023-05-04
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everyone:
this
is
our
iteration
release,
video
for
the
product,
Marketing
Group
for
digital
experience
for
May
the
4th
I'm
heading
over
to
Tina
and
go
in
the
room.
B
B
Here,
I'm
sharing
the
right
screen
am
I
sharing
the
right
screen.
Are
you
seeing
my
boards.
A
C
B
B
B
B
Now
we
want
to
just
kind
of
zoom
out
and
see
how
all
of
these
Pages
fit
together
from
a
customer
perspective
from
a
customer
Journey
perspective
who
they
are
where
they're
coming
from,
where
they're
going
where
they
should
go
and
then
find
Opportunities
to
add
or
remove,
touch
points
and
improve
those
touch
points
and
mostly
I've,
been
working
on
iteration
planning
for
Q2
Solutions
updates,
pulling
metrics
figuring
out,
which
pages
are
performing
well,
not
performing
well,
which
Pages
the
business
wants
to
prioritize,
and
you
know
making
issues
for
those
and
transferring
all
that
knowledge
to
Jess
who's
taking
over
this
body
of
work
and
I've
also
been
working
on
a
product,
Marketing,
Group,
Handover,
doc,
again,
a
transfer
of
knowledge
for
Jess
and
whoever
else
will
be
working
on
product
marketing
for
the
first
time,
so
kind
of
getting
a
little
bit
of
information
on
what
we've
been
doing
for
Solutions
on
our
security
Pages.
B
D
On
some
stuff
that
I
don't
want
to
show
but
yeah.
So
I
did
two
customer
Pages
they're,
just
in
review
right
now,
so
University
of
Surrey,
which
I
thought
of
Surrey
BC.
But
it's
not
I,
think
it's
Siri
UK,
so
I
got
excited.
We
had
a
Canadian
University,
but
not
this
one
and
SVA
so
they're
just
waiting
approval
and
then
they'll
hopefully
go
through
this
week.
D
The
big
one
that
I
worked
on
was
the
JavaScript
Heap
out
of
memory.
You'll
see
I
posted
in
the
digital
experience
team
channel
that
with
of
visas,
change,
looks
like
build
times,
are
down
like
seven
minutes,
so
it
used
to
take
22
minutes
to
go
from
come
to
merge,
request
to
production,
and
now
it's
about
15.
also
updated
node
to
now
version
18.
The
latest
version
18.,
so
we're
still
not
at
20.
D
But
you
know
what
at
least
we're
not
deprecated,
so
we're
still
getting
security
updates,
which
is
awesome
and
then
the
latest
version
of
nuxt,
which
is
going
to
help
us
position
for
next
three.
Eventually,
on
top
of
that,
just
some
small
things:
redirects
a
follow-up
to
the
World
Tour
page,
updating
some
images
and
then
on
the
side,
I've
been
kind
of
doing
a
token
audit.
D
So
we
have
tokens
and
by
our
experience
in
www
and
so
just
making
sure
that
we're
rotating
them
and
making
sure
that
we're
deleting
ones
that
we
don't
need,
but
yeah
I,
think
that's
it
for
me.
Javi
I
think
you're.
Next
on
the
list,
I.
C
Yeah,
it's
perfect.
This
iteration
worked
on
migrating
three
customer
case
studies
over
I
have
one
that's
in
review,
but
again
push
through
the
pipeline.
I
had
one
point
for
something
that
was
wrong
with
one
of
the
devops
pages,
so
the
re-time
pill
was
stretched
out.
There's
some
weird
Behavior
there,
so
I
fix
that
regression.
There's
a
couple
of
smaller
things
with
Dennis
having
some
tracking
braking.
C
There
is
some
breaking
JavaScript
in
one
of
the
pages
that
was
breaking
pretty
much
everything
so
then
picks
that
there's
one
other
thing:
I'm
working
for
Dennis
for
the
tracking
of
some
form
that
still
needs
to
be
worked
on.
I'm
gonna
share
my
screen
for
something
that's
a
little
out
of
the
usual,
but
I
also
worked
on
making
sure
that
Lighthouse
had
access
to
the
Chrome
build
image,
and
so
then
that
got
fixed.
C
Then
last
Friday
I
worked
on
something
called
the
gitlab
CI
server
and
essentially,
instead
of
pushing
our
results
of
Google
Lighthouse
over
to
temporary
storage.
There's
like
a
little
server
project
that
we
can
host
on
our
end
and
then,
like
it'll,
save
all
the
results
historically
I'm
going
to
share
my
screen.
Some
of
you
all
have
seen
this
already,
but
some
of
you
have
not,
and
so
this
is
what
it
looks
like
I.
What
I
ended
up
doing
was
made
a
new
repo
for
this
little
project.
C
We
talked
about
what
I
did
and
then
made
a
separate
branch
in
the
bio
experience,
repo
and
then
pushed
changes
up
through
Lighthouse
and
tried
to
see
what
it
would
look
like,
and
it
looks
kind
of
like
this.
This
is
checking
right
now.
One
commits
results
versus
another
one
and
then
checking
telling
you
like,
which
ones
have
changed,
which
you
haven't.
You
can
go
back.
C
Do
that
tell
you
that
it's
really
really
cool
I
showed
this
to
Justin,
and
he
gave
me
a
meme
as
I
think
of
the
data
it
like
at
Dennis
at
Michael
yeah,
so
we're
gonna
see
if
we
can
at
some
point
get
the
suppression,
because
it'd
be
really
cool
to
have
the
historical
alarm
house
builds.
E
All
right
so
first
week
of
my
iteration
was
mostly
the
white
Gill
up
page
it
had
this
new
drop
down.
That
was
a
bit
tricky
has
to
move
upwards
and
change
the
size
of
everything,
but
it
ended
up
very
cool
I
think
you
can
also
switch
the
content
with
the
the
links
down
below
here
and
yeah.
Then
the
pricing
blocks,
then
I
was
also
migrating
a
couple
of
customer
cases.
A
Kind
of
speaker
Margaret
choose
out
today.
She
is
working
on
the
gitlab
16
event,
landing
page
which
which,
if
you
have
a
initial
review
tomorrow
for
proof
for
the
stakeholders
as
well
as
it
looks
like
she
margarited
two
customer
case
studies
pages
and
fixed
a
bug
on
the
developer
survey
link
error
like
the
anchor
link
position
there
and
I
don't
have
another,
oh
and
then
a
couple
other,
like
small
one
point
bugs
here
and
there
for
UI
work
and
I.
A
Believe
that's
it
for
her,
it's
probably
one
or
two
more
customer
case.
It
is
actually
that
she
is
waiting
for
the
review
process
as
well
yeah.
Thank
you.
Everyone.