►
From YouTube: Recap sprint 6 marketing design system
Description
Related epics, issues, and merge requests :
Related OKR: https://gitlab.com/groups/gitlab-com/marketing/growth-marketing/-/epics/92
Inbound Marketing handbook page: https://about.gitlab.com/handbook/marketing/inbound-marketing/
A
Hello,
everyone
and
welcome
to
the
brandon,
digital
or
sorry
old
habits,
the
digital
experience
teams,
design
system
working
group
and
our
sprint
recap.
What
we'll
be
releasing
this
sprint?
So
yeah
first
thing
up
and
I
can
share
my
screen
here
once
I
find
that
button
is
the
new
pricing
page.
A
So
a
lot
of
work
went
into
this:
a
lot
of
coordination
for
multiple
teams,
a
great
job
on
the
design,
work
from
jess
and
getting
things
sorted
and
building
things
that
we
can
on
a
tight
deadline,
and
you
know
working
towards
later
iterations
of
an
nbc
but
yeah.
We
got
a
lot
of
feedback
that
basically
looks
great
and
the
mobile
experience.
A
lot
of
people
were
impressed
with
that.
So
and
we've
already
done
some
iterations
on
it
to
add
you
know:
navigation,
tabs
and
other
cool
stuff.
B
Thanks
brandon,
let
me
share
real
quick
here:
okay,
so
I've
spent
this
week
working
using
usertesting.com
to
do
card
sorting
and
there's
150
features
right
now
on
that
pricing
page
that
brandon
just
showed,
and
our
goal
is
to
group
them
and
kind
of
organize
them
in
a
fashion
that
will
make
it
much
easier
for
our
potential
buyers
to
find
what
they're
looking
for
in
case
they
want
to
like
compare
us
to
another
company
or
something
like
that
they
can
easily
just
go.
Oh
I'm
interested
in
security.
B
Let
me
drill
down
to
security
and
see
what
your
features
are.
So
I'm
wondering
like
90
of
the
way
there.
I've
already
got
a
bunch
of
features,
mapped,
and
I
just
had
a
bunch
of
tests
run
overnight,
so
I'm
gonna
hopefully
get
through
them
today
and
maybe,
by
the
end
of
the
day,
we'll
have
our
groups
dvd.
C
Cool
I'll
go
next,
first
one
mean
javi,
so
we
were
able
to
fix
up
some
of
the
post
css
problems
or
the
purge
css
problems
with
the
conditional
class
names
in
the
first
component
in
slippers,
and
so
now
we
got
that
working
as
intended
and
some
ideas
about
how
we
can
abstract
that
out
and
make
sure
it
continues
to
work
as
we
move
forward.
C
Other
things
small
details,
I
added
some
additional
package
manifest
items
for
the
slippers
repository
to
make
publishing
up
to
npm
a
little
smoother
and
give
some
more
details
and
give
us
some
more
places
to
to
drop
the
deliverables
there
and
make
that
usable
outside
of
the
repository
and
then,
following
up
on
that,
I
actually
imported
the
slippers
css
to
about
doculab.com
there's
not
much
there
at
the
moment.
C
It's
just
the
one,
the
one
style
sheet
for
the
one
block,
but
it
is
usable
and
it's
working
and
it's
imported
and
we
now
have
a
foothold
where,
as
we
make
progress
on
slippers,
we
can
reflect
that
progress
into
about
doculab.com,
which
is
super
exciting
and
then
on
top
of
that.
So
right
now,
that's
just
the
css.
Ideally,
I
think
where
we
want
to
be
isn't
a
place
where
we
can
take
this
design
system
and
make
it
usable
across
the
existing
web
properties.
We
have
so.
C
I
added
library
builds
to
the
slippers
repository,
which
means
when
we
publish
it
to
npm,
we
publish
up
a
like
a
full
bundle
that
is
consumable
either
by
browsers
or
webpack
or
whatever
else
we're
using
as
a
bundler,
which
will
give
us
access
to
actual
view
components,
and
there
is
a
path
forward
to
sprinkling
them
through
an
existing
templating.
D
D
Everything
is
now
paying
off
that's
when
we
adjust
anything
on
one
page,
we
can
see
it
affecting
every
other
page
site-wide,
so
this
is
just
a
sample
of
one
of
those
pages
that
we
ensure
that
all
the
elements
are
now
using
our
spacing
from
the
design
system
and
even
some
elements,
such
as
the
anchor
text
that
are
on
some
pages
and
not
on
some
pages.
So
there
are
a
lot
of
variables
all
around
all
these
pages.
That
needs
a
lot
of
work
and
a
lot
of
consistency
and
shout
out
to
steven.
D
I
know
it's
not
here
right
now
there
were
a
lot
of
decisions
we
made
about
stops
like
little
things
like
these
ankle
elements
that
are
now
displaying
like
an
arrow
at
the
end
of
it.
So
it
took
us
some
time
to
collaborate
and
to
decide
on
what
we
really
really
want
from
our
design
system
and
how
we
can
bring
them
onto
the
engineering
side.
So
that
is
all
from
me
for
now.
E
I'll
be
sharing
my
screen
next,
so
give
me
one
quick
second,
so
some
of
the
things
that
I
hope
to
collaborate
with
the
rest
of
the
team
on
is
creating
a
workshop,
which
is
awesome
in
terms
of
like
our
discussion
for
static
site
generator.
It's
helped
us
kind
of
organize
a
lot
of
our
thoughts
that
we've
had
that
are
just
ongoing.
E
I
think
it's
been
quite
a
journey
in
terms
of
the
things
that
we
find
to
be
important,
and
maybe
not
so
important
and
trying
to
find
us
kind
of
a
line
on
what
those
things
look
like
has
been
a
really
interesting
and
rewarding
experience.
I
think,
for
this
team.
E
We
still
need
to
do
a
part
two
for
those,
because
it
ran
quite
long,
which
is
a
good
problem
to
have
that.
We
have
too
much
to
talk
about
so
we're
going
to
be
doing
a
second
part
where
we
complete
this
exercise
and
assign
people
with
fraction
items
so
that
we
can
continue
to
move
forward
on
that
front
very
quickly
as
well
been
working
on
some
documentation
for
slippers.
So
just
getting
mark
down
to
render
within
pages,
which
is
simple,
but
just
we
were
getting
a
little
blocked
by
that.
E
So
just
like
getting
a
lot
of
that
stuff,
I
did
kind
of
like
a
faq
style
like
what
is
the
design
system.
Why
do
you
need
it?
What
is
the
difference
between
a
style,
good
and
a
pattern?
Library
et
cetera,
like
a
lot
of
very
common
things
that
people
come
to,
so
I
just
wanted
to
add
that
in
and
yeah.
B
And
I
think
I'm
bringing
up
the
rear
I
will
share
as
well.
B
So
I
did
a
small
update.
We
gitlab
updated
the
privacy
policy
and
wanted
to
add
a
30-day
notification.
So
now
on
the
home
page
you'll
see
this
small
banner
in
the
corner
that
links
the
privacy
policy.
Faq
turns
a
view
subscription
agreement
and
once
it's
dismissed,
it's
dismissed
forever.
I'll
just
do
a
refresh
refresh,
so
it
doesn't
pop
up
every
time
you're
on
the
page,
so
that
is
live
also,
and
I
will
stop
sharing.
A
Cool
thanks
everyone,
that's
the
end
of
our
recap.
For
this
sprint,
good
job
and
I'll,
we'll
see
you
next
time
later.