►
From YouTube: Digital Experience Release - Mar 10, 2022
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
A
Hi
everyone
welcome
to
the
digital
experience
team.
This
is
our
sprint
demo
sprint
recording
of
what
we
worked
on
for
the
last
two
week
period.
Today
is
thursday
march
11,
10th
10th
and
we'll
go
over.
What
we
worked
on
first
up
is
lauren.
B
All
right
just
came
back
from
pto
and
so
light
load,
and
I
shipped
this
solutions
page
super
cool.
We
got
this
cool
hover
effect
that
was
fun.
I
actually
got
to
build
something.
C
I
forgot
we're
skipping
tyler
that
called
me
off
guard
yeah.
Unfortunately,
my
sprint
was
a
little
messed
up
had
a
family
emergency,
so
I
was
kind
of
out
of
office
for
two
days
and
then
distracted
for
another
couple,
but
I've
been
mostly
working
on
just
like
merging
mrs.
I
don't
have
anything
to
demo
today,
but
hopefully,
by
the
end
of
the
week,
I'm
gonna
have
the
nav
split.
C
A
A
So
I
got
those
in
this
morning
and
we'll
keep
our
eyes
out
for
any
other
issues
that
come
up
and
then
I
worked
on
a
bug
that
michael
had
found
where
the
cookie
banner,
if
you're
in
one
of
the
regions
that
shows
the
cookie
banner,
the
drift
chat
box
is
on
top
of
the
cookie
banner,
which
makes
it
hard
to
dismiss
the
cookie
banner.
A
A
D
Thanks
laura
this
iteration,
I
worked
on
a
couple
things
so
first,
I
added
the
gitlab
eslint
plugin
to
our
buyer's
experience
repository,
so
there
should
be
an
iteration
to
our
eslint
tool.
Secondly,
I
worked
on
trying
to
add
prettier
to
the
buyer's
experience
repository
that
should
be
going
out
later.
Today
I
have
an
iteration
with
what's
it
called
launch
darkly
with
passing
query
parameters
and
I'm
actually
going
to
share
my
screen,
contrary
to
the
rest
of
the
team,
after
I
figure
this
out
here
share.
D
You
have
different
things
here,
so
that's
great
is,
if
you
want
to
see
different,
different
iterations
of
the
either
the
control
or
the
experiment,
and
I'm
also
trying
to
set
up
a
test
experiment
through
launch
darkly.
I
have
some
questions
so
that
I'm
still
not
really
sure
how
we're
going
to
do
it,
but
we're
going
to
figure
it
out
up
next
is
megan.
E
Hello
in
this
iteration
worked
on
two
placeholder
pages.
One
was
the
y
git
lab
page
and
the
other
was
the
pricing
page,
that's
almost
ready
to
get
merged
in
and,
lastly,
I'll
share.
My
screen
too
worked
on
implementing
a
faq,
the
faq
page,
schema
into
by
experience
repository
specifically
the
topics
pages.
E
If
someone
authoring
content,
as
in
this
specific,
like
schema,
a
lot
of
schemas
thrown
around
schema
on
your
yaml
file
for
your
schema,
there's
a
function
that
now
lives
in
a
typescript
file
that
will
get
consumed
by
our
other
typescript
file.
That
makes
our
pages,
but
at
the
end
of
the
day,
if
google
likes
what
they
see
and
actually
crawls
your
page,
this
is
what
it
should
look
like.
We're
testing
it
on
one
page
right
now:
the
devops
page,
actually
the
ci
cd
page,
but
every.
E
I
think
it
might
take
a
few
weeks
to
a
few
months,
hopefully
sooner
than
later,
but
keeping
an
eye
on
that.
Hopefully,
some
of
these
results
start
showing
up
on
the
googles.
Alright,
that's
all
I
got
next
up
is
jess.
A
Thanks,
I'm
also
going
to
share
similarly
to
nathan
had
an
unexpected
short
week,
and
I
do
have
some
things
to
share
so
that
the
navigation
here
were
have
a
much
larger
navigation
coming
with
our
information
architecture
refresh.
So
we
kind
of
made
it
a
little
bit
more
complex,
but
also
you
know
trying
to
keep
it
as
simple
as
possible
with
these
various
kind
of
drop
downs
and
then
like
sub
tabs
as
needed.
A
We
also
got
support
up
here
kind
of
like
a
secondary
navigation
for
search,
login
registered
support,
and
then
the
other
thing
I
did
was
a
massive
merge
into
our
slippers
design
system.
So
things
like
colors
have
been
updated
to
match
with
the
new
brand
guidelines
we
got
last
quarter,
so
the
big
ones
color
type
now
using
enter
instead
of
source
dance
pro
everything's
been
updated,
but
I'm
not
going
to
go
through
each
one
individually,
just
kind
of
give
you
a
quick
brief
example
and
then
tina
we're
up
next
thanks.
F
Oh,
I
cannot
hold
on
a
second
I'm
on
my
new
computer,
so
I
can't
seem
to
share
my
screen,
so
somebody
skip
me
I'll
go
after
and
I'm
gonna
fix
my
preferences.
Sorry
about
that.
G
G
So
it's
very
low
fidelity
right
now,
but
what
we're
working
on
is
trying
to
tell
a
story
through
kind
of
like
a
long
page
format,
instead
of
just
like
throwing
everything
that
we've
done
and
accomplished
at
gitlab
we're
just
kind
of
trying
to
skim
it
down
a
little
bit
more.
I've
been
working
with
our
content
team
to
kind
of
figure
out
what
what
is
best
for
this
page
but
yeah.
G
That's
it
and
I'm
also
doing
some
research
for
our
our
customer
solutions.
Page
pages,
so
yeah,
that's
that's
about
it
and
I
will
throw
it
to.
H
And
curry,
okay,
so
let's.
H
Okay,
so
for
this
iteration
I
work
on
the
solutions:
education,
joint
page,
it
went
from
the
last
iteration
yeah.
I
only
did
feedback
this
time.
You
can
see.
We
have
the
form,
this
new
menu,
that
material
did
and
we
have
some
little
animations
and
the
new
faq
section
with
two
columns.
We
have
only
one
column,
so
I
changed
it
to
two
columns.
H
H
I
Sadly,
there's
nothing
to
show
there,
because
it's
supposed
to
look
the
same
as
it
did
before
and
after
that
I
started
working
on
creating
a
new
emphasis
component
for
slippers,
and
that's
it
for
me.
Next
one
is
miguel.
J
Thanks
mateo
yeah,
I
think
I'll
share
my
screen.
J
So
yeah
for
this
iteration,
I
worked
in
the
analyst
page.
It's
mostly
ready,
but
we
still
have
an
update
on
on
content.
We
need
to
wait
for
it,
but
it's
it's
already.
It's
already
implemented.
J
Let
me
just
show
you
how
how
it
looks
so
here
we
we
also
use
the
new
menu
developed
by
mateo
and
yeah.
It's
basically,
basically
this.
I
think
that
I
don't
have
the
other
effect
lauren
has,
but
maybe
I
can
I
can
implement
it
but
yeah
in
the
meantime,
waiting
for
the
content.
J
Also,
we
decided
to
close
this
issue
in
our
last
ui
to
code
meeting
because
it
didn't
add
the
value
we
expected
as
a
standalone
component
in
slippers,
and
so
we
decided
to
close
it
and
also
I
created
the
placeholder
landing
page
and
at
the
beginning
I
I
did
more
work
that
was
needed
because
I
was
confused
about
this
features
page.
So
I
started
with
a
new
design,
which
is
actually
this
one,
but
it's
not
the
landing
features
landing
page.
So
it's
a
completely
different
page
but
yep.
J
F
All
right,
so
I
have
to
shift
some
priorities.
I
had
planned
to
work
on
the
solutions
template,
but
we
were
asked
to
do
a
mock-up
of
the
home
page
for
the
sales
kickoff
with
the
application
of
the
new
brand
standards.
So
this
is
what
I
worked
on
instead
I'll
just
scroll
down.
I
also
took
the
opportunity
to
just
like
improve
the
layout
a
little
bit.
This
isn't
necessarily
what
our
homepage
is.
F
Gonna
look
like
because
it
it
it
was
for
a
presentation,
but
it's
can
give
us
an
idea
of
what
it
could
look
like
with
the
new
braun
guidelines.
F
Another
thing
that
I
worked
on
was
last
week.
I
showed
the
new
customer
case
studies
page
and
I
just
put
together
the
mobile
version
here.
It
is.
F
Scroll
to
the
bottom
and
that's
about
it,
I
also
had
a
an
issue:
a
request
to
update
a
bio
image
which
we
don't
need
to
show.
That's
it
for
me,.