►
From YouTube: Digital Experience Release video - June 3, 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
Hi,
everyone
welcome
to
the
digital
experience,
teams,
sprint
or
iteration
release
video
going
over
what
we've
done
over
the
last
two
weeks
today
is
june,
2nd
and
I
believe
up
first-
is
lauren
barker.
B
Okay,
so
first
thing
we
did
was
we
implemented
a
new
authorization
for
nullify
cms?
We
did
client-side
implicit
grant
to
pkce
and
it
went
really
smooth,
and
that
was
exciting.
B
The
second
thing
is
we
added
inline
svg
extension
for
middleman,
and
this
is
a
little
middleman
extension
that
lets
you
easily
call
in
svgs
without
pasting
the
code
into
your
template,
and
it's
going
to
be
really
allow
us
to
use
svgs
more
efficiently
through
out
the
repo
this,
mr,
I
changed
a
bunch
of
the
the
icons
but
go
check
out
the
mr
and
then
look
for
more
use
of
that.
B
I
did
a
quick
patch
to
update
the
header
tags
on
our
comparison
pages
to
use
h1
and
h2
tags
instead
of
nothing
so
that
git
lab
versus
github
at
the
very
top
before
that
was,
I
think,
just
a
span,
but
now
it's
an
h1
which
is
going
to
really
help
with
seo,
and
that
was
just
a
nice
little
quick
patch
did
lazy
loading
off
screen
images
for
our
blog
category
pages,
just
a
quick
native
lazy
load.
B
So
if
you
scroll
down,
it
will
load
the
the
image
as
the
page
loads,
but
these
are
short,
so
you
won't
really
notice
it,
but
it's
there
makes
it
load
a
little
faster
and
started
step
five.
Oh
no.
Four
we've
got
a
there's,
a
little
content
thing
on
the
install
ce
or
ee
page,
where
there
used
to
be
a
a
list
under
that.
Why
use
enterprise
edition
now
we
have
bullet
points
instead
of
it
was
just
mixing
with
the
content,
so
it
didn't
kind
of
mixed
up
users.
B
So
I
just
quickly
added
the
bullet
points
there
and
started
step
five
for
the
event
template,
so
that's
connecting
it
to
netflix
cms,
I'm
about
60
there
and
tyler
finished
step
four.
So
putting
all
our
components
together
and
making
it
available,
which
is
very,
very
exciting
and
nathan
is
up
next.
A
I
don't
believe
he's
here.
I
can
chat
about
what
he
was
working
on
yeah
he
added
a
banner
to
the
home
page,
so
at
the
very
top
you'll
see
remote
by
gitlab
june,
29th
is
running
for
the
whole
month.
So
that's
a
nice
addition.
He
also
added
himself
to
a
team
page
or
orc
chart
and
our
digital
experience.
Handbook
sid
asked
for
some
updates
to
the
pricing
page.
So
I
believe
nathan
was
working
on
this
with
jess
and
made
some
quick
updates
to
maybe
the
control
group.
A
Maybe
the
test
the
a
b
test
group-
I'm
not
quite
sure,
and
then
there
was
someone
pointed
out
that
there
was
broken
markup
on
the
continuous
delivery
page.
So
this
page
previously,
where
all
the
links
are
were
showing
like
the
hammel
like
percent
side,
a
whatever
gobbledygook,
so
he's
fixed
all
of
those
links.
So
that
page
looks
a
lot
better
now
and
working
on
fixing
the
install
page
there's
a
bit
of
a
jumpy
scroll
happening
and
that
javascript
that
handles
that
was
written
like
four
years
ago.
A
C
I
love
that
word.
Gobbledygook.
Sorry,
just
couldn't
stop
thinking
about
it,
while
you're
talking
so
my
priority
for
this
iteration
cycle
was
to
create
a
template
for
the
solutions.
Page
cms,
I
selected
a
collection
of
blocks
that
mostly
already
exist
anyways
that
can
be
used
to
assemble
various
solution.
Page
layouts,
I
also
created
a
mother
template
which
holds
all
the
blocks
so
like
the
other
cms
templates,
we
created
if
a
block
isn't
needed,
it
won't
display.
C
And
lastly,
I
created
three
pressure
tests
to
see
how
the
mother
template
can
be
used
to
create
existing
pages,
one
of
which
is
the
updated
pub
sec
page
public
sector
page,
which
is
one
of
our
okr
epics.
C
So
that's
it
for
the
solutions
stuff.
I
also
narrowed
down
a
link,
a
list
of
links
for
the
product
footer.
So
that's
some
work
that
is
going
to
be
rolling
into
next
iteration.
So
for
this
version,
we're
going
to
link
to
home
resources,
blog
docs,
contribute
support
and
the
pricing
page
and,
lastly,
the
last
item
not
much
to
show
there
but
tyler,
and
I
went
heavy
with
some
planning
last
week
on
the
compare
page
project
which
is
kicking
off
next
iteration.
C
Some
work
has
already
started
this
iteration
behind
the
scenes.
We
gathered
some
info
and
started
breaking
out
the
epic
into
smaller
issues.
That's
it
next
is
jess.
A
And
the
first
thing
there
is
this:
what
we're
calling
iteration
two
of
the
pricing
page
is
a
request
from
sid
I'd,
say
mostly
copy
changes
in
an
attempt
to
create
a
more
of
a
visual
hierarchy
as
well,
and
then
laura
had
mentioned.
Nathan
worked
on
some
things,
we
kind
of
so
post.
What
you
see
here.
A
There
were
additional
changes
to
the
test
and
this
got
implemented
and
are
running
right
now
and
then
the
next
thing
is:
oh
yeah,
the
reusable
banner
component
for
to
direct
people
to
the
free
trial,
page
something
that
we're
going
to
plan
to
put
on
many
pages,
and
hopefully
you
know
just
a
little
blurb
to
let
people
know
that
it
exists
and
we'll
send
them
away
to
the
page
if
they're
interested
in
it
and
then
the
next
thing
is
oh
yeah,
the
research.
A
So
I
had
been
working
on
some
usability
research
for
the
sas
free
trial,
signup
flow.
This
is
like
kind
of
done.
We
paused
it
to
move
on
to
some
other
things,
but
we
were
able
to
get
four
tests
out,
got
some
really
great
feedback.
I
got
all
my
observations
on
the
ticket
there.
A
I've
been
working
with
sam
on
that
and
he's
gonna
like
take
it
away
from
there
and
just
you
know,
clean
up
the
form
as
best
as
possible
and
then
the
last
thing
is
the
contact
sales
update,
and
this
is,
I
would
say,
it's
not
a
huge
ux
update.
It's
definitely
a
ui
update,
so
it's
not
tweeted
somewhere
from
our
current
page.
Some
copy
changes
for
sure,
but
generally
just
kind
of
like
simplifying
that
page
and
making
it
a
little
bit
better.
D
Oh,
that's
me:
hello
turned
on
slippers
css
within
the
head,
which
means
that
slipper
css
is
accessible
at
any
page
within
www,
which
I
think
will
help
us
get
stuff
out.
There
was
some
changes
with
like
what
not
over
the
weekend
that
laura
and
nathan
like
were
able
to
pick
up
about
like
certain
different.
I
don't
even
know
what
was
happening
like
different
packages
for
slippers
being
used
in
different
nodes
in
different
areas.
So
thank
you
for
figuring
that
out.
D
I
did
some
work
with
the
component
generator
that
we
were
using
within
slippers.
I
found
like
some
gaping
bugs
with
it,
so
I
went
ahead
and
fixed
that,
and
I
just
to
remind
people
how
to
use
it.
Just
I
put
it
here
just
to
be
like
very
explicit.
I
made
this
like
big
quality
of
life.
Change
for
making
commits
to
slippers
previously
left
hook
would
run
a
pre-commit
hook
that
would
run
prettier
on
all
files
on
slippers
that
takes
forever.
D
Now
it's
only
running
on
stage
files,
meaning
that
like,
if
you
only
change
three
files,
it'll
only
check
the
printer
config
will
only
check
those
three
files
for
changed,
like
style
whatnot,
instead
of
checking
the
entire
directory,
which
will
help
keep
the
the
process
of
waiting
for,
like
you
know,
if,
if
you've
worked
with
slippers,
you
you'll
know
it'll
hang
for
like
three
or
four
seconds
so
now
it
should
be
like
almost
instantaneous
removed,
deprecated
navigation,
partials
and
I
cleaned
up
relevant
code.
D
This
is,
I
think,
like
almost
done
or
should
be
done.
I
there
was
like
some
random
issue
with
it,
but
essentially
we're
gonna
go
through
and
just
clean
up
all
like,
like
navigation
related
stuff
and
trying
to
get
all
of
this
all
synchronized,
so
that
when
we
do
switch
the
navs,
it's
all
like
gonna
all
change.
D
When
I
tried
doing
the
exploration
of
it,
there
is
like
a
lot
of
the
it
changes
in
some
pages
and
not
others,
and
so
this
was
like
kind
of
like
a
way
of
trying
to
rectify
some
of
that
and
make
it
make
it
so
that,
like
when
the
header
partial
in
www,
does
get
updated,
it'll
affect
the
entire
site,
not
just
like
some
pages
and
yeah,
so
much
better
with
that,
I
believe.
That's
it.
For
me,
next
up
is
laura.
A
Yeah,
so
I
had
done
a
quick
change
to
the
slippers,
radio
and
check
boxes.
Jess
had
come
up
with
some
new
designs
where
the
the
stroke
of
the
line
is
a
little
bit
thinner.
The
disabled
styles
keep
some
colors
in
them
and
stuff,
so
I
made
those
updates
just
so
that
we
could
release
a
new
version
of
slippers
and
fix
that
bug
that
javi
had
alluded
to
earlier,
so
they're
very
minimal
change
but
they're
there.
I
also
did
a
few
home
page
requests
added
a
new
video
to
the
video.
E
A
I
updated
the
install
page
to
have
colored
logos
so
that
they're,
like
more
visually
different.
You
can
pick
out
exactly
what
you're
looking
for
so
that
was
maybe
last
week
and
then
the
biggest
thing
I've
been
working
on
is
the
free
trial
page
update.
We
have
a
new
design
for
the
entire
page,
so
working
on
that
and
it's
not
ready
yet,
but
it's
coming
and
then
next
is
stephen.
E
Yeah
mine
are
pretty
boring,
just
a
lot
of
issues
that
I've
created
from
the
parent
epic
and
tried
to
fill
out.
Some
of
them
so
filled
out
the
main
one,
which
is
features
which
is
top
of
myself
and
brandon's
priority
so
trying
to
get
a
head
start
on
that
for
when
he
returns
from
vacation,
so
that
we
can
begin
to
divide
and
conquer
and
set
what
we
want
for
nbc
and
yeah.
That's
me
pretty
pretty
basic
and
pretty
straightforward,
very
boring.