►
From YouTube: DEX Engineering Iteration Release meeting
Description
Digital Experience Team engineering release video for Aug 14, 2023 - Aug 27, 2023
C
Okay,
I'm,
like
crying
okay
me
and
my
Midwestern
Mumble,
will
go
as
fast
as
I
can
and
we'll
have
to
talk
about.
No,
my
eyes
are
getting
all
right.
Thanks,
dude,
so
first
off
I
have
an
mro
to
update
the
buttons
on
the
free
trials.secops
page
and
those
are
in
English,
and
now
they
can
be
translated
made
some
pricing.
Page
translation
updates
made
an
update
to
our
changelog
and
we're
having
some
problems
with
our
sorry,
a
changelog
docs.
C
So
if
you're
having
a
problem
with
our
chainsaw
changelog
having
like
duplicate
entries
and
I
found,
that
was
from
so
now,
we
have
like
a
squash,
commit
message
box
and
a
merge
commit
message
box
and
if
you
have
the
conventional
commit
prefix
in
the
squash
message
and
the
Mr
message,
that's
how
we
have
duplicates
so
yeah
just
make
sure
you're
just
putting
it
in
the
Mr
message
box
and
not
the
squash
one.
But
those
dots
are
updated.
C
Finally,
closed
out
the
nav
Spike
issue
that
hubby
and
I
have
been
working
on
thanks,
y'all,
so
much
for
all
your
collaboration
on
that,
but
we're
going
with
the
Veet
git
dependency
route.
There's
some
performance
fix
issues
as
well
that
we
can
do
like
to
fix
our
constant
layout
shift.
C
So
I
created
some
issues
for
that
work
and
for
the
integration
with
CMS
and
that's
ready
to
move
forward
had
a
spike
for
how
our
internationalization
work
is
going
to
work
with
our
CMS.
C
Please
go
take
a
look
at
that
because
that
definitely
probably
impacts
each
and
every
one
of
you
that
might
update
a
page
or
add
a
page
to
our
CMS.
It's
likely
that
when
we
do
that,
we're
not
going
to
when
we
migrate
a
page
to
the
CMS,
we're
probably
not
going
to
bring
the
translations
along
with
it
at
first,
so
that
we
have
like
a
hybrid
approach
and
next
in
our
little
async
data
function.
So
if
English
grab
the
contentful
data,
if
not
grab
our
translated
content
that
lives
in
fire
experience
content
folder.
C
That
means
there
will
be
some
extra
scope
of
work
for
those
pages
that
have
translations,
as
we
might
have
to
update
the
yaml
files
of
the
translated
pages
to
kind
of
fit
with
the
Json
components
or
the
components
that
will
now
lead
Json
data.
So,
just
so
you
know,
might
not
be
an
easy
copy.
C
Paste
that'll
work
for
those
issues,
there's
going
to
be
some
more
coding
updates
involved,
and
lastly,
I
have
something
to
show
for
this
is
the
nav
performance
updates
where
we
removed
personalization
and
updated
the
resource
card.
Let
me
pull
that
up
so
when
I
first
was
working
on,
this
I
was
just
grabbing
the
data
from
my
local
server,
and
this
was
after
the
personalization
was
removed
and
all
these
these
green
circles,
it
was
so
exciting.
C
Big
improvements
just
got
this
to
production
today,
and
things
didn't
quite
budge,
but
I
do
want
to
call
out
that
this
was
from
Lighthouse
or
the
performance
insights
in
our
Dev
tools
and
I.
Don't
think
that's
an
accurate
snapshot.
We
should
be
using
the
page
insights
tool
from
Google.
It
uses
user
data
from
the
past
28
days.
So
every
week
we
should
be
looking
at
that
and
I
have
a
feeling
we're
going
to
be
seeing
some
upward
Trends
and
improvements
in
our
core
web
vitals
I
just
I.
C
Just
don't
trust
this
at
all
or
that
at
least
it
was
the
NAB
that
has
been
kind
of
one
of
the
bigger
issues
of
our
mobile
performance
problems,
but
all
right,
that's
all!
That's
all
I
got
but
I'll
pass
it
off
to
Nathan.
Thank
you.
D
Thanks
those
stats
were
pretty
cool
and
yeah.
It's
not
very
accurate
I
did
some
testing
and
I
like
removed
a
big
JS
file,
and
then
it
increased
the
page
load
time
and
I
was
like
that,
doesn't
make
sense
so
yeah.
We
should
definitely
not
use
Lighthouse
as
a
source
of
Truth
for
production,
at
least
yeah.
So
just
a
bit
of
Maintenance
organization,
so
I
removed,
like
30
of
our
epics.
D
A
lot
of
them
were
done
just
like
you're,
too
old
and
then
about
15
of
our
issues,
I'm
just
trying
to
clean
up
some
stuff
to
get
ready
for
the
CMS,
and
then
I
did
some
CMS
spikes.
So
how
do
we
handle
string,
literals
and
contentful?
D
This
could
be
used
for
maybe
premium
pricing
where
we
want
to
like
reuse,
that
29
value
throughout
the
whole
product
and
I
know
they
said
in
one
of
our
our
calls
there
that
you
could
use
like
inline
references
which
is
like
you
create
like
a
data
content
thing
that
says
like
29
in
it,
and
then
you
reference
that
every
single
time
in
a
rich
text
editor
but
I,
wasn't
sure
how
that's
going
to
scale.
So
I
did
like
a
small
proof
of
concept
of
creating
our
own
string
literals.
D
So
just
using
like
curly,
brace,
curly
brace
I,
don't
know
premium
pricing,
curly,
brace,
curly,
brace
and
then
through
scripts.
We
could
swap
those
out
with
the
actual
values
of
our
premium
and
anyway.
So
that's
all
in
a
best
practices
issue,
I,
just
spun
it
up
today,
I
think
I
linked
it
in
deck.
D
Stand
up,
so
I
just
want
to
put
all
the
findings
from
our
spikes
in
one
place
and
all
the
information
we
gathered
from
all
their
their
contentful
tutorials
I
guess
you
can
call
it
in
one
place
and
then
another
Spike
was
how
to
figure
out
icons
which
ends
up
we're.
Gonna
have
to
spin
up,
probably
a
contentful
app
or
a
contentful
add-on
or
Plug-In
or
Marketplace
app
whatever
they
want
to
call
it.
So
I
looked
into
that
it
doesn't
seem
too
difficult.
D
To
be
honest,
it
has
a
lot
of
flexibility
and
then
on
the
side,
trying
to
help
with
the
Slate
battles
as
well.
I
migrated
slippers
over
to
White
V.
However,
you
want
to
pronounce
it
I
think
it's
veed,
actually
Megan
you're
right
I've
been
calling
a
bite
for
the
longest
time
and
then
I
Googled
it
after
you
said
it
and
yep
it's
beat
yeah.
So
that's
one
up
as
an
MR
right
now,
there's
some
pretty
big
changes
there
and
then
there's
also
a
new
repo
for
the
marking,
svgs.
D
E
E
If
I
take
a
second
to
look
through
what
I
worked
on
so
this
iteration,
the
big
thing
that
I
worked
on
was
well
two
big
thing:
one
is
I
bumped
up
the
net,
which
is
a
quick
win
that
went
out
yesterday
in
the
afternoon,
so
that
should
be
merged
all
in
and
then
the
thing
that
I
worked
on
was
trying
to
get
the
to
work
on
the
navigation
lots
of
stuff
to
talk
about
there.
I'll
share
my
screen,
really
quick,
because
I
think
that's
or
else
start.
E
So
this
is
the
roll
up
analyzer
tool,
and
so,
if
I
look
at
the
entire
bundle
of
the
navigation,
the
JS
bundle
looks
like
this
looks
as
big
as
I
thought.
It
would
be
one
thing
that
I
wanted
to
call
out:
is
these
Json
files
the
way
they're
packaged
and
are
kind
of
taking
up
a
lot
of
stuff?
E
So
that
might
be
something
to
look
into
when
we're
using
contact
full
with
the
CMS
we'd,
probably
want
better
experience
to
handle
the
process
of
content
being
built
out.
The
reason
being
is
that,
if
content
changes
happen,
we
don't
need
to
push
up
like
new
changes
or
anything
along
that
end,
but
this
looks
mostly
right.
The
one
issue
that
I
do
have
right
now
is
that
our
slipper
CSS
styles
are
being
created
into
this
massive,
like
style,
about
CSS,
it's
1.7
Meg
me
medicine,
size
and
I'm,
trying
to
figure
out.
E
What's
up
with
that,
I
tried
somewhere
I'll,
just
call
it
out.
I
tried
using
your
link
with
these
Veet
updates
in
the
navigation,
just
try
to
see
like
what
it
would
look
like
and
it
time
to
load
slower
locally,
which
is
not
a
great
sign
trying
to
figure
out.
What's
up
with
that,
I'm,
not
sure
if
we're
processing
the
components
in
the
way
that
I
thought
we
were
in
the
navigation
project,
I'm
calling
them
as
essentially
like
the
payloads.
E
Are
you
know
the
three
components,
the
third
big
components
of
modules,
being
the
navigation,
the
footer
and
the
search
and
I
tried
to
set
it
up
as
a
plug-in
with
the
existing
navigation
plugin
file
that
we
have
and
I
mean
it
looks
like
it's
loading,
fine,
it
just
slower.
E
So
I'm
trying
to
figure
out
what's
the
big
like
1.7
Meg
CSS
files,
the
culprit
of
that
it
might
be
so
I'll,
try
to
figure
that
out
next
iteration
and
we'll
keep
working
along
that
stream
of
work
until
we
get
that
down
to
where
we
want
it
to
be.
E
That's
the
big
stuff
that
I
worked
on
I,
don't
think
there
might
have
been
a
couple
little
things.
If
I
had
my
branding,
I'd
lost
everything,
but
those
are
the
things.
I
worked
on,
I,
don't
know
who's
next
I
came
ill-frepared
with
the
board,
but
whoever's
next.
If
you
could
look
in
the
order
and
then
call
out
whoever's
next,
that
would
be
great.
Thank
you.
F
Yeah,
apparently
it's
me
I
also,
don't
have
the
board
open.
Oh
I
feel,
like
my
internet,
just
jumped
okay
yeah,
so
this
iteration.
Let
me
pull
up
my
stuff.
F
I
did
a
few
content
changes
for
the
Google
Cloud
next
page
and
the
devsecops
world
tour
Pages,
that's
kind
of
an
ongoing
back
and
forth
I,
also
added
a
few
pages
to
the
robot
stock
text
file
and
www
that
shouldn't
be
indexed
by
Google
and
excluded
them
from
our
site
map
in
buyer
experience
I,
finally,
merged
the
get
Ops
page
refresh,
which
had
some
new
components.
F
I
showed
that
last
Sprint
release
we
were
just
waiting
for
some
content
updates,
so
I
won't
show
it
again
other
than
that
I
did
a
big
component
audit
I
posted
about
it
in
slack,
so
you
can
all
go
check
it
out
there.
It's
in
figma
file
that
shows
kind
of
all
of
the
web
pages
that
exist
on
the
site
and
then
kind
of
how
I
visualize
each
of
their
components
being
grouped
and
which
one
needs
to
be
individual
components
versus
like
combined
components
with
different
properties.
F
So
you
can
take
a
look
at
that
there
and
comment
in
the
issue
that
I
linked
as
well.
If
you
have
thoughts
and
opinions,
I
added
a
integration
with
slack
for
our
blog
repo,
so
we'll
get
alerts
for
failures
in
Dex
alerts
and
other
than
that
I
think
that's.
It
try
to
catch
up
on
all
the
contentful
meetings
that
I've
missed
because
they
tend
to
like
booking
it.
During
the
two
hour
breaks
I'm,
not
in
the
office.
That's
it
for
me,
I!
Think
Miracle
is
next.
A
Okay,
this
iteration
for
me
was
all
about
collect
experiments
so
for
those
who
don't
know,
I
redesigned
the
free
trial
page
and
the
products
and
we'll
be
running
an
experiment.
Our
very
first
experiment
in
the
product
to
show
the
old
version
versus
the
new
version.
A
It's
been
slow
implementations
because
I
built
a
redesign
about
a
few
months
ago
and
in
between
that
we've
had
gitlab
16
launch.
So
some
of
the
style,
selectors
and
tags
that
I
use
to
redesign
were
deprecated
in
pajamas
to
keep
up
with
gitlab
16,
so
I
had
to
go
ahead
and
redo.
A
Those
I
did
have
a
meeting
with
growth
teams
collects
experts
because
there's
some
brand
new
errors
that
I
am
seeing
that
he
hasn't
seen
either
while
implementing
this
process
and
I
guess
my
last
blocker
is:
it
looks
like
there's
an
MR,
that's
in
the
process
of
being
approved.
It
looks
like
it's
in
the
tail
ends
of
being
approved
where
there
are
changes
to
the
logos
and
reassurances
on
the
free
trial
page
and
in
order
for
me
to
roll
out
my
experiment.
I
have
to
pull
in
those
new
changes.
A
We
don't
really
want
to
be
running
an
experiment
as
changes
to
the
free
trial
page
get
pushed
up
and
to
production,
and
that's
it
for
me
who
who
is
next?
That's
the
question
is
John
here.
A
G
You,
okay
in
this
iteration
I
work
on
in
translations
to
the
solutions
kubernetes
page
also
I
did
a
fix
in
the
Gita
code,
removing
some
duplicates
Google
tag
manager,
tax,
also,
I,
work
on
implementing
the
content
for
client
on
by
your
experience
and
removing
some
Uncle
sorry
I'm
fixing
some
anchor
leaks
that
we're
working
on
on
the
pricing
page.
The
most
important
issue
that
I'm
working
right
now
I
will
show
it
to
you
right
now.
G
Sorry
this
one
is
the
library
in
contentful,
so
in
this
case,
is
for
I
implemented
it
for
the
each
blog
post
that
we
have
in
this
contentful
space
and
also
for
the
archive
page
and
I'm
working
for
the
landing
page
of
the
blog
repository
I
will
show
you
real
quick
what
we
have
right
now
we
have.
We
can
have
a
lot
of
platforms.
G
Each
platform
can
have
like
a
different
environment
for
live
previews
in
this
case,
I
have
one
for
review
apps
and
one
for
localhost,
and
here
we
can
determine
which
Pages,
which
content
type
for
this
case
I
have
a
content
type
for
the
archive
and
a
content
type
for
each
blog
post
that
we
have
I'm
going
to
show
you
real
quick.
What
is
live?
Remover,
for
example,
this?
G
When
we
go
to
our
content,
to
edit
the
content,
we
can
go
to
the
open,
Live
preview
or
we
are
related
to
our
live
previewer.
In
this
case,
it's
an
iframe
to
our
application
and
we
can
change
the
content,
live.
G
So
it
is
really
useful
for
for
Content
for
for
the
content
team
in
order
to
add
some
data
in
the
in
content,
so
it
is
pretty
awesome.
I
have
also
the
archive
page
here.
B
Thanks
John,
that's
so
cool
I'll
try
to
go
fast.
Let's
make
you
only
have
10
minutes
left
right
and
share
my
screen.
So
first,
this
one
was
a
small
one.
It
was
just
changing
the
URL
for
a
Solutions
page
to
to
now
live
in
Solutions.
It
was
previously
in
features.
Then
I
had
one
of
these
content
Pages
the
the
event
Pages,
sorry
for
New
York.
So
a
lot
of
content
changes
as
those
become
available.
B
I
also
had
adding
a
video
to
to
the
dedicated
page,
which
is
here
now
and
also
did
this,
where
the
any
publishing
contentful
will
now
trigger
the
pipelines
in
both
the
blog
Ripple
story
and
buyers
experience.
So
if
I
go
in
at
Dot
and
publish,
then
a
new
pipeline
gets
triggered
currently
heavy
triggers
it
it's
his
token,
but
Megan
is
working
on
getting
a
decks
account
so
that
we
can
know
what
was
triggered
by
contentful
also
removed
some
some
components
from
the
from
the
devscopes
page.
B
It
looks
like
this
now
without
those
these
two
created
new
components
to
use
in
the
blog.
It's
these.
We
can
see
them
here,
there's
a
cool
thing
where
we
have
all
the
variants
of
the
component
in
the
quote.
So
if
I
go
to
content
and
quote
now
this
one
and
if
I
change
the
the
variant
so,
for
example
like
to
quote
and
publish
then
I
can
refresh
here-
and
the
quote
is
now
looks
like
this-
doesn't
have
the
image
and
has
like
different
styling,
so
it
can
be
switched
fast
from
from
contentful.
B
H
Thank
you
Mateo
or
my
part,
I
shipped,
a
Solutions
page.
You
can
see
my
screen
is
this
new
Solutions
analytics
and
insights
page,
which
is
pretty
cool?
Thank
you
very
much
to
Jess
and
Margaret
and
Laura
for
all
the
help.
Here
we
do
have
a
follow-up
issue
for
this
component
to
add
the
tabs
for
videos
and
blog
over
here,
but
this
this
is
live
already
and
also
I
ship.
This.
H
This
cups,
virtual
for
Dallas,
Page
and
also
I,
worked
a
little
bit
on
documentation
for
the
iterable
email
that
was
requested
and
all
the
contentful
reading
and
yep.
That
was
it
from
me
and
next
is
sorry.
He
I
think
it's
Margaret.
I
Okay,
I
will
try
to
be
first,
so
I
updated
our
Swift
type
on
our
search.
All
my
other
issues
are
still
happening.
They
are
going
on
I
started
to
try
to
fix
our
book,
found
on
a
specific
components
that
is
not
localizing.
Our
links,
I'm
struggling
with
it
I,
don't
know
why
the
bug
is
happening
and
it's
really
hard
to
try
to
fix
it,
because
it's
not
happening
locally
so
locally.
I
It's
working,
just
fine
I
spent
some
days
trying
to
fix
it
since
I
I
couldn't
I
started
my
AI
tab
and
this
dancer
SEC
Ops
page,
because
it's
a
huge
one,
I'm
working
with
Trevor
I
can
share
my
screen
really
quickly.
Okay,
so
this
is
the
page.
We
change
it
a
little
bit
the
design
here
in
the
header.
I
Also
in
the
text-
and
this
is
our
new
I-
would
say
like
it
used
to
be
the
test,
but
it's
also
type
navigation
and
yeah
I
finished
this
part,
so
I'm
going
to
change
the
content
and
that's
it
I
think
that's
it
for
me,
and
I
will
pass
back
to
Justin.