►
From YouTube: Digital Experience Release Video - Nov 4, 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
A
Hi,
everyone
welcome
to
the
digital
experience
teams,
sprint,
release,
video
or
iteration
release
video
we'll
go
over
what
we
worked
on
for
the
last
two
week
period,
I'm
up
first,
so
I
will
go
ahead
so
first
off
I
have
one
trust
updates.
There
have
been
some
some
carryover
pieces
for
one
trust,
namely
the
docs
team
added,
one
trust
into
their
repo
and
the
gitlab
team
added
one
trust
to
certain
pages
in
the
gitlab
repo.
A
So
those
are
the
get
lab
repo
one
is
live
now
I
think
docs
is
being
released
today.
So
that's
exciting.
You
know
the
helping
out
with
those
teams
and
then
we
also
updated
the
one
truss
script
to
allow
auto
blocking,
and
that
happened
in
both
w
and
in
the
core
new
core
site
repository,
and
then
I
updated
the
handbook
also
to
reflect
those
changes.
A
And
then,
after
that
I
worked
on
the
footer
updates,
and
so,
if
you
want
to
click
on
and
be
there,
the
minimal
footer
thing
wait.
Is
it
frozen
for
yeah?
No
okay,
there.
A
Yeah,
so
if
you
go
to
that
free
trial
down
in
the
footer,
that's
the
new
minimal
footer
has
a
cookie
preferences
tab
and
then
in
the
big
footer,
not
huge
differences.
You
know
way
down
the
cookie
preferences.
Tab
is
now
under
the
company
banner
and
at
the
very,
very
bottom
for
those
links
that
say,
like
huge
view,
page
source
view
web
ide,
those
used
to
have
a
little
underlying
space
beside
them
and
it
drove
me
nuts.
A
So
I
got
rid
of
those
as
well
and
then
we
updated
our
some
of
the
trademark
test
text
and
stuff
there.
So
that's
in
both
this
www
repository
and
in
the
core
site,
and
then
I'm
working
on
the
stages
of
devops
like
cycle
page
there's
a
lot
of
content
missing.
So
that's
in
progress
and
then
I
added
a
gray
background
component
to
the
core
site.
Lauren
pointed
out
that
you
know
we
weren't
doing
this.
A
The
best
way
thanks
parker,
and
so
I
just
built
out
a
new
component
that
allows
us
to
use
a
gray
background
on
certain
pieces.
And
lastly,
I
finished
up
the
ce
versus
ee
page.
So
this
is
yeah
under
the
install
subdomain
jess
and
a
number
of
other
people.
Dylan
have
been
working
on
this,
so
yeah
much
simpler
page
compared
to
what
was
already
existed
in
the
live
site.
So
that
should
go
out
today
and
that's
it
for
me,
and
next
is
tina.
C
Hi
thanks
so
the
first
item.
I
did
some
maintenance
and
slippers
the
the
figma
slippers
and
I
tried
to
focus
on
links
because
I
noticed
some
inconsistencies,
particularly
on
the
home
page,
with
our
buttons,
sometimes
having
arrows,
sometimes
not
having
arrows,
sometimes
the
arrows
wrong
and
then
just
ended
up
doing
a
deep
dive
and
updating
a
bunch
of
other
interaction.
Styles.
C
So
I
worked
on
buttons
links,
tool,
tips
and
accordions
they're,
now
more
succinct,
more
consistent
and
have
documentation
in
figma
on
how
to
use
them,
and
next
I
also
took
a
look.
I
did
a
bit
of
due
diligence
on
the
ux
for
the
pricing
page
pop-up
that
I
believe
nathan
was
going
to
work
on
this
iteration.
I
just
wanted
to
make
sure
that
everything
was
a-okay
and
we
weren't
making
a
huge
mistake
in
adding
this
pop-up.
C
Maybe
an
iterative
approach
on
how
we're
going
to
handle
that,
since
there
are
so
many
eyes
on
that
page,
so
I
also
added
readmes
to
the
file
and
updated
link.
Styles.
The
other
item
is,
I
worked
on
the
features
page.
C
I
created
a
second
iteration
of
the
features
page,
which
I
believe
nathan
is
also
going
to
be
working
on.
I
added
some
additional
interaction
to
reduce
effort
and
support
information.
Seeking
I
added
a
tabbed
ui,
as
you
can
see
at
the
top
some
filtering
options.
I
also
highlighted
highlighted
some
product
categories.
C
It's
a
bit
larger
in
scope
than
the
original
design,
but
we
can.
We
can
do
this.
This
iteratively,
I'm
pretty
confident
about
that,
and
I
see
that
I
believe
barker
added
d
to
the
list
adjust
logos
on
the
homepage.
I
haven't
read
the
issue
yet,
but
I
will
be
working
on
that
and
delivering
that
today.
B
B
I
don't
know
if
we're
gonna
need
this
now
that
docs
is
gonna,
have
one
trust
which
is
awesome,
but
I
still
think
that,
like
this
approach
of
starting
to
track
like
traffic
from
different
areas
of
not
just
about
but
outside
of
that
realm
to
the
pricing
page
will
help
us
know
like
what's
getting
people
to
pull
out
their
wallets,
so
that's
helpful
and
then
so
I
did
the
same
for
their
cta
on
the
docs
page,
so
the
on
the
main
navigation
on
the
right
hand,
side
there's,
like
a
query
string
attached
to
the
cta
of
that.
B
So
that'll
help
us
again
with
knowing
what
that's.
What's
going
on
with
that
right
here
I
have
add
marketing
alert
boxes,
10
pages
guiding
for
trial,
we're
still
figuring
out
where
we're
going
to
put
this,
but
I
wanted
to
just
show
what
it
is.
I
don't
think
I've
showed
it
before
like
this
call
out.
So
this
is
what
it
looks
like.
This
is
wonderful
great.
I
did
not
do
the
development
for
this.
B
This
was
like
people
on
docks,
so,
but
essentially
all
I'm
doing
is
putting
it
in
the
pay
each
and
finding
out
like
what
this
url
goes
to
and
like
the
content
and
whatnot.
So
that's
that,
let's
see
what
else
we
have
so
we
have
add
feature
availability
hub
section
at
the
top.
This
is
actually
like
again
related
to
ducks,
but
it's
more
so
something
that
stays
permanent
across
all
pages
of
ducks.
So
this
is
like
essentially
being
pulled
from
over
here.
B
This
section
right
here,
essentially
just
something
over
here-
and
this
is
the
first
nbc
for
this
design-
a
suggestion
that
they've
created
on
growth
from
the
ux
team,
and
so
I
also
linked,
I
believe,
the
designs
of
what
it
looks
like
what
the
final
version
of
it
should
look
like.
So
there's
that
there
I
have
navigation
stability.
B
This
essentially
is
fixing
all
of
our
mess
when
it
comes
to
making
sure
the
navigation
looks
proper,
both
in
the
www
repository
and
the
buyer
experience
there's
been
like
lots
of
weirdness
with
them,
so
just
making
sure
that
across
both
sites,
this
looks
consistent.
This
isn't
something
that
we've
always
hit.
B
The
mark
on
so
just
making
sure
that,
like
all
the
little
things
that
happen
as
you
switch
between
and
then
tina
wrote
a
comment
that
this
is
404,
I
believe
the
issue
is
confidential,
so
I
don't
know
if
that's
being
yeah,
sorry
I
can.
I
can
show
it
to
you
tina
just
so
that
you
can
see
like
afterwards,
so
but
yeah,
that's
it
for
me
up
next
is
lord
bye.
D
So
I
don't
know
if
y'all
noticed,
but
we
have
a
digital
experience
sub
group
now
and
like
that
is
not
where
that
was
supposed
to
go
wow
here.
Let
me
go
find
that
link
and
drop
it
in
for
you
in
the
yeah.
D
D
D
Such
a
like
lead
up
to
a
fail
there.
There.
It
is
digital
experience,
group
and
what's
really
cool
about
this-
is
we're
going
to
put
our
repos
here
and
our
projects
and
issues
and
the
issue
can
live
in
the
project
and
you
can
create,
mr
straight
from
it
and
all
kinds
of
amazing
stuff.
We
have
three
projects
there
right
now,
onboarding
for
our
digital
experience,
team
members-
and
this
is
where
all
of
our
new
team
members
have
specific
issues
for
onboarding
to
our
team.
D
D
I
created
a
solutions
template
for
our
cut
wow.
That
was
a
word
vomit
created
a
solutions
template
for
in
the
buyer
experience
journey,
so
we
have
a
solutions:
template
that's
in
the
dub,
dub
dub
repo,
and
it's
like.
Okay.
We
need
to
build
this
in
our
buyer.
Experience
repository,
so
I
went
ahead
and
did
it-
and
here
it
is.
D
I
still
have
some
tweaking
to
do,
but
what's
really
cool
about
this,
is
it
utilizes
us
to
build
a
series
of
pages
that
live
in
a
data
directory
defines
what
the
routes
are
and
it's
adding
a
whole
bunch
of
new
components.
So
it's
cool.
It's
like
the
first
step
to
really
starting
to
build,
build
out
lots
of
pages.
D
I'm
really
excited
to
get
that
out
the
door
disabled,
the
global
banner,
and
there
is
a
hotfix
for
doing
that.
We
had
a
banner
about
the
ipo
we
just
had
to
take
that
off.
The
site
worked
on
setting
up
projects
for
onboarding
our
new
team
members
and
then
created
an
epic
within
our
digital
experience
group
that
then
links
to
our
buyer
experience
project.
D
Where
is
visual
quality
assurance
issues
for
a
whole
bunch
of
different
devices
browsers
and
then
in
the
same
project
they're
going
to
create
issues
for
when
they
find
things
that
are
like
whoa
that
looks
weird
and
we'll
have
a
nice
catalog
of
things
we
got
to
work
on,
which
is
awesome.
This
next
one's
super
exciting.
We
had
this
epic
community
contribution
where
we
upgraded
to
middleman
442,
and
this
guy
also
collaborated
with
the
maintainers
of
middleman
to
get
them
to
actually
bump
the
version
of
middleman
for
us,
just
like
wow
really
cool.
D
So
that's
live.
Let
us
know
if
there's
something
funky
there,
a
bunch
of
content
updates
that
went
out
and
then
a
couple
regression
patches,
the
big
ones
are
for
our
blog
posts.
If
you
hop
down
to
them
just
skipping
over
those
content
updates,
it's
just
content
the
our
blog
post.
If
you
scroll
down,
oh
whoa,
wait,
go
back
up
up
up
up
up
up
up
mermaid
way
up
up
up
up
a
little
more
really
good
for
those
mermaid
charts
there.
D
They
are
yeah
those
things
we
had
a
regression
when
I
enabled
our
blog
navigation
helpers,
didn't
re-enable
those
mermaid
charts
and
so
now
they're
enabled
that
was
cool
and
then,
if
we
scroll
all
the
way
to
the
bottom,
our
disk
comments
are
now
confined
into
the
the
container
they
were
spreading
100.