►
From YouTube: Digital Experience Iteration Plan Sync - 6/21 to 7/2
Description
Digital experience planing sync for the iteration starting on 6/21/21 and ending on 7/2/21
Iteration planning doc:
https://docs.google.com/document/d/1uFw2snKuBlt2VirP5mjMvCr66HD7hOAB6QrXaElBZQE/edit?usp=sharing
A
There
want
some
work
done
on
those.
We
will
be
pushing
to
launch
the
commit
landing
page,
which
is
looking
really
good
ready
to
go.
Also
push
out
handbook
documentation
for
the
commit
landing
page.
How
to
to
work
with
that
network.
Cms
push
out
the
partner
page
for
red
hat
and
work
on
the
solutions
template
build
in
slippers,
and
I
have
an
undesignated
amount
of
points
for
that.
But
I'm
going
to
try
to
get
a
head
start
on
that
and
I'll
pass
it
over
to
nathan.
B
Yep,
so
we're
going
to
swap
out
the
homepage
banner,
I
think
the
current
one
ends
june
29th
and
the
new
one
will
start
early
july.
I
believe
and
that's
the
commit
banner
and
that's
the
events
page,
adding
in
the
url
adding
a
filter,
so
you
can
filter
by
region,
location
whatever
adding
an
faq
heading
to
pricing.
Page,
that's
just
a
quick
one!
B
A
blog
template
links
are
not
working
which
could
have
been
from
something
I
did
last
week
so
I'll
dive
into
that
and
try
and
get
that
fixed
and
then
there's
another
link.
One
that's
to
be
able
to
target,
to
links
that
are
hidden,
so
within
the
faq
section,
be
able
to
open
it
up
and
link
to
it
and
then
I'm
going
to
start
an
investigation
on
our
features,
topic
solutions.
So
these
are
part
of
the
okr,
and
so
I
took
over
for
brandon.
C
Okay,
thanks
I'm
going
to
continue
work
on
the
comparison
pages,
so
that
means
wrapping
up
some
of
the
user
testing
sessions
that
I've
got
going
on.
I
saved
two
points
to
implement
some
design
updates
if
the
user
testing
reveals
that
they're
needed-
and
I
also
have
still
have
to
create
a
mock-up
for
a
single
tool
versus
the
platform
partners
for
comparisons,
I
saved
a
point
to
support
for
the
commit
event
launch,
which
I
think
is
happening
this
week.
Maybe
next
and
I
also
saved
a
point
for
rescuing
the
solutions.
C
Cms
template
work
specifically
regarding
the
public
sector,
page
commitments
that
we
made
and
that's
it
for
me
tyler,
who
is
absent.
I
think
I
can
read
for
him
he's
on
the
get
lab
14
release
right
now.
He
noted
here
homepage
promotion,
landing
page
and
revisions
from
nmr,
that's
linked
in
this
document.
C
One
point
for
slippers,
navigation
deployment,
two
points
for
research
into
pipeline
times,
trending
upwards,
four
points
to
build
the
comparing
graphic
components
that
I
just
talked
about
and
then
two
points
for
interviewing
and
training
and
next
is
jess
who's.
Also,
not
here
I'll,
just
keep
going
she's,
also
absent
for
get
lab
14
release,
which
is
what
she's
working
on
home
page
hero
takeover,
as
well
as
the
release
of
the
landing
page.
And
then
she
saved
eight
points
for
ins.
The
install
page
mvc2
that
she's
working
on.
D
D
It's
just
like
weird
issues
happening
with
the
css
and
specifically
with
the
tailwind
typography
package,
and
so
we're
going
to
go
figure
that
out,
while
I'm
in
there,
I
figured
it'd,
probably
be
a
good
idea
to
do
things
like
updating
our
storybook
dependency
itself,
looking
out
for
weird
blog
in
terms
of
when
you're
launching
storybook,
like
the
things
that
are
being
outputted
out
since
I
know
that
our
build
times
for
local
development
for
storybook
has
gone
up.
So
just
doing
little.
Things
like
that,
I
have
five
points
set
for
navigation
work
related
things.
D
D
This
is
important
to
start
having
scoped
work
for
some
of
these
things,
and
I
feel,
like
it'd,
be
a
good
idea
for
me
to
get
that
now,
especially
that
I'm
finishing
up
such
a
big
project,
and
I
want
to
start
clearing
some
of
those
out,
especially
some
of
those
little
ones
that
start
I've
been
creeping
up
for
a
while
now,
so
that's
it.
For
me
up
next
is
stephen.
E
Yeah
I
haven't
committed
to
the
full
point
allocation
of
this
just
due
to
availability
of
being
on
and
off
the
road,
and
but
what
I
will
commit
to
before
I
go
is
completing
the
features
page,
the
past
of
the
content
team.
So
we
had
a
chat
last
week
with
free
and
our
approach
for
this
is
to
break
it
out
into
sections
and
provide
them
with
a
template
to
then
create
content
for
that,
because,
right
now,
it's
just
too
much
of
a
mess
to
even
comprehend.
E
A
lot
of
it
is
old,
so
it
needs
to
be
deprecated.
There's
things
that
just
need
to
be
taken
out
so
design-wise,
it's
in
a
good,
it's
in
a
good
state
and
we'll
bring
it
up
again
with
some
of
the
ux
team
to
go
over
some
of
the
conventions
that
we're
going
to
adopt,
because
it's
very
new
and
then
begin
work
on
the
topics
landing
page
as
well.
I've
already
had
a
look
at
this
and
sort
of
figuring
out
what
we
can
do
from
existing
templates.