►
From YouTube: Digital Experience Release Video - Feb 10, 2022
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
A
A
Oh,
I
probably
could
have
shared
that
better
anyway,
so
I
kind
of
I
have
shadows
still
to
do.
That's
meant
for
kind
of
the
friday
friday
thing,
so
I'm
gonna
work
on
that
tomorrow
and
then
what
I've
been
working
on
is
currently.
This
is
in
review.
So
what
we
did
is
we
replaced
all
the
styling
in
the
buyer,
experience
repo
with
slippers
and
that's
going
out
on
monday.
A
We're
going
to
wait
for
all
these
other,
mrs
to
get
merged
in
before
we
do
this
and
then
I'm
currently
working
on
the
pricing
carousel.
So
I'm
trying
to
get
blockers
done
before
we
start
on
the
pricing
page
and
one
of
them
is
we
use
like
a
carousel.
I
don't
know
if
you've
noticed
it
on
the
mobile
version
of
the
pricing
page
to
kind
of
slide
or
swipe
between
tiers.
A
So
I'm
trying
to
find
like
a
view
alternative
for
that
or
somehow
implement
jquery.
I
really
don't
want
to
put
jquery
in
the
new
site,
but
I'll
figure
something
out,
and
then
I
just
worked
on
a
bunch
of
small
stuff,
there's
redirects
that
were
broken,
some
p
styling.
That
was
affected
the
navigation.
A
I
imported
slippers
into
the
bar
experience
repo,
so
it's
just
there.
It
doesn't
do
anything,
it
doesn't
affect
anything,
but
at
least
the
import's
there
now
slippers
v1
is
published.
I
changed
the
branch
name
for
the
slippers
repository
and
did
a
bunch
of
branching
changes.
Yeah.
I
think
that's
it
for
what
I
worked
on
the
last
two
weeks
and
a
bunch
of
just
kind
of
planning
for
the
next
quarter.
B
Are
you
seeing
my
board
yeah?
Okay,
so
I
had
a
shorter
sprint
cycle
than
usual
due
to
some
pto.
So,
aside
from
a
bunch
of
mr
reviews,
which
I
know
everyone
does
but
I
like
to
mention
it
because
they're
so
darn
time
consuming
and
they
don't
show
up
on
my
boards
but
anyways,
my
only
real
contribution
was
an
update
on
the
home
page
security
and
compliance
banner.
So
this
is
the
issue.
That's
closed.
I'm
gonna
just
scroll
down
to
the
update
here.
B
So
here's
the
updated,
visual
there's,
an
engineering
issue
that
I
just
opened.
You
know
maybe
an
hour
ago
with
all
the
links,
so
the
changes
in
include
adding
the
iso
certification
banner,
the
csa,
trust
cloud
provider
banner
and
updating
some
copy,
because
now
we
have
this
with
c3
certification
and
we're
removing
the
bid
site
banner.
So
that's
ready
for
hopefully
next
iteration
and
it's
in
triage
and
that's
it
for
me.
C
I'll
hop
in
go
next
so
for
this
iteration,
so
I
do
all
this
stuff
over
here.
So
I
I
looked
into
redirecting
gitlab.com
to
the
pricing
page
turns
out
that
the
pricing
name
space
is
owned
by
a
private
group.
We
reached
out
to
them
to
see
if
they
would
give
it
up
to
us
and
they
said
no,
so
that's
not
happening,
we'll
look
at
maybe
some
other
things
later.
C
We
wrapped
up-
and
this
is
the
team
not
me,
but
all
of
the
the
child
topics-
digital
transformation
pages
and
migrated
the
remaining
solution
pages,
so
good
work
team.
I
am
still
working
on
this
visible
script.
Hard
coding
into
the
project
realized
yesterday
that
I
need
two
sister,
mrs
one
for
omnibus
and
one
for
charts,
and
then
they
all
have
to
ship
in
the
same
release.
So
the
next
release
is
february
22nd.
So
that
will
be
my
big
push.
C
C
There
was
some
stuff
that
hanoff
noticed
like
our
h2
tags
were
off,
there
were
no
canonical
paths
and
their
faq
schema
was
missing.
So
I
pushed
two
mrs
one
is
this
one
was
to
edit
all
the
h
tags.
So
now
our
pages
have
h1
and
h2
and
h3,
and
then
we
added
the
canonical
paths
in
one
of
them,
but
that's
not
showing
here
and
then
I
have
this
draft.
Mr
to
add,
the
faq
schema
back,
but.
E
All
right
in
this
iteration
worked
on
a
lot
of
the
topics.
Page
migrations,
the
big
one
I
wanted
to
point
out
was
the
devops
page.
What
I
thought
was
just
adding
the
content
in
the
new
repo
it
turned
into
so
much
more
thanks
to
jess.
I
think
these
pages
look
so
much
better.
We
tweaked
a
lot
of
components
and
made
things
a
lot
more
like
mobile,
friendly
and
just
more
slippers
related,
so
really
proud
of
that
one.
E
In
the
demo
page,
we
replaced
the
form
with
a
video,
and
then
I
finished
a
startup
solutions
page,
I
should
be
finishing
the
devops
platform
page
very
soon.
I
think
it
just
needs
to
get
reviewed
and
then
no
go
on
the
support
page,
just
there's
some
dependencies
on
other.
Mrs
who
knows,
if
we'll
get
to
this
before
we
kind
of
go
into
the
architecture,
refresh
work
but
yeah.
That's
all.
I
had
all
right,
jess.
D
D
Okay,
so
a
lot
of
what
I
did
this
week
was
just
working
on
updating
slippers,
continuing
to
audit
fix
things.
Add
things
one
thing
I'll
show
you
a
second
is
improving
the
button
ux,
and
I
also
made
a
branch
in
figma
and
started
playing
around
with
the
new
brand
design
guidelines.
So
I'll
show
you
that
as
well,
so
I'll
also
point
out
that
still
working
on
this
information
architecture,
refresh
content
gathering
just
trying
to
figure
out
what
pages
already
exist,
what
pages
do
we
need
net
new?
What
can
we
combine?
D
What
can
we
get
rid
of?
So
that's
an
ongoing
task,
and
then
I
also
just
kind
of
made
a
final
summary
of
what
we
did
in
the
free
trial,
but
nothing
new
that
we
worked
on
this
week
and
let
me
pull
up
figma.
So
one
thing
I
talked
about
was
the
button
ux
and
I'll
just
zoom
in
so
you
can
see
but
kind
of
going
for
this
more
physical
button
type
click
we're
going
for
and
then
also
there's
branch.
D
So
we
have
this
whole
new
brand
design.
Guideline
new
colors,
new
typography,
so
just
kind
of
pull
that
in
to
see
you
know
how
that
would
work
with
us.
Some
of
it
still
will
work
in
progress,
but
trying
to
figure
out
what
the
colors
would
look
like.
You
know
how
shadows
would
work
typography
using
inter
instead
of
source
sands,
that
kind
of
stuff
so
work
in
progress
on
this
as
well,
I'm
just
kind
of
playing
around
with
what
it
could
look
like
and
that's
it
for
me.
F
I
can
go
next
share
the
screen
desktop
too
cool,
so
the
view
that's
most
useful
for
me
here
is
these
merge
requests
that
have
merged,
because
a
few
of
them
didn't
have
issues
this
time
around
which
maybe
I'll
do
better
next
week.
So
starting
here
up,
this
was
a
funny
one.
The
our
like
pricing
page
has
a
bunch
of
like
it's
easy
to
get
turned
around.
F
F
It
went
out
and
then
more
of
the
same,
where
basically
like
just
stuff
that
either
I
had
diverged
from
the
spec
on
google
tag
manager,
I
had
to
like
format
some
stuff
of
strings
or
places
where
the
spec
had
been
slightly
off,
where,
like
the
currency
code,
was
outside
of
the
object
that
we
needed
it
to
be
in
and
then
another
fun
one
that
shipped
last
night.
I
was
very
excited
about
it's
a
super
small
change,
but
it's
very
meaningful.
F
So
when
we
track
the
checkout
event,
I
I
was
like
just
digging
through
some
of
the
ux
code,
and
I
was
like
oh
cool
selected
group
users
like
that
makes
a
lot
of
sense,
because
here
it
is
for
the
update
number
of
users
turns
out.
This
will
return
one.
If
so,
if
you
buy
a
sas
subscription,
but
you
don't
pin
it
to
like
a
group
if
you
just
buy,
but
if
you
buy
two
seats
not
assigned
to
a
group,
this
number
will
be
one.
F
So
I
think
all
of
the
data
from
like
last
night
at
10
pm
onwards,
will
be
correct
and
we've
like
looked
through
some
historical
data,
and
I
think,
like
that,
bug
is
like
consistent
with
the
behavior
that
we're
seeing
so
and
then
there
was
another
issue
about
drift,
which
we
can't
do
or
like
I
mean
we
can
we
just
don't,
have
the
permissions,
the
little
flashing
notifications,
we
have
it's
a
setting
and
drift.
There's
no
programmatic
way
to
change
it
so
drift.
F
G
H
I
Yeah
I
work
on
adding
new
components
to
the
stage
they
both
fly
cycle
landing
page.
I
also
work
on
a
couple
of
child
pages.
Configuring
released
and
also
I've
been
working
on
ux
iteration.
There
are
a
lot
of
mineral
issues
to
fix
there
like
hero
spacing
cda
decks.
Let
me
share
my
screen
to
show
you
something.
I
J
J
J
K
There
you
go
so
this
iteration.
I
worked
on
getting
something
done
for
dennis.
It
was
essentially
a
google
tag,
manager
thing
that
wasn't
brought
over
to
the
buyer.
Experience
repository,
so
I
just
got
that
done,
for
him
was
essentially
making
sure
that
we're
tracking
the
tabs
of
which
navigation
item
we're
going
through.
I
added
a
link
to
the
buy
experience
which
is
exciting.
It's
essentially
a
lint
job
and
he
has
configuration
where
it's
running
through
making
sure
that
all
of
our
javascript
is
applied
to
some
extent.
K
I
do
want
to
try
to
get
another
iteration
where
we're
using
the
gitlab
eslint
module.
On
top
of
that,
although
that
one
is
more
strict
and
from
trying
to
run
it
locally,
we
have
like
500
errors
on
our
buy
experience,
so
that's
probably
going
to
take
long
longer
to
merge
in,
but
that's
something
that
we're
working
on
right
now.
That's
something!
That's
in
review
is
doing
a
lot
of
the
follow-up
for
the
nbc
navigation
before
and
just
making
sure
that
it's
going
to
review
and
through
that
pipeline.
That's
it
for
me.