►
From YouTube: Digital Experience Release Video - Jan 13, 2022
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
A
B
She
designed
a
new
side
panel
to
encourage
free
trial
adoption
on
the
login
page.
She
worked
on
the
smb
page,
where
she
suggested
various
updates,
such
as
linking
out
to
related
pages,
adding
a
hero,
video
and
cleaning
up
ui
inconsistencies
and
the
last
item
listed
here.
She
found
and
modified
unsplash
stock
photos
to
replace
gitlab
team
member
photos
in
our
various
cta
blocks,
and
there
are
no
show
items
here
so
we'll
move
on
to
tyler.
C
Yeah,
so
nothing
to
show
in
this
a
bunch
of
google
tag
manager
stuff.
So
I
patched
up,
I
had
missed
the
almost
their
view
in
the
free
trial
flow.
So
now
that
is
instrumented.
I
added
the
add
to
cart,
enhanced
ecommerce
events
on
the
pricing
page
when
you
like
click
to
the
purchase.
So
it's
like
nested
clicks
in
updated,
there's
a
trial
form
where
I
had
missed
a
trial
group
creation
event.
So
I
patched
that
up.
C
I
also
patched
up
this
one's
fun
to
say
so.
We
added
gtm
tracking
for
gitlab
export
project
imports.
So
if
you're
like
importing
a
project
from
an
existing
gitlab
export,
I
had
also
missed
that
event.
So
that's
there!
Now
too,
I
just
landed.
I
just
did
a
super
quick
refactor.
I
had
forgotten
to
like
move
some
feature
flag
stuff
into
before
actions
and
then
throughout
the
last
week
or
two
I've
just
had
like
some
small,
mrs,
that
I've
like
reviewed
and
merged.
C
So
we
like
added
gzip
compression
to
files
on
about
iqlab.com
or
back
to
it,
there's
some
seo
stuff
with
meta
titles.
Some,
oh,
I
changed
the
deploy,
jobs
and
buyer
experience
to
share
an
image
that
we
need
for
like
patched
like
google
utilities
and
then
dallas
has
been
doing
a
bunch
of
stuff
with
free
trials.
So
I
just
like
click
the
merge
button
for
them
on
that
and
I
think
that's
it
so
megan
you
are
up
next.
D
All
right,
the
majority
of
the
past
two
weeks
was
like
onboarding
stuff
and
when
I
wrapped
that
up,
I
worked
with
nathan
to
find
kind
of
a
low
stakes
issue
to
work
on.
So
I
wrapped
up
a
an
hr
rendering
issue
in
the
dub
dub
dub
repo.
It
was
a
good
way
to
get
acquainted
with
that
repository
and
getting
my
environment
all
set
up
locally,
but
lauren.
B
Thanks,
I
also
did
a
ton
of
mr
reviews.
I
continued
to
support
the
ongoing
page
migration
to
the
buyer.
Experience
repo,
basically
just
checking
designs,
making
sure
ui
ux
is
acceptable
and
consistent.
I
worked
on
my
onboarding
issue.
Nothing
to
show
there
unless
you
all
want
to
see
all
my
certificates
and
badges
that
I've
completed.
It's
been
a
really
great
refresher,
considering
I've
been
already
technically
working
at
gitlab
for
over
a
year.
It's
funny
to
revisit
all
this
stuff
doing.
B
Onboarding
issues
twice
is
interesting
also
and
lastly,
I
started
to
get
my
head
into
the
ux
updates
for
the
analysis
page
issue.
I
created
a
content
outline
for
the
requesting
team
members
to
review
and
populate
because
there
were
a
couple
issues
for
this
page
update
with
a
lot
of
ideas,
but
no
really
no
kind
of
document
that
tells
us
what
is
actually
going
to
be
on
the
page,
so
I'm
a
little
bit
blocked
there,
but
I
I
think
that
we'll
circle
back
next
iteration
next
is
laura.
A
Yeah,
so
I'm
finishing
up
some
work
on
our
swift
type
search.
Google
analytics
instrumentation
in
the
buyer
experience
repo.
It's
currently
live
on
the
regular
website.
Tyler
made
a
good
point
about
key
up
events
instead
of
click
events,
so
I'm
just
fixing
that
up
and
those
events
are
are
also
working
on
our
404
page
search,
which
is
handy
because
it's
the
same
swift
type
with
the
same
class
names,
and
I
made
some
one
trust
updates.
A
F
G
Thank
you
mega
for
me
what
I
worked
on
this
iteration.
I
had
an
issue
open
for
slippers
reserve
retrospective
parker.
Thank
you
for
asking
the
structured
questions.
I
think
it
helped
with
getting
some
of
the
answers
out
if
you
haven't
added
points-
and
you
would
like
to
do
so
before
the
end
of
this
week,
because
I'd
like
to
add
some
of
the
points
that
we've
talked
about
to
the
handbook,
especially
our
slippers
page,
because
I
think
all
of
that
stuff
is
really
important.
G
I
have
a
draft
for
the
navigation
mvc4.
I
very
much
underestimated
how
long
this
would
take,
but
this
is
something
that
just
worked
on
for
sigma,
and
so
I'm
doing
this
here
things
to
know.
So,
if
I
inspect
and
if
we
go
to
class
stuff,
oh
I
have
to
remove
this
one,
but
for
the
most
part,
all
classes
are
no
longer
yeah.
If
I
keep
going
like
we're,
we're
using
them.
G
Slippers
is
no
more
for
the
navigation,
at
least
on
the
dub
dub
dub
side,
and
so
that's
that
I'm
trying
to
find
my
spot
and
so
then
I
worked
on
a
card
plate
consistently.
I
wanted
to
show
the
review
app.
I
had
a
lint
error.
Sorry,
so
I'm
just
linting
I'm
showing
this
changes
to
show
that
I've
did
something.
I
swear,
I'm
also
reverting
20
alert
boxes
on
the
docks
for
headed
to
the
free
trial.
G
I
have
a
whole
issue
talking
about
the
reasons
why
I
did
that,
but
essentially
the
experiment
did
not
pass
and,
if
you're
interested
in
finding
out,
why
there's
the
issue
discussing
why
I
have
a
lot
of
little
chores
in
terms
of
removing
things
for
the
slash
analyst
page,
adding
the
slippers,
ui
template,
adjusting
open
graph
to
work
and
brainstorming
stuff
for
more
experiments
to
run
on
the
free
trial
stuff.
So
up
next
is
john.
H
Okay,
so
in
this
iteration
I
work
on
the
migration
of
more
solutions.
Child
pages,
so
I
work
in
the
cover
dates:
one,
the
open
source
page
and
also
the
jira
page.
Regarding
the
data
page,
I
added
aos
animations
to
the
buyer,
experience
repo.
That
is
the
same
library
that
we
were
using
on
that
dot,
repo
and
also
I'm
not
in
a
generic
component
taken
from
learn
page
mark
that
I
have.
We
are
not
going
to
migrate,
learn
page,
but
that
component
will
be
useful
for
us
in
the
next
iterations.
I
Yeah
for
this
iteration
I
work.
I
continue
working
on
the
migration
of
state,
the
stage
the
box
life
cycle
at
last
minute,
jessica,
shared
me,
the
new
redesign
that
looks
amazing,
so
extra
work
was
required
there
I
needed
to
customize
some
components
and
also
work
on
the
migration
of
the
child,
child
patients
of
a
stageable
flight
cycle
that
there
is
a
degree
of
dependency
on
on
the
parent,
so
I'm
still
working
on
on
that
part.
J
K
Yeah,
okay,
I'm
gonna
create
a
retro
one
day,
just
to
go
over
what
happened
with
slippers,
who
won,
but
in
the
short
of
it.
I
built
that
on
slippery
view,
three
found
out
view.
Three
cannot
go
to
view
two
because
buyer's
experience
on
v2.
I
tried
to
write
my
own
like
transpiler,
and
try
and
do
it
myself
and
it
took
too
long
so
now
I
went
back
to
view
two
anyway
that
works
done.
K
I
tokenized
slippers
with
the
help
of
justin
tina,
so
now
we're
no
longer
using
like
the
actual
color
names
or
the
actual
like
not
it's
not
semantic
anymore,
it's
more
like
100
200
300.
So
now,
if
we
change
the
color,
we
don't
have
to
replace
it
everywhere.
I
imported
the
slippers
v1
package
finally
into
the
virus.
Experience
repo.
It's
only
an
mr
right
now,
so
I
think
I'll
do
it
maybe
tuesday
next
week.
K
I
don't
want
to
do
it
before
the
weekend
and
then
I
also
globally
set
all
the
components
and
styles,
so
you
won't
have
to
import
like
the
button,
the
container
or
even
in
the
scss
file.
You
don't
have
to
import
variables
anymore.
They're!
All
globally
imported
and
I
replaced
all
the
existing
css
variables
in
the
buyer,
experience
repo
with
the
tokenized
version.
So
there's
a
big
mr
there
I
went
through
all
the
files
in
the
wire
experience
repo
and
replaced
those.
K
I
think
I
got
them
all.
It's
gonna
need
a
bit
of
qa,
so
I
think
on
that
review
app
when
it's
up
and
running
tina,
just
gonna
need
some
help,
just
to
make
sure
that
the
headers
are
the
right
headings
and
all
that
kind
of
stuff,
but,
like
I
said
I'll,
follow
up,
probably
on
tuesday,
with
like
a
big
post
and
how
we're
gonna
go
forward,
but
yeah.
That's
it
for
me,
yeah.
I
think
that's
it
for
the
sprint
release.