►
From YouTube: Recap sprint 4 marketing design system
Description
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
What's
up
everybody,
this
is
digital
experience,
retro
for
the
design
system,
team,
we're
gonna
be
talking
about
our
last
two
week:
sprint
and
we're
just
gonna
go
over
some
of
the
docs
that
we've
been
kind
of
writing
and
ideating
together.
So
some
of
our
action
items
from
last
our
last
retro
we're
trying
to
just
make
sure
that
we
are
kind
of
following
up
with
some
of
those
we
have
file
organization,
as
one
and
team
feel
free
to
stop
me.
If
there's
something
in
particular,
you
want
to
talk
about.
B
We
just
share
the
screen,
so
people
can
see.
A
Oh
yeah,
for
sure,
let
me
share
it.
Okay,
do
you
all
see
this?
Yes,
okay,
so
file
organization
decide
on
css
framework,
looking
to
discuss
with
stakeholders
about
no
longer
supporting
ie,
discussing
research
methods
and
meet
with
technical
people
to
align.
A
I'm
going
to
be
talking
about
things
that
people
thought
went
well,
progress
made
in
all
directions.
What
feels
like
getting
synced
up
as
team
slippers
generates
css
file
nbc3
of
home
page
went,
live
looking
much
better,
quick
turnaround
on
improvements
to
the
homepage.
Ctas
quick
turnaround
on
the
banner
to
bring
back
marketing
announcements
storybook
until
when
css
works
smoothly
and
get
lab.
A
I
think
this
is
related
to
our
repo
health
in
general
and
there's
a
lot
of
branches
that
we
don't
know
what
they
do
in
terms
of
things
that
people
have
pushed
up,
but
we're
not
sure
exactly
if
people
are
working
on
them,
so
just
trying
to
maintain
good
repo
health
and
this
kind
of
falls
in
with
this
next
point
here,
branding
version
best
practices.
A
I
think
this
is
like
a
long
conversation
that
we
can
have,
but
I
think
marketing
in
general,
like
the
developers
of
marketing,
want
to
make
sure
that
we're
all
aligning
on
how
to
write
styling
so
that,
if
I'm
writing,
styling
or
sammy
is
writing,
styling
or
brandon.
Is
writing
styling?
It
all
feels
like
it's
the
same.
I
think
that
helps
with
outward
communication
so
that
people
know
what
styling
should
look
like
on
the
site
naming
conventions.
C
C
C
But
I'm
not
sure
what
the
return
at
this
point
on
is
for
doing
that.
So
it
may
be
a
good
idea
to
write
up
an
issue
just
as
as
a
shell
issue
for
grooming
that
we
can
kind
of
see,
someone
do
a
you
know
a
time-boxed
analysis
and
you
know
see
what
they
recommend.
I
think
would
probably
be
the
action
item
there.
C
Can
you
sum
up,
your
action
item
really
quickly
sure
sure
create
an
issue
to
research
recommendations
for
reducing
items
files
in
the
repo.
I.
D
A
Yeah,
something,
I
think
would
help
is
I
don't
know
what
text
editor
you
all
use,
but
for
vs
code
you
can
kind
of
the
search
functionality
for
that
is
actually
really
smart,
even
if
you
don't
aren't
super
familiar
with,
like
grip
so
like
for
regular
expression
searching.
So
I
would
think
that's
also
a
good
way
kind
of
to
double
check
like
where
things
are
being
used.
C
C
C
I
I
was,
I
was
just
going
to
say.
I
think
it
looks
like
the
next
item
on
the
list.
Maybe
is
the
oh
aligning
what
we
want
for
accessibility
that
could
be
action.
Item
is
well.
I
I
think
in
the
past
we've
discussed
that
kind
of
as
like
within
well,
so
accessibility
is
done
whenever
we
create
each
designing
component
and
code,
but
it's
also
the
the
question
of
aligning
on
what
we
want
for
it.
C
I'm
not
sure
what
the
action
item
is
there
other
than
maybe
to
define
in
what
ways
we're
trying
to
be
accessible.
I
guess
yeah,
that's
pretty.
E
Yeah,
I
was
going
to
say
with
accessibility.
It's
there's
often
like
a
service
level
idea
of
what
accessibility
is,
but
when
you
actually
go
into
it,
there's
a
lot
more
nuanced
approaches
that
we
might
have
to
adhere
to
in
terms
of
like
how
it
replicates
as
well.
It
leverages
on
top
of
the
product
in
terms
of
that
type
of
accessibility,
so
there's
obviously
screen
contrast
and
and
general
website
accessibility,
but
then
there's
code,
accessibility
and
then
there's
screen
reader
and
things
like
that.
C
Yeah,
I
think
products
has
more
resources
and
more
optimistic
goals.
Then
maybe
we
can
achieve,
but
it's
it's
a
good
starting
point.
Like
you
said
to
kind
of
research,
I
I
like
the
mention
of
kind
of
the
the
service
level
agreement.
Sort
of
you
know,
basically
what
we
aim
to
do
whenever
we're
building
each
new
thing.
I
guess,
and
you
know,
maybe
we
get
80
coverage
or
60
coverage.
How
do
we
measure
that
coverage?
I
guess
so
having
a
list
where
we
can
say
we
got
to
80
of
these
things.
C
Next
mvc
will
maybe
be
100
or
something
like
that.
So.
B
Yeah
have
some
accessibility
documents
and
checklists
from
like
a
two-day
thing.
We
did
at
my
last
company
with
a
accessibility
like
agency,
so
I
can
definitely
share
those
out
with
you
guys,
and
maybe
we
can
use
those
as
well
as
like
a
starting
base.
D
Yeah,
that
would
be
great,
and
I
have
a
couple
of
some
documents
like
that
too,
because,
like
what
stephen
said,
there's
a
lot
in
accessibility,
for
example,
button
rules
and
all
that
when
you
click
it,
but
in
the
role
of
that
button
you
need
to
define
it
what's
the
button
intended
to
do
maybe
for
someone
using
the
screen
reader
if
it's
a
pop-up,
the
pop-up
needs
to
announce
itself.
But
if
you're
not
bothered
about
those
demographics
of
users,
then
you
are
web
accessible.
D
B
Well,
yeah
that
came
for
me,
brandon's,
probably
wearing
this.
We
just
the
the
logos
that
we
have
available
for
us
to
use
right
now
are
generally
not
like
super
well-known
companies.
I
mean
there's
a
few,
but
I
would
love
to
know
like
who
owns
that
space,
so
you
can
talk
to
them
and
see
like
if
there's
any
other
ones
coming
up.
I
had
seen
like
I
don't
know
this
public
knowledge,
but
there
was
a
large
company
who
asked
to
use
our
logo,
and
so
it
was
just
like
a
slack
thread.
B
A
C
So
I
know
there's
a
handbook
documentation
around
it,
but
that
doesn't
mean
it's
necessarily
up
to
date.
We
can
check
in
with
michael
and
becky,
and
probably
someone
in
content,
marketing
and
partnership
or
partner
marketing.
That
might
know
those
kinds
of
questions.
C
Do
they
have
a
slack
channel,
probably.
B
It's
also
me,
as
we
may
know,
we've
had
a
rough
rocky
road.
So
far
I
don't
know
if
we've
like
completely
burned
our
bridges
with
them,
but
I
also
don't
know
what
we
could
have
done
differently
to
get
the
end
result.
So
I'm
just
thinking
more,
like
broadly,
like
we've
been
nice
to
maintain
that
relationship
and
hopefully
be
able
to
work
with
them
in
the
future.
But
right
now
it's
it's
not
looking
so
good.
C
Yeah,
I
think,
having
followed
the
thread
a
bit,
I
would
kind
of
phrase
it
as
like.
Basically,
different
teams
focused
on
different
goals
focused
on
you
know
their
their
own
product,
we're
on
marketing.
You
know
they
have
their
processes
in
place.
Maybe
you
know
you
know
we
reach
out
for
help,
and
you
know
their
timelines
and
methodologies
might
not
match
up
with
marketing
best
practices
or
methodologies.
So
it's
it's
kind
of
just
it's
not
that
we
don't
want
to
work
with
them.
They
don't
want
to
work
with
us.
It's
just
like
we.
C
We
have
different
priorities
and
goals
at
the
moment,
so
you
know
learning
what
we
can
from
them
and
they'll.
You
know
we'll
share
our
learnings
with
them,
one
of
the
things
that
helped
when
we
were
growth,
marketing
team.
We
would
share
information
with
growth,
product
team
and
you
know
back
and
forth.
So
we
formed
a
channel
that
we
can.
All
you
know,
collaborate
in
and
stuff
like
that,
it's
more
of
a
long-term
goal,
but
yeah.
That's
that's
kind
of
my
thoughts
on
that
at
the
moment.
C
Yeah,
I
think
that's
definitely
a
possibility
or
or
even
you
know,
maybe
a
working
group
like
hey.
You
know
we
have
this
research
project
that
we're
working
on.
Do
you
have
any
recommendations,
even
though,
following
that
issue,
there
was
a
lot
of
back
and
forth
already,
but
it's
differently
asynchronous
to
work
in
an
issue
versus
having
chats
and
slack
and
zoom
and
all
that
kind
of
stuff.
So
yeah.
C
A
So
that's
I.
A
I
was
like,
let's
not
just,
prescribe
a
solution
for
your
problems
that
you
deal
so
no.
A
A
Sounds
great:
okay,
get
more
out
of
storybook
html
write,
md
docs.
I
think
this
is
kind
of
what
we
were
talking
about
a
little
bit
offline
when
we
were
saying
about
finding
ways
to
make
docs
just
more
publicly
accessible
like
finding
out
like
what
works,
not
only
just
for
developers
but
for
the
whole
working
group.
A
I'm
pretty.
I
think
it
sounds
like
we're
pretty
open.
We've
talked
about
handbook,
we've
talked
about
creating
or
creating
our
own
page.
A
Storybook
yeah
I'm
question
mark
on
storybook,
just
because
the
way
I
I
have
to
look
further
into
it
because
out
of
the
box
straight
away
default
configuration,
I
tried
just
to
render
markdown
files
and
it
was
like
not
liking
that
too
much
so
just
setting
it
up
so
that
we
can
do
that.
But
I
don't
think
that
would
be
too
difficult
to
do
with
another
tool,
for
instance
within
that
same
repo,
if
storybook
itself
doesn't
work.
I
just
thought
of
that
idea.
Right
now
and
it's
like
oh,
we
could
do
that
as
well.
C
Yeah,
so
I
think
one
of
the
things
we
had
talked
about
earlier
is
kind
of
just
getting
it
started
somewhere,
and
so
maybe,
if
we're
not
set
up
with
storybook,
yet
you
know
wherever
that
first
place
we
choose,
is
you
know
just
action
item
creating
an
issue
starting
documentation
wherever
it
gets
put,
is
tbd
but
yeah.
That's
that's
kind
of
the
theory.
I
think
there.
A
Yeah,
I
think
it
makes
sense
to
create
an
issue
just
to
put
things
in
the
handbook,
and
what
we
can
do
is
link
out
to
other
places.
If
we
end
up
moving
where
that
location
is
so
just
say
like
this
is
where
we're
putting
our
documentation
right
now
and
just
put
everything
there
and
then
once
we
have
a
more
dedicated
place
for.
B
A
A
I
think
we
need
to
discuss
the
not
supporting
ie
more
explicitly
from
the
engineering
side.
D
C
C
D
A
All
right:
well,
this
is
our
retro.
Hopefully
we
can
do
something
about
these
action
items,
but
what
I
can
do
is
I
really
like
the
ish.
I
think
I've
gotten
better
with
issue
writing,
so
I
can
start
putting
these
in
and
then
we
can
start
collaborating
on
this
for
our
work.
While
everyone
is
away
so
thanks,
everybody
see
you
all
soon.