►
From YouTube: Digital Experience Iteration Recap 2021/03/25
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
A
So
these
are
so
these.
This
is
a
figma
file
with
different
blocks
that
can
be
assembled
to
create
the
events
templates.
So
the
events
template
will
be
held
in
one
mother
template
and
we
can
use
that
template
to
create
all
of
the
different
stages
of
the
events.
This
issue
is
in
review
and
going
into
design.
A
Also
for
my
sprint
release,
I
worked
on
some
blog
issues.
I
created
some
thumbnail
issue,
some
thumbnail
images
for
the
blog
homepage.
I
also
created
in
body
cta
block
for
cross
blog
promotions.
This
has
also
been
closed
now
past
reviews.
So
this
is
an
issue
for
engineering
and,
lastly,
I
collected
with
the
help
of
shane
some
heat
mapping
for
the
top
five
pages
funneling
traffic
to
the
free
trial.
A
This
is
part
of
an
okr
and
for
the
next
print
I'll
be
taking
a
look
at
the
the
results
of
these
heat
maps
and
making
some
recommendations
for
ux
improvements.
A
There
we
go
next
is
lauren
all
right.
B
So
we
executed
the
brand
messaging
top
10
pages
epic,
so
we
updated
all
those
pages
with
the
new
brand
message.
It
did
that
with
val
super
exciting
went
really
smooth.
Moving
on
we,
I
update
or
added
some
slippers
blog
components
to
the
repo,
the
blog
header
and
the
tags
component.
B
We
will
be
adding
the
breadcrumbs
component
shortly,
like
the
end
of
today
also
updated
our
typeform
handbook
updates
so
back
on
our
netlifecms
landing
page,
and
then
I
also
added
instructions
elsewhere
in
the
handbook
on
how
to
use
typeform.
B
We
have
a
mr
that's
in
flight
right
now,
where
we're
launching
new
pricing
calculator
on
the
website
super
exciting,
that's
kind
of
been
in
progress
for
about
like
a
half
a
year,
so
exciting
to
see
that
go,
live
big
update.
That
was
really
the
entire
digital
experience.
Team
was
making
our
new
blog
post
template
live
and
we
have
a
follow-up
epic,
which
was
a
team
effort.
Everyone
taking
a
look
and
saying
hey,
we
gotta
fix
this.
We
gotta
fix
that
we
gotta
do
this.
B
Look
at
all
those
beautiful
issues
we
have
and
we're
gonna
be
busting
those
out
over
the
next
couple
of
weeks.
So,
if
you
see
something,
we've
got
an
epic
for
you
to
add
an
issue
to
and
tyler
who
is
not
here
I'll
move
on.
He
fixed
some
issues.
We
have
with
duplicating
styles
on
our
blog
template.
B
He
also
came
up
with
a
great
solution
to
our
slippers,
conflicting
styles,
with
our
website
styles,
using
a
shadow
dom
which
is
actually
really
really
cool
and
it
works
so
sweet
and
it's
live
now,
and
he
also
added
a
bunch
more
blog
components
like
the
image
gallery.
Pull
quote
banner
sidebar
blog
feature
image
and
the
anchor
link
with
arrow
so
that
wraps
it
up.
C
Over
to
jess
yeah
thanks,
so
I
just
got
one
thing
for
you
guys
today,
which
is
the
navigation
design
for
both
desktop
and
mobile.
If
you
can
open
the
figma
file,
you
can
see
the
designs
had
a
lot
of
back
and
forth
different
changes,
since
we
did
the
research,
so
hopefully
this
is
good
to
go.
There
might
be
iterations
after
this
seeing
how
things
work
in
the
real
world
and
a
little
bit
of
work
on
the
search
as
well
and
there's.
C
D
Yeah,
so
I
made
a
few
updates
to
slippers.
We
now
have
form
fields,
so
these
are
like
your
traditional
input
fields
which
are
you
can
play
around
with
them
there.
There
will
be
some
updates
with
these,
but
yeah.
D
There
are
controls
that
lets
you
change
with
what
the
placeholder
text
says,
or
the
label
text
says
and
will
update
the
styles
based
on
what
state
the
form
input
is
in,
and
those
controls
are
also
available
to
the
checkbox
and
radio
which
they
weren't
before
so
some
improvements
to
form
fields
all
around
hopefully
they'll
play
nicely
with
some
of
our
existing
form:
external
vendors
that
we
have
on
the
site.
D
D
We
had
had
some
commit
meetings
for
the
upcoming
commit
event,
the
2021
event
for
the
new
template
that
we're
building
and
what
came
out
of
that
meeting
was.
We
might
want
to
link
to
last
year's
event
at
some
point,
which
was
problematic
because
I
had
changed.
All
of
that.
I
had
just
updated
last
year's
files
to
be
this
year's
days,
so
I
went
back
and
kind
of
cherry
picked
those
commits
and
and
preserved
that
page,
so
that
existing
last
year's
website
will
always
be
available
at
the
commit
2020
url.
D
So
that's
safe.
Once
again,
it's
been
reinstated
and
up
next
is
hobby.
E
E
This
is
just
me
doing
me
things.
I
found
like
a
thing
that
lets
us
view
our
configuration
file
of
tailwind
for
our
repo,
and
so
then
this
is
like
the
actual
project
itself.
It
was
super
simple
to
set
up
it's
nice.
I
like
it.
I
think
it'll
help
us
with
the
developer.
Experience
worked
on
footer
using
slippers
tried
to
get
it
to
work.
E
I
realized
that
I
might
have
not
used
shadow
dom,
which
explains
why
I
probably
have
a
ton
of
conflict,
so
I'm
gonna
use
that
for
that
footer
and
I'm
looking
to
make
a
layout
for
it.
Essentially,
so
we
have
like
one
layout
in
middleman.
That's
just
like
all
slippers,
and
I
think
that
will
like
play
nicely
with
the
work
of
like
wanting
to
get
like
a
header
in
there
as
well,
which
is
what
like
the
navigation
that
just
worked
on.
E
I
have
some
stuff
about
like
stuff.
That's
just
been
super
work
in
progress.
I
just
wanted
to
call
out
this
one
thing
in
particular
where
it's
like:
if
no
one
else
has
any
like
comments
on
this,
I'm
just
gonna
make
an
mrn
tag,
tyler
for
it
and
that's
like
yeah.
E
That's
fine,
one
other
thing
that
I
want
to
work
on
in
the
next
day
or
two
or
at
least
like
try
to
see
if
we
can
make
any
headway
is
to
just
like
essentially
like
use
the
different
tailwind
at
apply
directives
that
exist
and
trying
to
get
those
to
work
within,
like
the
view
components
themselves,
people
have
been
asking
for
them,
laura
asked
for
them.
E
Tyler
has
asked
for
them
so
yeah,
let's,
let's
get
those
in
there
and
it
helps
with
like
keeping
all
of
our
code
consistent,
helps
with
like
reusing
tailwind
as
much
as
we
can,
and
so
that's
all
it.
For
me,
I
see
that
brandon
I
saw
his
tooltip
show
up,
so
I
don't
know
if
he's
here.
F
Sorry
I
popped
in
at
the
I
came
in
late,
but
yeah,
so
there's
not
too
much
to
see
here
visually,
but
the
pricing
page
is
going
through
another
test
iteration
and
it's
basically
comparing
you
know
what
the
we're
trying
to
learn.
If
the
view
more
toggle
on
the
plan
matrix
at
the
top
because
about
half
people
were
clicking
on
it
previously,
we
want
to
learn
if
it's
beneficial
to
just
leave.
It
always
open.
If
that
impacts
conversion
or
not.
F
So
that's
what
we're
testing
now
and
that's
live
as
of
yesterday
afternoon
and
so
yeah
more
to
learn
from
that
coming
up
soon
and
that's
it.
For
me,
all
right
looks
like
stephen,
but
yeah
he's
here.
G
So
added
labels
to
the
spacing
in
figma,
which
may
sound
simple,
but
here
we
are
so
when
you
drag
them
in,
you
can
see
actually
what
size
they
are,
as
opposed
to
trying
to
guess
what
they
are
from
some
color
code,
which
makes
no
sense
and
small
changes.
G
I've
added
I
provided
an
update
on
this
okr
feature
description
page.
It's
got
some
metrics
that
we've
pulled
from
the
current
state
and
for
ahead
of
a
kickoff
meeting
next
week,
so
feel
free
to
go
ahead
and
have
a
look
there
and
documentation.
God,
damn
new
zoom.
Sorry,
the
zoom
menu
has
covered
my
screen.
There
we
go.
G
I've
made
a
start
on
some
documentation
here,
some
of
it's
quite
high
level
as
to
what
exactly
slippers
is,
and
some
of
it
gets
a
little
bit
into
the
weeds,
around
typography,
color
and
spacing
and
and
so
on.
This
is
a
big
work
in
progress.
I'll
be
looking
to
get
everybody's
eyes
on
this
at
some
stage.
Giving
me
some
help
please,
on
this
and
but
yeah.