►
From YouTube: Digital Experience Team Release - Aug 26, 2021
Description
Digital Experience Handbook Page: https://about.gitlab.com/handbook/marketing/inbound-marketing/digital-experience/
Digital Experience Release Doc: https://docs.google.com/document/d/1I9Th3Q-AakOkE_-pmNtEzwwMDSqYKF5Je2etGdPTovk/edit?usp=sharing
B
Hello
yeah,
so
lots
of
really
good
stuff
going
on
with
the
big
core
marketing
site
architecture
project.
So
we
got
access
to
a
provision
from
us
for
maintainer
status
on
a
new
repository
in
the
marketing
org,
which
I
was
able
to
push
up
our
next,
like
the
boilerplate
too
after
which
went
through
and
did
the
slippers
ui
integration
similar
to
the
demo
that
I
posted
in
slack
a
while
back
about
like
how
that
could
all
get
wired
up.
B
That's
pretty
much
exactly
the
same,
so
we
now
have
slippers
ui
integrated
there
and
it
is
managed
appropriately
through
yarn,
which
is
great.
There's
an
mr
for
that.
If
you
want
to
see
the
diffs,
I
added
the
content
module.
So
this
that
gives
us
tools.
A
lot
of
folks
are
familiar
with
this
I'm
seeing
nodding.
You
know,
tools
to
use
common,
conventional
data
structures
in
like
a
conventional
way
in
next
content.
B
B
I
just
we're
just
gonna
have
to
sort
of
duplicate
it,
which
I
did
for
the
most
part.
I
have
some
outstanding
questions
there
for
folks,
but
the
real
crux
of
it
is
like
coming
up
with
a
schema
for
how
we
handle,
like
the
differences
between
style
sheet
links,
script,
tags
and
then
like
third-party
javascript.
That
wants
to
run
in
the
head
and
there's
some
documentation
around
that
as
well.
B
Big
shout
out
to
chad,
we
had
a
great
pairing
session
and
which
pushed
me
forward
on
the
ci
config
for
it.
So
first
we
had
like
an
initial
ci
config,
push
it
to
get
lab
pages,
and
then
I
fixed
up
a
couple
things
on
these
deployments.
But
the
big
thing
is
like
we're
good,
like
I
put
together
the
review
app
infrastructure
for
this
repository.
B
So
when
you
make
mrs
you'll
get
review
apps
just
like
you
do
on
the
middleman
repository
and
I'm
like,
I
have
a
game
plan
on
deployments,
but
I
might
hold
off
on
it
until
we
have
like
stuff
to
deploy
because
there
will
there.
There
is
a
one-way
door
portion
of
this,
where
at
some
point
like
stuff
will
start
getting
pulled
into
the
production
site.
A
Yeah
I'll
read
for
tina,
so
the
first
thing
she
has
is
for
the
home
page
she's
doing
this
information
gather
to
kind
of
figure
out
how
to
do
a
data
driven
content
block
which
could
mean,
for
example,
if
we
know
you're
an
enterprise
person,
we
can
show
you
enterprise
related
content
in
the
homepage
for
euro,
or
it
could
be
geographical
like
if
you're
in
a
certain
region.
We
show
you
something
different
than
ever
another
region,
so
she's
in
the
process
of
gathering
information.
A
For
that,
the
second
thing
there
is,
I
recently
launched
a
security
block
on
the
homepage
and
I
think
you
can
show
that
one.
It's
live.
She's
chat,
we'll
do
a
little
shout
out
to
laura
for
the
development
there.
If
you
scroll
down
it's
kind
of
in
the
middle
of
the
page,
and
it
just
shows
right
there,
our
various
compliance,
badges
for
different
things,
so
that's
great
and
then
the
last
thing
for
tina
is
she's,
also
doing
some
information
gathering
for
our
gitlab's
10-year
anniversary.
A
I
believe
the
original
request
was
some
sort
of
like
data
visualization,
I'm
not
exactly
sure
where
they
are
on
this
one.
But
I
know
she's
trying
to
figure
out
what
they
can
do.
I
think
it's
in
like
three
weeks,
so
it's
coming
down
the
play
pretty
soon
and
then
for
myself.
I've
got
the
next
one.
There
did
a
little
customer,
adding
customer
logos
quote
above
the
fold.
A
You
know
it's
not
it's
a
responsive
web
page
there's
not
really
an
actual
but
the
full,
but
on
the
home
page,
which
would
be
kind
of
very
similar
to
our
enterprise
pages.
If
you
scroll
into
the
homepage
hero,
you
can
see
just
a
few
of
our
main
logos
right
under
the
top
two
buttons
there
to
get
master
seamless,
nvidia
fanatics
again,
yeah
just
very
similar
to
our
enterprise
and
just
kind
of
calling
out
the
big
names
that
we
work
with,
and
next
is
stephen.
C
Hey
so
yeah,
we
finalized
our
doc
issue
and
we
have
and
then
excuse
me
associated
with
that.
We
have
a
doc
site
content
audit,
which
will
help
us
identify
the
top
performing
pages.
It
was
a
bit
of
messing
around.
I
had
to
do
with
that,
one
to
get
it
to
work
and
sort
of
decide
for
what
pages
were
which,
because,
when
we
were
trying
to
do
in
the
original
doc,
the
formulas
would
break
and
everything
would
kind
of
collapse
and
disappear
and
and
we're
also
over.
C
C
There's
a
new
issue
created
for
google
analytics,
so
we're
using
the
top
pages
that
are
in
docs
and
we
can
identify
which
hedge
you
want
to
drive
traffic
to
on
about.getlab
and
we've
created
a
figma
epic
first
to
track
any
changes
that
we're
doing
with
figma,
because
it's
kind
of
a
kind
of
ongoing
kind
of
block
of
work
and
and
then
there's
a
design
system,
documentation.
Epic
2,
as
well,
which
has
sub
issues
in
there
too,
for
all
of
us
to
contribute
to
next
up,
is
parker.
D
There
it
is
so
that
deployed
with
0.14.6
of
slippers
it's
on
npm
and
I
can
now
transfer
over
building
that
in
www
there
were
a
couple
unsuccessful
attempts
to
solve
our
failed
to
execute
post
message
on
the
dom
window.
That's
that
air
that
we
have
on
the
live
site
that
fires
like
thousands
of
times
and
makes
it
super
hard
to
find
other
issues,
but
it
didn't
fix
it.
So,
oh
well,
we'll
try
grant
and
that
was
it
got
kicked
off
by
I'm
getting
his
name.
D
E
Thanks
lauren,
I
onboarded
to
the
docs
directory
repository
on
the
website
directory,
something
that
I
found
really
interesting,
that
I
didn't
notice
about
docs
is
that
they
pull
like
the
content
for
docs
doesn't
live
on
the
actual
docs
repository.
It
lives
like
within
their
own
respective
repository,
so
it's
like
they're
actually
calling
that
information
during
build,
which
is
where
all
the
docs
stuff
gets
pulled,
which
is
really
really
smart.
E
I
had
a
mr
with
resolving
style
and
card
consistency
I
didn't
put
show,
but
I'm
just
going
to
briefly
kind
of
walk
through,
like
some
of
the
things
that
we
had
talked
about
in
mr,
because
I
think
tina
did
a
really
good
job
of
like
kind
of
calling
out
like
what
are
things
that
were
like
in
issues
and
then
like
me,
screenshotting
and
then
like
essentially
like
the
whole
back
and
forth
of
us
like
trying
to
get
these
cards
to
all.
Look
the
same
just
just
right
now
on
the
slipper
side.
E
So
these
have
these
changes
haven't
been
brought
over
to
dub,
dub,
dub
and
yeah.
I
have
this
still
left
to
do
the
marketo
resource
type
formstart.
It's
essentially
like
instrumentation
with
google
analytics,
but
I'm
hoping
to
get
that
out
early
next
week
and
then
my
fourth
point
I
have
onboarding
and
I
have
a
small
bunch
of
handbook
fixes
like
little
like
either
things
that
jess
has
called
out
in
the
past
when
she
did
onboarding
things
that
I
figured
were
issues
with
our
own
handbook
stuff
like
that.
A
Yeah
so
first
up
t
already
mentioned
the
homepage:
compliance
fudge,
section,
there's
still
additional
work
to
be
done
there,
but
the
first
nbc
is
up,
and
I
updated
the
slippers
drop
down
component
that
I
built
previously
so
that
it
had
scroll
functionality
so
clicking
on
it
could
scroll
to
a
certain
location
which
I
hadn't
built
up
before
and
that's
live
on
the
install
page.
Now,
if
you're
on
a
tablet
or
mobile
screen
a
small
screen,
we
also
added
the
user
survey
pop-up
on
the
home
page.
A
A
F
Yeah
so
the
usual
pricing
page
updates.
We
made
some
changes
to
the
list
of
features
that
show
up
under
the
drop
downs
for
each
tier
and
then
some
experiment
cleanup.
So
I
actually
forgot
to
we
remove
the
code
for
the
experiment,
but
I
forgot
to
stop
the
experiment
on
launch
directly,
so
I
had
to
do
that
and
then
clean
up
all
that
stuff,
which
is
fine
and
then
a
lot
of
this
sprint
was
actually
reading
so
jumping
in
and
trying
to
port
the
enterprise
page
over.
F
Obviously,
like
learning
view,
learning
nux
like
all
this
stuff
took
a
lot
of
time,
and
so
I
felt
like
I
just
read
like
20
hours
a
week
of
documentation,
but
now
it's
been
good
and
the
migration
is
going
well
and
then
just
a
bunch
of
like
repo
tweaks
like
adding
sass,
loader
and
figuring
how
nux
content
works
and
making
sure
we're
importing
properly
and
making
things
modular.
So
big
learning
learning
sprint,
we'll
call
it,
but
I
think
that's
it
for
everybody.