►
From YouTube: Slippers Foundation Figma Walk Through
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi,
this
is
stephen
mcguinness
and
jess
hallerin
from
the
inbound
marketing
team.
This
is
a
quick
overview
of
our
figma
asset
file
and
library
that
all
our
designers
use
to
create
mocks
and
user
journeys
early
on
in
any
kind
of
project.
So
I'm
just
going
to
share
my
screen.
A
So
this
is
our
slippers
foundation
package.
This
contains
all
the
basic
elements
that
our
design
system
is
made
up
of
so
type
scale.
We
have
our
grid,
we
have
our
colors
over
here
we
have
our
spacing
and
we
have
some
icons
which
are
subject
to
change
as
well.
Anything
is
in
the
design
system.
We
also
then
have
our
components.
A
We
have
our
buttons.
We
have
radio
buttons,
we
have
forms
with
tooltips,
we
have
some
tables
and
we
have
some
accordions
and
and
down
below
here
we
have
some
blocks
as
well.
This
is
all
a
work
in
progress,
but
this
gives
all
our
designers
access
to
a
library
that
will
help
them,
create
wysiwyg
layouts,
to
test
their
proof
of
concept
and
to
test
in
some
flows,
and
we
provide
things
in
mobile
and
desktop,
and
some
are
reflected
in
code.
A
So
some
are
in
our
storybook
repo
and
built
out
with
with
view,
and
they
can
be
a
direct
er
mimic
of
each
other
and
then
the
whole
purpose
of
this
is
that
they
get
pushed
to
our
shared
library
of
assets,
and
so
designers
can
pull
them
in
use.
Layouts
and
jess
is
going
to
do
a
quick
show
and
tell
on
that
one.
Take
it
away.
Jess.
B
Let
me
just
share
my
screen
all
right,
so
I
just
want
to
kind
of
go
through
how
this
works
and
then
show
an
example
of
how
one
worked
in
real
life.
So
I'm
just
hit
a
here.
Oh
maybe
try
one
more
time
there
we
go
hit
a
and
I'll
just
choose.
You
know
I
can
choose.
I
don't
know,
let's
just
say
an
iphone
11
pro
max
and
then
oh,
you
know
what
I
didn't
add
slippers
to
this,
which
would
really
help.
I
just
pulled
up
a
new
one,
so
here
we
go.
B
B
Let's
so
let's
say
I
want
actually
sorry
doing
this
on
the
fly
there
we
go
so
one
thing
like
you
just
talked
about:
we
have
a
grid,
so
I
can
go
into
mobile,
choose
that
and
I
can
kind
of
turn
it
on
and
off
just
so,
I
can
have
some
guidelines
as
I'm
designing,
to
know
how
it's
going
to
work
on
a
responsive
environment.
B
B
Of
course
how
it's
going
to
go
here,
we
go
semi,
bold,
that's
a
little
bug
I
like
to
deal
with.
You
can
come
in
here.
You
can,
you
know
change
it
to
whatever
it
is
and
it
expands
and
contracts
with
you
just
an
example
of
how
you
kind
of
can
pull
things
in
and
out,
and
then
I
want
to
just
show
you
also.
B
So
we
had
this
featured
partners
template
recently,
just
as
an
example
of
how
we
can
use
the
slippers
design
system
in
a
much
quicker
fashion
than
we
were
starting
from
scratch.
So
we
had
a
content
page
that
said,
okay,
we
have
the
logo
and
a
title
and
a
sub
header,
and
things
like
that,
and
instead
of
just
trying
to
figure
this
all
out
from
scratch,
I
just
went
into
the
slippers
foundation
and
looked
at
the
block
section
over
here.
B
B
So
it's
already
existed,
so
I
don't
have
to
like
rethink
the
whole
thing,
and
I
pulled
it
in
to
down
here
at
the
bottom
here
and
just
reuse
that
whole
block.
So
again,
it
just
saves
us
a
lot
of
time.
We
kind
of
can
trust
that
it's
already
been
vetted.
The
nice
thing
about
it
is
it's
also
already
been
developed
or
is
about
to
be
developed.
So
once
it
comes
down
to
the
sign
we
get
to
code,
then
we
just
pull
that
code
in
and
reuse
it
elsewhere
again.
B
So
it's
saving
both
designers,
time
and
developers.
Time
and
like
you're
able
to
pull
this
quote
block
from
the
blog
design
and
pretty
much
everything
here
was
a
pre-existing
block
or
very
similar.
There
might
have
been
like
a
slight
tweak,
but
it
just
saved
a
ton
of
time
and
it's
able
to
do
this
whole
page,
both
desktop
and
mobile,
in
a
single
day,
which
is
huge
used
to
take
us.
B
You
know
several
days
or
even
a
week
or
more
depending
on
the
content,
but
we
just
kind
of
have
exponentially
increased
our
time
by
using
reusable
blocks
and
elements.
A
Thank
you
and
just
gonna
re-share,
just
a
quick
something
over
here,
just
to
show
how
easy
it
is
that
we
can
make
changes
to
things
so
within
here.
These
are
all
classes
assets
we
can
go
over
here
and
we
can
push
changes
to
any
of
these
libraries.
Obviously
we're
more
focused
around
slippers,
and
it
tells
us
right
here
that
it's
published
and
up-to-date
if
we
ever
make
a
change
or
an
edit
to
any
of
these.
A
The
change
gets
pushed
to
the
cloud
and
designers
get
who
are
using
certain
components,
get
the
option
to
pull
in
the
new
and
up-to-date
version
of
things
not
gonna
happen
with
colors
can
happen
with
type
or
bugs,
or
anything
like
that.
So
it
gives
us
a
lot
of
high
level
interaction
with
all
of
the
designers
we're
all
working
from
the
latest
and
greatest
version
as
well.
We
don't
have
to
reinvent
the
wheel.
A
We
don't
have
to
go
search
to
a
file,
it's
all
done
for
us
and
we
get
the
option
to
sync
with
our
master
files
as
well
and
so
yeah.
That's
about
it.
Just
wanted
to
give
a
quick
overview
of
how
quick
and
easy
this
workflow
is
for
us
as
a
team
and
scalability
that
it
has
and
how
it's
also
reflected
in
code,
and
we
use
this
to
build
upon
slippers
each
time
and
we're
always
looking
to
improve
this
as
we
go.
So
this.