►
From YouTube: Digital Experience Release Video - May 20, 2021
Description
Sprint Release Doc:
https://docs.google.com/document/d/1kMNiUF2UDuSrMDuzLyRi8OEhVxry_MJoYi38RmmWafY/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
sprint
planning
for
the
digital
experience
team.
Oh
sorry,
not
sprint
planning
sprint
retro.
So
this
is
what
we
released
on
the
sprint
ending
today
may
20th,
and
it
looks
like
first
up
is
tina.
B
It's
me
sprint
release
retros
later
all
good,
I'm
first,
I
take
a
deep
dive
into
okay,
our
planning,
there's
nothing
really
fun
to
look
at
here.
I
just
tried
to
get
up
to
date
on
some
bigger,
some
of
the
bigger
cross-functional
asks
and
prioritizing
that
work.
I
listed
some
of
the
new
epics
that
have
bones
mostly
for
visibility,
as
some
of
them
relate
to
some
of
your
other
okrs.
B
The
top
two
are
what
I'll
be
focusing
on
next
sprint
cycle
which
we'll
talk
about
later,
but
that
is
the
product
footer,
sorry,
the
solutions,
pubset
cms
template
and
the
product
footer
yeah.
So
that's
it
for
okay
planning.
I
also
added
a
page
to
the
handbook
to
start
kind
of
collecting
some
figma
guidelines
and
naming
conventions.
B
I
imagine
this
page
is
going
to
keep
growing,
especially
if
we
start
doing
some
figment
design
101s.
We
can
maybe
add
links
to
those
there
and
I
opened
up
a
collaboration,
improvement
issue
just
to
continue
the
conversations
about
team
collaboration
that
we
started
during
our
kickoff.
That's
it
for
me,
and
next
tyler.
C
Yeah,
so
I
don't
have
most
of
my
things
are
unshowable
because
they
have
to
like
live
in
a
dev
environment,
so
I'll
just
go
through
them
here
fix
up.
There
was
a
canonical
url
that
was
incorrect,
had
some
double
slashes
so
fix
that
up
quickly,
barker
and
I
worked
on
the
template
assembly
follow-up
with
some
guidance
from
tina.
Thank
you
very
much
and
we
wrapped
that
really
early
on
and
then
we
were
able
to
move
on
into
all
the
integrations
from
slippers
commit
components
into
the
www
repo.
C
So
I
got
the
speakers.
Video
benefits
blocks
all
integrated
in
there,
and
I
know
we've
got
a
bunch
of
others
that
came
through
as
well
ran
into
a
thing
when
we
had
done
our
blog
updates
months
ago.
We
didn't
carry
over
one
of
the
conditionals
in
the
front
matter
to
be
able
to
disable
comments
which
turned
into
a
problem
so
fix
that
added.
C
I
went
over
this
in
show
and
tell
wrote
a
little
script
for
to
get
like
a
pulsar
the
activity
of
commit
history
in
our
relevant
directories.
C
We
also
had
some
breaking
stuff
in
slippers
with
some
image
dependencies,
which
I
patched
up
at
least
temporarily
for
slippers
components
and
then
the
big
one
that
I'm
working
through
today,
but
it's
like
basically
ready
to
go,
is
content.
Team
is
disabling
the
unfiltered
yeah
months
ago,
laura
the
blog
thing
was
like
january
or
february
months.
I
don't
know
if,
if
recording
sees
the
chat
but
laura
asked
months
ago
and
we're
deprecating
unfiltered
blog,
so
we've
got
like
a
linter.
C
Now
that,
like
checks,
all
the
blog
posts
and
says
hey,
is
there
a
new
blog
post
passed
like
on
or
after
the
20th,
and
does
it
use
the
unfiltered
category
if
so
fail
the
pipeline?
So
that
is
yeah
gonna
launch
shortly
and
up
next
is
happy.
D
So
I
worked
with
trying
to
get
some
of
our
slipper
spacing
to
align
with
sigma.
This
is
its
own
deal
essentially
like
a
past,
mr
that
we
made
where
we
changed.
The
way
that
we
named
different
utility
classes
and
relating
to
our
root
m
like
how
all
that
works,
essentially
that
only
works
for
margin
and
padding
utilities
and
we're
trying
to
gain
alignment
for
that
same
thing
for,
like
other
utilities,
such
as,
like
top
left
right
background
images,
translates
what
not
trying
to
get
all
of
the
spacing
to
be
consistent.
D
This
will
probably
be
released
at
the
beginning
of
next
sprint,
slash
iteration
cycle,
just
because
we
want
to
have
time
for
essentially
checking
that
all
of
this
actually
works
as
intended.
We're
probably
gonna
like
end
up
setting
a
alpha
version
of
a
slippers
version
for
this
and
testing
it.
But
again,
I
I
personally
feel
better
doing
it
at
the
end
at
the
beginning
of
next
sprint.
For
that
reason,
to
not
feel
like
the
pressure
of
we
need
to
release
something
by
this
day.
So
reasoning
for
that
now,
I've
worked
been
working
on.
D
Navigation,
that's
set
to
be
released
as
soon
as
possible.
Essentially,
this
is
the
slippers
mr4,
and
this
is
the
about
gitlab.
Mr
that's
currently
work
in
progress.
I
imagine
that
it's
gonna
take
a
second
to
get
all
of
those
little
kinks
worked
out.
D
I'm
also
scoping
this
works,
so
essentially
it's
only
we're
only
promising
that
this
navigation
will
be
a
first-class
citizen
for
anything
that
lives
within
the
primary
navigation
and
big
pages
such
as,
like,
like
home
blog,
essentially
very
like
public
facing
changes
and
there's
like
a
lot
of
technical
details
that
we
can
get
into
about
like
the
how,
but
you
can
find
those
details
in
the
mr,
if
you're
interested.
D
D
I
talked
about
this,
I
believe
the
beginning
of
last
week
about
like
what
are
things
that
we
can
do
to
make
sure
that,
like
the
agency
process
flows
smoothly,
and
I
think
that
there
was
an
ebook
that
I
read
that
I
just
want
to
like
mind,
dump
into
it
and
condense
it
down
to
have
like
you
know,
a
good
set
of
like
this
is
what
it
means
for
someone
in
digital
experience
team
to,
like
you,
know,
listen
to
someone's
requests
and
also
not
be
people,
be
you
know,
people
pusher
being
pushed
around
by
other
people,
etc.
D
I
just
wanted
to
have
like
something
like
that
in
there,
especially
because
that
was
something
that
I
think
happens
for
our
team
specifically,
and
I
want
to
make
sure
that
our
team
has
a
guardrail
set
in
place
to
make
sure
that
they
are
doing
the
work
that
benefits
the
entire
organization.
That's
it
for
me,
up
next
is
jess.
E
Jess
is
another
call,
so
I'm
going
to
speak
on
her
behalf,
and
so
next
iteration
of
the
pricing
page
is
the
talk
to
an
expert
call
out
for
those
who
might
prefer
speaking
to
a
sales
rep
when
they
can
make
an
approach.
So
there's
links
to
figma
and
the
ux
issue
there
and
then
bonus
research,
product,
slash,
devops
life
cycle,
page
usability
testing.
So
there's
a
highlight
reel
and
an
issue
to
go
along
with
that
and
I'm
up
next
and
very
similar
to
tina
earlier
on
just
sort
of
deep
in
okr
stuff
planning
that
out.
E
So
I
filled
out
some
child
epics.
A
lot
of
this
is
subject
to
change,
especially
after
the
meeting
we
had
this
morning,
which
is
the
prioritization
of
the
top
15
and
ferraro
okay
or
myself
and
brandon.
So
we've
split
that
out
and
we're
beginning
to
like
categorize
and
prioritize
different
pages.
So
we're
splitting
this
workout
as
we
go
along
and
next
up
is
laura.
F
Yeah,
similar
to
what
tyler
was
saying
earlier,
I
did
a
bunch
of
work
for
the
events,
template
that
isn't
really
showable,
except
in
a
local
environment.
So
I
completed
the
partners
block
so
a
list
of
sponsors.
The
announcement
block
the
countdown
and
the
header
block
is
code,
complete,
which
shows
all
three
header
variations
with
an
image
with
a
video
or
with
neither
of
those
and
then
number
24.
I
moved
oh
yeah,
I
moved
the
slippers
components
into
a
shared
directory.
F
Javi
did
a
really
cool
generator,
mr
last
iteration
or
sprint
that
will
put
new
components
in
the
same
directory.
So
we'll
have
a
directory
named.
You
know
header
and
then
the
pieces
within
it
so
yeah.
I
just
put
this
in
there,
so
you
kind
of
get
a
visual
of
what
I
mean
before
there
was
like
a
folder
for
like
the
checkbox
view
component
and
then
a
folder
for
the
checkbox
story.
F
Now
they're
just
going
to
live
in
the
same
folder
called
checkbox,
so
it's
just
meant
like
pretty
much
just
touching
every
file
and
moving
in
and
making
sure
all
the
paths
remained
correct,
so
that
was
split
into
two.
Mrs
last
week,
and
then
I
made
a
few
handbook
updates
as
well.
I
added
to
the
digital
experience
team
a
little
blurb
about
code
freezes.
F
This
came
up
last
spring
retro
that
we
were
worried
about
now
that
we're
trying
to
get
more
people
to
contribute
to
the
site,
making
sure
that
we
have
kind
of
two
week
setting
period
for
any
changes
that
we
make
in
case
we're
doing,
testing
or
usability
on
any
of
that
and
some
guidelines
for
people
who
want
to
contribute-
and
I
added
a
piece
to
the
handbook
just
now
about
pages
in
slippers
what
has
been
touched
with
slippers
css,
what
has
been
built
since
the
first
in
storybook,
so
that
mr
should
be
merged
in
and
we'll
kind
of,
have
a
running
list
of
things
that
use
slippers
and
if
people
think
of
it,
as
they're,
building
stuff
out
with
slippers.
G
All
right
so
finished
up
the
event
assembly
in
slippers
and
just
patched
up
the
the
copy
block.
So
if
you
can
go
ahead
and
show
that
whoever
is
yeah-
and
this
opens
up
our
events
template
in
slippers,
which
is
good
it'll
carry
through,
but
this
is
what
we
like
everything.
That's
in
the
side
that
says
events.
This
is
everything
the
team
has
been
building
over
the
last
iteration.
G
G
You
got
it
all
the
way
templates
yeah
there
you
go
yeah,
here's
our
events,
template-
and
this
is
everything
the
entire
team
is
pulled
together
to
build
and
we
had
to
build
in
slippers
first,
and
so
this
is
everyone,
and
now
we
go
hop
back
to
the
agenda
and
then
the
next
one,
the
whole
team
worked
on
actually
building
these
suckers
in
to
the
dub
dub
dub
repo,
and
here
you
can
see
our
actual
erb
components
and
for
this
cycle
this
is
our
actual
template
and
for
this
cycle
I
added
the
copy
and
image
block
the
event.
G
Cta
event,
block
cards,
the
connect,
the
block
lists
and
the
heading
component,
which
I'm
going
to
patch
up
today,
and
that
was
really
cool.
It
just
kind
of
shows
the
the
process
where
we're
at
right.
Now.
Everyone
did
a
really
good
job
just
crushing
through
that
we
had
some
blog
seo
errors.
We
added
I
added
a
category
paginator
a
few
weeks
ago
and
it
was
putting
the
same
title
and
description
on
each
of
the
black
blog
category
pages
that
were
paginated.
G
So
you
can
see
down
oh
yeah,
there
you
go!
So
if
you
go
to
the
top,
I
think
it
says
in
the
description.
Oh
it
doesn't.
It
now
just
says
like
you're,
on
page
one
of
four
of
the
news
category
page
and
or
page
three
or
four,
and
that's
going
to
help
with
our
seo
results
added
the
unfiltered
blog
post
badge
to
our
all
of
our
unfiltered
blog
posts.
G
So
it's
that
cool
little
purple
box
down
there
so
added
that
in
slippers
and
then
added
it
to
our
blog
post,
template
and
another
quick.
Mr
just
to
add
some
link
styling
to
our
in-text
links.
So
you
can
see
in
the
text
here
now.
If
it's
a
link,
it
has
a
the
under
underline
and
then,
if
you
hover
over
it,
it
changes
colors,
and
so
that
was
the
first
iteration
for
these
install
pages
and
then
I'll
be
working
to
add
that
more
globally
and
that's
it
for
me.