►
From YouTube: Digital Experience Iteration Release - Mar 24, 2022
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
A
B
B
So
did
that,
but
there's
going
to
be
another
iteration
where
you
make
that
a
lot
more
efficient,
because
we
can't
run
scripts
for
that
long.
It
changed
some
h1
headings
on.
I
believe
it
was
a
topics,
template
added,
a
couple
of
child
topic
pages
and
I
will
share
those
right-
the
the
yeah,
that's
not
the
one
nah,
that's
that
one!
B
Okay
and
let's
see
we
haven't
had
child
topic
pages
yet
so
kind
of
built
that
functionality
in
and
these
were
built
by
val,
so
just
kind
of
helping
her
out
got
those
on
there.
So
now
we
can
have
other
child
pages,
maybe
in
our
solutions
or
topics
which
is
cool,
assisted
in
page
depreciation
redirects.
I
think
tyler
actually
did
most
of
that.
B
I
was
assigned
on
to
it
and
then
the
other
one
was
null,
and
the
last
thing
I'm
working
on
is
getting
the
gl
website
group
depreciate
or
taking
me
like
off
of
it.
I
realized
I
was
the
only
one
in
the
geo
website
group,
so
every
community
contribution
to
dub
dub
dub
was
getting
pinged
and
I
was
the
only
one
so
fixing
that
we
started
a
a
get
lab.
Dashcom
dash
community
group,
john's
gonna
lead
it.
C
His
camera
is
off
yeah,
I'm
eating
mac
and
cheese,
but
I'll
turn
around
for
this
I
it's
hard
to
track
like
I
ended
up
getting
pulled
into
like
a
bunch
of
different
stuff,
but
at
a
high
level
a
lot
of
it
was
like
parker
said,
like
I
did
a
lot
of
the
page
deprecation
for
the
stuff.
That's
going
away.
We
just
like
four
afford
a
bunch
of
pages.
I
helped
hannah
do
that.
C
I
pitched
in
on
the
customer
case
studies
landing
page
for
a
couple
days
while
megan
was
out
and
then
honestly,
just
like
bits
and
pieces
here
and
there,
like
every
other
day
like
there,
was
not
like
a
single
like
task
that
I
completed.
That
was
just
me,
so
I
don't
have
a
ton
else
to
start
about
for
release,
but
you
all
know
what
I
did.
D
I
spent
most
the
well
maybe
half
the
iteration
working
on
the
nav.
I
got
it
in
a
pretty
good
place
and
then
we
just
made
a
couple
changes
with
from
hover
to
click,
and
I
did
that
right
before
this
meeting.
So
unfortunately
I
can't
share
it,
but
I'll
share
it
after
you
can
take
a
look
it'll
be
on
the
refresh
branch
once
it's
merged
in
and
then
added
some
data
attributes
back
to
the
nav.
D
D
Hopefully
we
can
figure
out
why
it
happened,
I'm
still
not
sure
and
then
a
lot
of
merging,
so
getting
the
refresh
branches
updated,
getting
the
main
branches
updated
and
then
pulling
in
lower
slipper
changes
into
the
main
repository
or
the
refresh
repository
and
then
adding
some
stuff
to
slippers.
I
think
there
were
some
colors
for
surface
and
a
few
other
little
things.
So
a
lot
of
just
like
odds
and
ends,
but
yeah
laura.
I
think
you're
next.
A
Yeah,
thank
you.
I
had
a
couple
of
seo
related
issues
from
hanov.
One
was
for
the
404
page
that
one
is
code
complete,
but
it
was
missing
a
page
title
and
the
url
canonical
url
was
adding
an
extra
trailing
slash,
which
is
an
issue
we
had
dealt
with
before
so
fixing
that,
for
the
404
page
is
in
review,
hannah's
taking
a
look
at
it
and
then
a
couple
more
homepage
updates
for
the
canonical
url,
so
those
are
merged.
A
There
was
also,
since
we
added
the
home
page
to
our
new
buyer
experience
repo.
We
have
to
kind
of
update
the
way
that
the
release
team
does
releases
because
our
homepage
gets
updated
with
releases,
so
I
updated
the
documentation
for
the
release
team
so
that
they
are
changing
it
in
the
correct
repository
now
and
then.
Finally,
as
nathan
mentioned,
I
added
the
kind
of
fresh
coat
of
paint,
new
slippers,
colors
and
confetti
and
styles
into
the
slippers.
E
E
There
is
a
tabs
menu
component
mobile
regression,
essentially
just
catching
regressions
that
are
happening,
there's
also
another
regression
on
the
buyer's
experience
repository
where
markdown
wasn't
being
rendered
into
html,
and
so
then
I
fixed
that
there
are
some
style
things
that
were
also
being
caught
that
I
worked
with
nathan
at,
like
I
don't
know
like
9
00
p.m.
On
friday
night
last
week-
and
I
didn't
do
this-
it's
actually
something
that
nathan
did
important
refresh
branch
into
by
experience.
E
F
Hey,
I
think
I
was
able
to
release
in
this
sprint,
was
an
update
to
the
faq
page
schema.
It
can
now
consume
markdown
if
someone
wants
to
add
like
a
list
or
a
link
it'll
work
now,
but
with
all
my
days
of
out
of
the
office,
I
didn't
get
a
chance
to
finish
up
the
customers
page,
but
it's
pretty
close.
Thank
you
so
much
tyler
for
contributing
to
that.
But
next
up
is
john.
G
G
This
one,
so
this
is
what
I
have
right
now:
it's
a
work
in
progress,
but
we
now
have
the
features
page,
not
with
all
the
content
that
your
original
has,
but
we
have
filtering
so
we
can
filter
by
features.
We
can
see
what
is
missing.
For
example,
here
in
plan
we
have
missing
features
at
the
bottom
of
the
page.
You
can
see
the
animations
also
what
is
missing
and
you
can
go
back
on
filter
again.
You
can
filter
if
it's
free,
so
you
can
see
what
is
free
here.
G
H
I
have
been
working
on
the
migration
for
that
one
and
also
some
content
updates,
which
were
requested
in
a
separate
mr
to
to
the
pricing
page
and
a
new
component
also
for
the
carousel,
which
is
one
of
the
features
that
comes
from
the
repo
and
also
big
thanks
to
megan.
She
had
already
worked
on
a
base
template
for
the
pricing
page.
H
So
this
is
the
already
migrated
pricing
page
and
I
have
added
the
features
that
come
from
the
www
repo,
such
as
the
this
expanding
lists
with
the
tooltips
and
this
new
faq
behavior,
which
has
all
the
questions
being
expandable,
and
this
show
all
button
which
opens
all
of
them
and
then
becomes
this
hide
all
button
and
then
for
the
mobile
version.
Also,
this
carousel,
which
can
be
switched
either
by
dragging
or
by
clicking
these
buttons
over
here
and
that's
it
for
me.
Next
one
is
miguel.
A
So
if
you
come
in
kind
of
to
the
middle
here,
you
can
choose
whatever
plan
that
you
have
and
just
get
the
information
you
need
for
your
specific
plan
and
then
everything
else,
all
that
kind
of
big
information
at
the
bottom
of
that
page
kind
of
just
becomes
an
faq
and
kind
of
what
miguel
was
showing.
I
think
it
was
miguel
with
the
hide
all
show
all
plus
and
minuses
same
same
idea
with
this
faq
here
and
just
a
couple
cards
at
the
bottom.
A
J
I'll
share
my
screen.
I've
had
a
lot
going
on
this
sprint.
The
first
thing
that
took
priority
was
the
jobs
to
be
done
templates
for
some
of
our
ia
refresh
works,
so
this
is:
we've
decided
to
templatize
the
solutions
pages,
so
we've
kind
of
tried
to
figure
out
how
to
do
that
by
using
the
jobs
to
be
done.
I'm
I'm
going
to
be
completely
honest.
J
This
is
template
two
and
a
couple
of
examples
of
how
each
template
could
be
used
for
specific
sections
example:
company
size,
which
would
be
like
enterprise
and
smb
and
startup
industry,
which
would
be
like
finance
and
healthcare,
and
things
like
that,
so
those
are
in
the
hands
of
gem
3
now
to
do
their
magic.
I
also
did
the
jobs
to
be
done
templates
for
the
features
section,
which
is
what
john
just
showed.
J
We
said
that
it
would
be
helpful
if
we
start
skinning
these
without
assets,
just
so
that
engineers
have
something
to
work
with
so
I'll,
be
improving
this
page
with
some
of
what
we
saw
from
gem
3
today,
but
this
is
an
example
of
a
single
features:
page
template
using
source
code
management
as
an
example.
So
this
is
what
it
could
look
like.
J
Did
I
get
through
everything
home
page
bragwall
updates,
that's
blocked,
because
when
I
logged
into
g2
to
change
the
badges,
I
realized
that
I
completely
missed
the
winter
badges
and
worn
spring,
but
this
is
to
update
them
for
the
winter
badges.
So
I'm
just
waiting
to
hear
from
that,
and
I'm
not
sure
where
we
are
with
this
issue.
Next
is
gary.
K
K
K
K
I've
also
been
working
on
the
jobs
to
be
done
for
that
to
eventually
hand
off
to
jam
three
similar
to
tina,
and
so
we
have
kind
of
our
templates
here
for
different
kind
of
checklists.
They
all
kind
of
are
the
same
template
just
different
jobs
to
be
done
for
each
user
type,
and
then
we
have
the
higher
fidelity
that
I've
just
been
starting
to
work
on
and
that's
it.
L
So
you
just
like
select
your
device
category
browser
brand
and
then
filter
for
a
page,
and
then
it
just
show
you
some
of
the
web
vitals
in
terms
of
the
scale
and
some
definitions
as
well.
I'll
still
have
it
in
a
table
format
that
way
you
can
kind
of
see
it
from
an
overview
in
terms
of
page
performance
and
then
at
the
bottom.
I
also
have
like
javascript
errors
mainly
for
engineers
if
they
want
to
take
a
peek
at
what's
throwing
a
wrench
in
our
system
and
then
yeah,
I'm
still
working
through.