►
From YouTube: Digital Experience Release Video - May 6, 2021
Description
Sprint Recap/Release Video Doc: https://docs.google.com/document/d/1I9Th3Q-AakOkE_-pmNtEzwwMDSqYKF5Je2etGdPTovk/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,
we're
the
digital
experience
team
in
inbound
marketing.
This
is
our
release,
video
for
the
sprint
ending
today
may
6th
2021.,
I'm
first
up,
we
completed
an
iteration
of
the
install
page.
There
are
still
some
issues
associated
with
this
page,
and
this
page
is
one
of
our
top
pages
that
we'll
be
looking
at
improving
for
q2,
but
for
now
this
iteration
is
complete,
laura
who
built
the
page.
I
don't
know
if
you
want
to
add
anything.
B
A
Cool
also,
I
closed
out
the
prospects
to
free
trials,
okr
and
created
a
short
video
summarizing
that
the
work
that
came
out
of
that,
so
that
was
a
customer
journey
map
and
some
some
kind
of
visualization
of
some
metrics
that
we
pulled.
And,
lastly,
for
me
I
wrapped
an
iteration
of
the
card
ux
that
includes
ui,
updates
usage,
documentation
and
assigned
out
some
issues
for
updates
and
fixes.
C
Yeah
so
tyler
worked
on
closing
some
of
the
view,
3.0.0
migrations
and
there
was
a
couple
incidents.
He
was.
This
resulted
in
creating
an
mr
to
consolidate
some
of
the
documentation
for
that
stuff
in
the
handbook
and
because
of
the
migration
there's
stuff
that
needs
to
be
worked
on
for
the
git
pod
integration
as
well.
For
those
who
don't
know,
gitpod
is
like
a
situation
where
it
lets.
C
You
run
like
a
browser
version
environment
of
the
dub,
dub
dub
website,
and
so
obviously
changing
the
ruby
version
of
that
needs
that
I'm
trying
to
think
of
the
word
the
environment
to
that
needs
to
be
updated
with
review.3.0
as
well.
So
that's
something
that
he
was
working
on
the
event
template
navigation.
C
He
created
a
merge
request
for
that
which
will,
I'm
sure,
will
be
merged
shortly.
He
also
wrote
a
blog
post
about
the
slippers
blog
template.
He
didn't
say
to
share
this,
but
I
think
I'm
going
to
share
a
little
bit
of
it.
I
think
doing
this
structure
of
like
taking
some
of
his
thoughts
and
writing
them
down.
C
Not
only
helps
give
outside
parties
insight
into
like
what
he
did,
but
also
give
us
on,
like
especially
some
of
the
other
engineers
on
the
team
insight
into
like
why
he
did
the
things
that
he
did.
That
is
more
conducive
and
easier
to
follow
through
in
like
a
block
format.
So
I
just
wanted
to
call
that
out.
I
was
looking
at
this
like
before
our
meeting
started,
laura
also
called
out
that
she
also
likes
comb
through
some
of
this
stuff.
C
So
I
think
stuff
like
this
is
something
that,
if
you
do
something
complicated,
a
blog
post
might
be
a
really
good
way
of
articulating
some
of
that.
He
had
a
documentation
about
how
to
add
markdown
in
the
docs
for
different
slippers
component,
and
he
added
some
of
that
into
my
generator,
mr
that
I
can
talk
more
about
in
my
section,
but
yeah,
just
making
sure
that
people
have
insight
into
how
to
write
that
documentation,
because
it's
not
super
clear
in
the
docs.
C
B
B
B
It
takes
a
village,
it
looks
great
cool,
so
onto
brandon's
things,
brandon
has
been
working
on
a
b
test,
a
lot
of
a
b
testing
and
so
he's
added
some
engineering
documentation
in
the
handbook,
so
that
link
just
shows
a
handbook
page
with
how
to
run
a
a
b
test
so
that
we
can
all
follow
along
which
we're
using
launch
darkly.
For
so
that's
great
and
then
there's
also
an
mr
checklist
that
we
can
go
along
once
we
create
a
b
tests.
This
link
might
yeah.
B
I
I
was
having
trouble
opening
this
link
as
well,
but
it
will
find
it
and
it
does
exist,
and
then
the
retro
template
also
for
a
b
testing.
So
yeah
there's
a
checklist
here
for
making
sure
we
run
through
these
after
a
b
testing
and
then
yeah
social
media
open
graphs.
So
whenever
we
make
new
pages
and
we
want
to
have
a
twitter
image
or
something
like
that
for
social,
this
is
how
external
people
outside
of
our
team
can
request
those.
B
So
there's
a
little
template
update
there,
and
then
he
also
worked
on
the
faq
accordions
on
the
pricing
page.
I
think
yeah
at
number
14.,
so
he's
been
working
on
that
with
release
on
monday
partner
pages.
This
is
some
stuff
that
have
been
left
left
behind
from
sami,
so
aws
is
released
and
we're
working
on
releasing
ibm
next
week,
and
then
next
is
me.
B
As
mentioned
before,
we
worked
on
the
install
page
and
did
a
few
iterations
on
that,
and
then
we
also,
I
built
out
a
remote
work
landing
page,
so
that
is
live
and
that
went
out
tuesday
of
last
week.
I
think
so
that
one
you
can
show,
I
don't
have
too
much
else
to
show
but
yeah.
So
this
is
an
upgrade
from
the
2020
report.
B
We
now
have
the
2021
version
with
these
pull
quotes
and
yeah
partner
cards,
which
are
using
slippers
also,
which
is
cool,
and
then
I
also
tyler
had
pointed
out
that
I
should
refactor
our
event
countdown
number
18
there
and
so
doing
that
I
used
some
life
cycle
hooks,
which
I'd
only
ever
done
in
react.
So
doing
an
interview
was
kind
of
cool
and
that's
it
for
me,
and
next
is
javi.
C
C
C
I'm
going
to
open
that,
mr
because
it's
kind
of
interesting
for
the
developers
on
this
side
of
the
workflow.
If
you're
ever
trying
to
add
a
component
to
slippers
right
now,
you
essentially
have
to
do
a
ton
of
copy
and
pasting
from
other
existing
components
or
just
know
what
you're
doing
and
that's
like
kind
of
annoying
and
tricky.
C
So,
like
I
created
essentially
a
little
script
that
like
when
you
call
yarn,
generate
the
name
of
a
component
it'll
generate
all
of
the
necessary
directories,
template
for
I
for
both
the
story,
file
and
the
view
file
and
then
it'll
add
it
to
the
main
bundle.
So
that's
really
helpful
so
that,
like
essentially
all
of
like
the
menial
tasks,
time
consuming
work,
that
happens
when
you're
trying
to
write
new
components,
it
gets
all
automated
away.
C
Automation
is
nice,
so
we
should
use
it
whenever
possible.
This
is
like
almost
done.
It
just
needs
like
one
little
thing
to
get
merged
and
I
did
an
iteration
for
navigation
that
is
currently
work
in
progress.
I
have
not
asked
anyone
to
look
at
it
because
there's
still
stuff
that
needs
to
be
fixed
for
the
most
part,
the
1.1
stuff
that
I
listed
in
the
mr
from
the
previous
iteration
has
been
done.
C
C
I
assume
that
it's
going
to
completely
break
as
with
the
blog
stuff
that
tyler
did
so,
I'm
not
sure
if
we're
going
to
in
implementation,
for
that
we're
going
to
use
something
similar
to
like
the
web
component
technology
that
tyler
wrote
in
his
blog
post.
I
don't
know
if
that
makes
more
sense
for
what
we're
doing
here,
but
I
just
wanted
to
call
out
that.
That's
like
something
that's
on
the
horizon
for
this
stuff,
because,
as
mentioned
by
previous
members
of
this
team
at
various
points
throughout
the
two
weeks,
it'd
be
great.
D
So
I
worked
with
some
lean,
tyler
and
chad
to
launch
the
handbook
separation
working
group.
So
we've
got
a
handbook
page.
It
was
decided
this
week
that
we're
actually
not
gonna
work
on
it.
This
quarter,
but
we're
ready
to
fire
this
up
when
it
does
happen,
so
that
took
a
lot
of
cross-collaboration
for
us
to
get
really
clean
on.
D
B
There's
also
this
issue
here,
where
I've
just
written
out
all
my
observations,
and
this
will
set
us
up
for
q2
really
nicely
and
then
the
next
thing
on
there
is
the
free
trial
update
when
you
open
the
figma
file,
you'll
see
it's
a
bit
different
than
our
current
one,
we're
really
focusing
on
sas
as
the
default
and
then
giving
a
secondary
option
to
self-managed.
If
you
scroll
down
a
little
bit,
you'll
see,
there's
actually
a
form
we
can
embed
for
self-managed,
which
we
can't
do
for
sas
currently
and
really
proactively.
B
Answering
people's
questions
with
faqs
and
just
overall
big
copy
changes,
so
it'll
be
much
clearer
for
the
user.
What
they're
getting
out
of
signing
up
for
free
trial?
The
next
thing
is
some
updates
to
slippers
on
the
design
side.
So
one
thing
is
a
button
with
an
icon
attached,
as
you
can
see
up
with
twitter,
whoever
we
have
to
need
at
the
time.
B
You
can
keep
this
one
open
hobby,
the
other
second
one
after
this
is
just
updates
buttons
in
general,
so
making
sure
we're
consistent
with
our
like
disabled
across
the
board,
it's
kind
of
using
the
same
style,
a
new
event
which
is
like
on
click
or
pressed.
So
when
you,
actually,
you
know,
click
on
the
button,
if
you
remove
the
drop
shadow,
it
gives
it
like
a
3d
effect
that
you've
actually
pressed
something.
B
So
we
added
that
in
there
as
well-
and
the
last
thing
is:
oh
just
updates
to
go
down
number
radio
buttons
and
check
boxes
and
they're
pretty
subtle.
I
don't
know
if
you're
gonna
really
notice
much,
but
just
like
reducing
the
outline
to
one
pixel
and
again
making
them
consistent
across
the
board
yeah.
Just
some
slippers
updates.
That's
all
stephen's
up.