►
From YouTube: Digital Experience Sprint Planning 2021-02-01
Description
Sprint planning agenda: https://docs.google.com/document/d/1DFs47irmcL513pP5v-SPzjFypK7SDCR_dYSwSI7R3og/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
Hello
and
welcome
to
the
digital
experience
sprint
planning
meeting.
This
is
planning
meeting
seven
for
some
of
us,
but
we're
also
kind
of
coming
together
to
merge
our
design
system
and
cms
teams
kind
of
going
forward.
So
we'll
just
reset
this
number
at
one
and
yeah
talking
about
what
we
can
accomplish.
This
iteration
cycle
looks
like
first
up
on
the
list
is
tyler.
B
Yeah,
so
I
have
a
few
things.
First
up
is
just
some
wrap
up
from
the
last
sprint
I'm
going
to
fix
up.
I
got
the
vue.js
components
working
in
middleman
templating,
but
I
accidentally
double
exported
them,
so
I'm
just
going
to
wrap
that
up
and
fix
it
up
for
some
performance
reasons
related.
I
have
some
ideas.
B
I
don't
have
an
issue
for
this,
yet
I'll
make
it
after
this
meeting
about
setting
up
a
good
release
pipeline
so
that
we
get
our
versioning
under
control
in
in
a
good
space,
and
so
that
we
like
publish
the
right
number
and
we
kind
of
know
what
we're
working
with.
After
that.
I
have
another
thing
that
I
have
been
behind
on,
which
is
the
cloudinary
proof
of
concept,
I'm
going
to
add
the
cloudinary
integration
to
lauren's,
netlify,
cms,
proof
of
concept
repo
just
for
the
tool
exploration.
B
B
I'll
be
lauren's
already
got
a
rough
draft
on
migrating
roll
up
to
webpack
and
because
I've
been
very
much
in
webpack
land
the
last
week
or
so
I
will
jump
in
and
collaborate
on
that
with
her
and
then
my
last
thing
is.
I
got
a
little
like
too
clever
for
my
own
good
and
I
wrote
a
monkey
patch
for
our
middleman
site,
which
should
make
local
templating
development
better.
B
It's
not
fully
tested,
but
a
few
people
have
looked
at
it
and
like
it.
So
I'm
going
to
ship
that
so
people
can
start
using
it
and
find
maybe
some
of
the
sharp
edges
of
what
does
not
work.
The
nice
thing
is
it
doesn't
impact
build
pipelines,
it's
really
just
an
opt-in
development
setting.
So
I'm
going
to
ship
that
sometime
today,
once
people
take
another
look
at
it
and
I
can
add
some
documentation.
So
that's
it
for
me.
C
C
So
once
those
are
done
I'll
have
our
internal
team
review
them
and
then
that'll
go
out
to
rebecca
dodd
for
review
and
then
to
somebody
from
seo
and
analytics
to
take
a
look
at
it
and
I'll
also
be
working
on
just
a
one
functionality
that
didn't
make
it
into
the
this
past
few
iterations
of
the
cms
topic
pages
and
that's
the
on-page
sticky
navigation.
There's
an
issue
open
for
that
and
I'll
be
working
on
the
ui
and
ux
for
that
in
this
sprint
as
well,
and
that's
it
for
me.
D
Okay,
I'm
up
next.
For
this
sprint,
I'm
going
to
be
doing
admin
iterations
on
netlife
cms,
adjusting
the
block
order
and
then
adding
a
youtube
media
embed.
In
the
editor
we
will
be
enabling
the
netlify
cms
admin
on
production,
and
there
is
an
epic
associated
with
that-
a
host
of
issues,
as
you
can
see
there,
that
will
be
really
exciting
and
then
once
it's
turned
on,
I'm
going
to
be
working
with
tina
to
document
the
publishing
process
of
netlify
cms
in
our
handbooked.
E
Yeah
so
first
up,
I
have
a
ticket
to
or
an
issue
to,
update
the
spacing
on
some
of
the
pages
that
we've
already
updated
with
some
of
the
slippers
design
system,
like
the
enterprise
page
and
the
home
page
and
free
trial
page
and
giving
those
new
utility
classes
for
padding
and
margin
so
that
they
are
in
line
with
the
slippers
design
system
for
those
values.
And
then
I
have
a
bit
of
work
to
do
for
the
content.
E
A
So
I'll
be
doing
another
iteration
for
the
pricing
page
kind
of
looking
to
hopefully
get
us
into
a
stable
point
from
where
we
can
gather
you
know
some
metrics
without
the
page
constantly
changing
and
then
also,
basically,
we
were
unable
to
get
certain
parts
that
we
wanted
to
do
done
in
time
for
the
nbc
one.
So
this
kind
of
a
micro
iteration
and
get
those
feature
comparisons
grouped
up,
is
kind
of
where
we're
going.
A
Next
with
that
and
then
the
second
item,
I'll
be
working
on
is
kind
of
an
early
exploration
for
the
upcoming
commit
event,
and
I
just
want
to
get
us
thinking
about
that
early
because
there's
a
lot
that
goes
on
in
prep
for
that
it's
kind
of
a
lot
of
project
work.
So
I
want
to
see
what
we
can
do
in
the
cms.
E
E
It's
just
20
is
kind
of
doing
like
a
grayscale,
wireframe
or
template
for
partner
pages,
and
then
21
is
actually
doing
the
mocks
and
getting
them
visually
inspect
out
also,
hopefully,
while
I'm
doing
that
I'll
also
run
some
tree
testing
for
a
marketing
navigation,
make
sure
we've
got
everything
in
the
right
spot
and
if
that
happens,
to
go
well,
then
I'll
start
working
on
the
information
architecture
and
the
design
of
our
new
navigation,
and
that's
it
that's
it
for
me
so
hobby.
I
think
you're
next.
F
F
G
And
so
I
can
help
him
with
any
of
the
issues
that
we
just
discussed
and
continuous
work
on
bugs
and
figments,
but
to
get
things
to
work
responsibly,
especially
with
some
of
the
new
contributions
that
we
have
in
there.
And
so
that's
still
a
learning
curve
going
on
with
that
and
I'll
pass
it
to
sammy.
H
Thank
you
very
much,
so
one
of
the
things
I'm
going
to
be
doing
during
this
print
is
the
page
updates
to
some
of
our
solution
pages
that
was
reported
that
was
submitted
by
alicia,
rashid
about
vm
timezone.
So
I'm
gonna
be
making
some
update
to
this
content.
I'm
already
collaborating
with
them
to
get
some
information
that
we're
gonna
use
them
for
this
page
and
the
next
one
is
also
a
solutions
page
which
is
for
our
meeting
e
iec
page.
H
That
needs
some
more
information
that
was
suggested
by
some
customers
through
this
support
system.
That
way
that
we
use
for
the
ticketing
system.
I
think
so
there's
already
some
comments
on
that
and
I've
already
reached
out
to
them
so
that
we
can
quickly
do
justice
to
that,
and
the
next
thing
that
I'm
going
to
be
working
on
will
be
the
sm
page
mvc1.
H
The
smb
page
currently
is
still
blocked
for
the
design
that
I'm
going
to
be
getting
around
february
5,
and
I'm
looking
forward
to
finishing
this
by
february
chef,
which
will
be
around
the
end
of
our
sprint
and
the
next
one
is
our
partner
overview
page.
It's
still
blocked
due
to
design
from
our
ux
designers
too,
but
I'm
going
to
be
working
on
that
during
this
point.
H
Lastly,
is
from
our
cms:
there
is
a
issue
convexina,
which
is
just
the
spacing
between
our
video
and
text,
components
on
some
sections
of
the
page
and
that
will
be
easily
fit
today,
because
what
we
are
doing
is
to
ensure
that
a
lot
of
content
are
very,
very
consistent
with
our
design
system.
So
if
there
is
a
video,
there
should
be
some
required
level
of
space
or
padding
between
the
elements,
and
it
should
affect
every
other
single
page
on
the
design
system,
every
other
topics
pages.