►
From YouTube: Design tokens walkthrough
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
Well,
let
me
show
my
screen:
okay
and,
as
you
can
see,
there's
a
there's.
A
few
tabs
open,
there's
a
few
things
going
on.
Okay,
so
what
I'm
I
think
the
Crux
of
it?
A
What
I'm
trying
to
get
a
better
understanding
of
is
how
sort
of
tokens
or
token
like
kind
of
structures
are
used
in
figma
at
the
moment
there
is
a
disconnect
at
the
moment
between,
like
a
formalized
design,
token
kind
of
spec
that
there's
a
draft
order
of
or
like
we
call
it
standard
being
written
at
the
moment,
there's
style
dictionary
and
how
it
works.
And
then,
let's
figure
out
how
it
works.
A
You
can,
you
know,
translate,
transform
content
between
all
those
things
as
much
as
you
like,
but
there's
some
decisions
that
kind
of
inform,
maybe
how
we
want
to
go
for
like
Simplicity
or
ease
of
use,
where
this
kind
of
has
what
what
I
would
love
to
have
more
of
an
understanding
of
is
we
have
flat
values
so
you'll
have
something
like
blue
500
equals.
You
know
hex
code
and
those
things
map
really
really
well,
when
we
have
what
is
called
like
composite
values,
essentially
objects.
A
So
things
like
Shadows
or
typography-
that's
where
there's
maybe
architectural
decisions
to
be
made,
how
those
things
talk
between
tools,
how
they're
consumed
in
CSS
or
by
components
at
the
moment
I
can
see
two
kind
of
Pathways
one.
We
just
have
yeah.
This
is
very
early
stuff,
but
a
flat
structure.
A
A
We
can
use
that
reference
in
a
composite
value
that
is
used
for
figma,
so
we
can
create
an
object
which
has
oh,
my
goodness
here.
If
I
look
at
something
like
this,
the
font
weight,
size
line,
height.
A
I
was
playing
around
with
shadows
and
how
we
have
them
represented
in
figma,
and
these
at
the
moment
are
yeah
multi-line,
CSS
kind
of
things,
and
you
can
see
the
example
that
I've
got
here,
where
it
might
be
nice
to
reference
the
color
gray,
so
that
that
can
transform.
Although
that
was
my
smart
idea
yesterday
this
morning,
I
was
like,
maybe
not
because
that
may
not
be
desirable
for
like
when
dark
mode
switches
back.
You
may
not
actually
want
the
1950
like.
A
So,
okay,
so
that's
a
really
good
segue
into
how
thick
how
we're
currently
using
I'm
going
to
use
like
Styles
in
figma,
because
I
think
that's
what
they're
called
like
the
we
might
have
here
like
yeah,
neutral
900,
or
something
like
that
yeah.
How
we're
currently
using
those
I
know.
I
was
reading
through
some
of
the
documentation
around
figma
use.
A
A
A
How
do
we
currently
use
them
and
what
else
the
question
I
have
is
when
we
have
do,
we
have
anything
beyond
sort
of
the
the
bass
Styles
like
blue
500.
Do
we
do
anything
like
button
button,
confirm
or
Shadows
or
anything
like
that.
B
Yeah
so
in
figma,
I
think
that
two
parts
to
your
question,
the
first
in
relation
to
how
we
might
get
tokens
or
work
with
tokens
in
figma,
yeah
I,
think
that
the
the
main,
oh
gosh,
the
main
plug-in
it's
the
the
names
kind
of
evading
me
right
now,
but
the
style
token
or
whatever
that
main
component
or
the
plug-in
extension
is
that's
something.
B
We've
looked
at,
however,
with
with
figma's
events,
I
believe
next
week,
I
think
it
is
I,
think
it's
I
think
that's
when
config
is
there's
talk
that
there
might
be
native
token
support,
so
we've
been
kind
of
holding
out
for
that
when
foundations
a
little
background
when
foundations
decided
to
work
on
or
to
take
a
look
at
priorities
for
the
year
tokens
is
was
like
high
on
the
desired
list,
but
we
also
decided
you
know
what
we're
just
not
quite
ready
for
it
yet,
and
we
want
to
wait
for
more.
B
You
know
ability
more
time
from
engineering,
but
also
we
wanted
to
wait
to
see
what
figma
was
going
to
do
in
this
next
kind
of
push.
So
that's
where
we're
at
with,
like
the
plug-in
thing
is
like:
don't
really
want
to
rely
on
a
plug-in
dependency
if
we
can
help
it
and
and
so
seeing
if
they
support
anything
native,
if
they,
if
it
comes
out
and
they
don't,
then
we'll
we'll
look
to
to
look
at
some
of
those
options.
B
So
that's
that
as
far
as
the
actual
styles
in
figma,
they
are
pretty
flat
right
now.
If
you
want
me
to
share
I'm
I
would
be.
B
Okay,
so
in
figma,
let's
go
over
here.
This
is
what
we've
got
right
now,
so
we
have
textiles,
color,
styles
and
effect
Styles,
and
there
are
some
grid
Styles.
The
grid
styles
are
used
internally,
like
hey,
I
want
to
set
up
a
16x16
icon
grid
whatever,
and
some
of
these
other
ones
are
just
purely
for
more
like
helper
stuff,
so
nothing
official
that
we
would
push
out
to
the
system.
B
We
do
have
some
deprecated
stuff,
so
textiles,
for
example,
breaking
it
down
into
UI,
where
we
have
display
H1
H2
at
the
different
break
points.
So
the
the
sizes,
paragraph
mono
label-
and
let
me
know
if
I'm
flipping
through
any
of
these
too
fast
and
whatnot
I,
could
probably
pull
out
an
entire
list
of
these.
For
you
somehow.
A
B
If
you,
let's
see
here,
I'm,
assuming
that
you
don't
have
like,
like
the
editor
license
for
figma,
but.
A
B
You
just
have
the
inspect
mode
right,
so
you
can
only
see
what
you
click
on.
Is
that
correct?
Okay,
yeah
yeah,
perfect?
If
you
were,
if
you
just
made
a
copy
of
this
to
your
drafts,
you
should
have
a
full
list
of
everything
in
there
and
then
you
could
view
that
in
the
edit
mode,
so
all
the
type
Styles
pretty
flat
right
now
they
are
pretty
descriptive
names.
So
it's
it's
very
much
a
h.
You
know
H1
XL,
H1,
medium
break
point,
so
they're
very
descriptive,
not
abstracted
at
all
same
with.
B
You
know,
paragraph
regular,
large,
Etc,
and
so
that's
it
for
you
know
type.
Then
we
get
into
there's
things
for
like
avatars
that
we
have
in
here
like
the
identicon
large.
These
are
actually
textiles
as
well,
but
just
you
know
we
would
use
in
like
this
for
the
Avatar,
just
as
a
style,
you
know,
given
that
it's
used
for
one
thing,
it
might
not
even
be
necessary
to
be
a
style,
so
it's
something
that
we
wouldn't
necessarily
have
to
push
forward
to
anything
see
documentation.
B
This
is
all
internal
just
to
the
file.
So
you
know
when
we
want
to
just
consistently
style
like
these
kind
of
headings
and
whatnot
it's
using
like
documentation
heading
so
it's
in
the
own
category
and
then
all
the
color
styles,
which
you're
already
familiar
with.
B
So
and
then
we
have.
We
do
have
transparent
color
styles,
which
would
take
either
a
neutral
of
950,
with
a
different
percentage,
usually
base
eight
separations
and
then
white
with
a
few
of
those
and
then
all
the
themes
that
are
used
today
as
well.
We
have
styles
for
the
focus
ring,
and
this
is
once
again
maybe
figma
specific
just
to
allow
us
like
an
inner
and
an
outer
Focus
ring
so
depending
on
the
the
component.
B
We
have
that
concept
today,
where,
like
on
a
a
drop
down,
that
elements
probably
going
to
use
an
inset
Focus
ring
and
also
it
doesn't
break
out
of
the
bounds
versus
a
button,
is
going
to
be
on
the
outside.
So
we
just
have
multiple
styles
to
help,
support
that
there's
Avatar
color
styles,
which
contain
fill
and-
and
so
they
they
just
have.
The
the
different
image
fills
just
to
make
it
easy.
A
B
So
again
those
probably
don't
need
to
be
extended
brand
this.
So
the
brand
color
palette,
which
that
one
I
I
mean
it'd,
be
probably
nice
to
include
just
because
you
know,
maybe
if
we
do
anything
with
the
Tanuki
with
the
SVG
I
I,
don't
know
there
might
be,
might
be
some
some
room
there
to
work
with
then
there's
so
that's
typography.
Then
there
are
effect
styles.
B
So
we
have
like
this
pagination
it's
it's.
Basically,
it
looks
like
a
maybe
a
top
border.
Let
me
just
see
here
inner
Shadow,
so
it
has
something
to
do
with
the
individual
pagination
items.
So
the
way
the
borders
overlap
and
whatnot
I
think
it's
using
the
inner
Shadows
to
kind
of
facilitate
that
I'd
have
to
look
to
see
if
that's
actually
being
used.
B
I
could
look
at
a
say
with
some
time.
I'll
I
can
inspect
that
later
and
then
there
are
styles
for
like
table
so
there's
a
table
border
so
different.
B
The
cell
and
again
some
of
these
are
you
know
very
specific
to
just
figma
implementation
and,
and
quite
honestly,
some
of
these
could
probably
be
removed.
Now
that
figma
supports,
like
the
independent
borders
like
these
might
be
a
little
outdated
right,
because
if
it's
using
an
inner
Shadow
now
just
to
do
that
right
border,
we
can
just
do
like
a
right
border
now
in
figma.
So
so
some
of
these
are
a
bit
outdated
and
you
know
feel
free
to
stop
me
at
any
point.
B
If,
if
this
is
a
bit
Overkill
here,
but.
B
Segmented
control,
like
it's
another
component,
specific
one
with
the
borders,
and
you
know
what
segment
control
is
actually
deprecated,
so
I
should
deprecate
those
Styles.
That's
a
good
thing
to
do.
B
I'm,
recording
this
so
I'll
make
sure
that
I
go
back
and
take
some
notes
for
myself
layer
Shadows.
So
we
have
the
small
medium
and
large
what
what
you've
seen
already
that
are
kind
of
constructed
of
multiple
drop
Shadows
that
have
different
values
and
I'm
I'm,
pretty
sure
you're
familiar
with
the
concept
of
why
you'd
have
multiple
Shadows
for
the
different
depth
and
yeah.
So
yeah.
A
B
Perfect
tabs,
so
the
active
hover
once
again,
this
is
using
the
border
which
could
probably
be
updated
or
I'm
sorry
they're,
using
the
inset
Shadow,
which
could
probably
be
updated
to
to
leverage
border
instead.
B
Sidebar
same
thing.
This
is
probably
navigation
specific.
So
it's
again
it's
it's
nothing
really
system
button,
Shadow,
I,
don't
I,
don't
even
know
if
this
is
actually
used.
I
think
it
might
be,
although
very
subtly
there's
an
input,
focus
on
the
form,
just
a
separate
style
and
block
quote.
So
that's
that's
kind
of
the
I
guess
the
the
bulk
of
it
like,
like
I,
said
these
other
items
are
are
probably
meaningless
when
it
comes
to
the
system.
B
A
But
that
seems
in
a
really
good
place
actually
so
that
and
it's
good
that
you
mentioned
the
figma
config
conference
or
whatever
it
is
because
that's
the
Crux
of
it
right.
So
the
color
one
is
really
straightforward,
except
if
you
want
to
you,
know
rename
gray
to
neutral
or
something
like
that.
We'd
have
to
update
the
references.
Yeah,
that's
a
subjective!
Take
because
I
can't
spell
gray.
A
Know
yeah
original
spelling
for
some
reason.
So
yes,
so
the
independent
styles
for
like
button
and
those
sort
of
things
largely
seem
like
workarounds
for
limitations
or
previous
limitations
in
figma,
the
rest
of
the
references
colors
and
those
map
pretty
much
one
to
one,
that's
pretty
straightforward,
and
then
things
like
Avatar
or
any
of
those
are
sort
of
you
know
can
be
specific
to
figma.
A
So
I'll
give
you
some
context.
Why
I'm
thinking
this
way
and
I
don't
want
to
take
up
all
your
evening
is
because
with
tokens
it
can
kind
of
be
a.
A
You
know
how
long
is
a
piece
of
string
kind
of
thing,
so
there's
so
what
I'm
doing
in
this
Prima
concept
is
I'm,
trying
to
validate
all
the
different
caveats
that
we
might
find
so
during
this
week,
I've
been
going
through
this.
This
is
what
I'm
calling
Rabbit
Hole
week
every
day
is
like
a
new,
a
new
subject:
I'm
going
to
dive
into
that.
A
So
one
was
the
wherever
the,
where
it
is
this
one,
the
Community
draft
report,
so
the
community
draft
for
design
tokens
how's
that
different
from
style
dictionary,
the
creative
style
dictionary
is
a
member
of
this
team.
A
Is
there
anything
major
in
here
that
could
impact?
You
know
future
proofing,
making
decisions
that
sort
of
thing
one
of
the
deep
Dives
is:
how
does
figma
use
stuff
and
kind
of
half
learning
how
to
use
figma
again,
yeah
and
then
the
big,
oh
sorry,
and
then
there's
there's
composite.
We
discusses
at
the
top
of
this
is
called
composite
values
and
how
those
might
be
translated
or
whatever
a
lot
of
those
to
be
honest,
can
be
flattened
and
made
complex
when
they
need
to
be
made
complex.
A
But
then
there
is,
you
know,
and
this
is
not
necessarily
A
blocker
to
any
initial
work
or
initial
iterations.
This
is
more
of
a
being
mindful
of
to
make
some
decisions
at
some
time.
A
What
happens
when
you
have
you
know
a
case
like
you
know,
color
success,
muted
foreground,
you
know,
is
it
button?
Color
confirm
background
hover.
A
You
know
what
what
order
do
those
things
go
into?
Ultimate,
ultimately,
we're
not
going
to
consume
those.
You
know
immediately.
That
would
need
be
factoring
in
figma
and
then
gitlab,
UI
and
I
feel
like
those
are
decisions
that
might
be
influenced
by
what
what
figma
chooses
to
do
with
Native.
B
A
If
they
bring
in
something
like
from
what
I've
seen
like
atlassian
and
others
have
used,
where
they
have
named
tokens
for
each
kind
of
usage,
they've
developed
their
own
figma,
plugin
I
haven't
been
able
to
access
it,
but
yeah
that
might
be.
That
might
be
a
you.
B
A
B
That
conference
I
confirm
it's:
it's
June
like
21st
and
22nd.
So
it's
it's
towards
the
end
of
the
month.
Right.
A
Oh
cool,
yeah
and
and
I
should
clarify
that
the
First
Slice
of
any
of
this
work
would
most
likely
be
color
and
most
likely
just
be
the
initial
color
palettes.
So
maybe
not
yeah.
B
A
A
data
visualization
or
the
theming,
although
structurally
they're,
real.
A
Well,
ideally,
light
and
dark,
and
that
goes
into
modes.
A
And
how
we
do
modes
is
how
I'm
currently
doing
it
so
in
if
I
show
you
here,
you
can
toggle
between
my
dark
mode.
It
doesn't
do
the
background
or
anything
cool
like
that
at
the
moment,
but
a
hot
spots,
the
values
up,
so
you
can
def,
you
can
Define
tokens
and
you'll
have
like
a.
A
Base
set
of
all
the
tokens,
what
I
might
show
you
here
to
get
an
actually
contextual
sense,
is
here's
what
I
prepared
earlier
slash
I'm
halfway
through
editing,
so
it's
probably
a
bit
messy.
A
You
know
everything
in
the
kitchen
sink.
These
are
all
the
tokens
style
dictionary
translates
them
to
SAS
variables,
some
currently
outputting.
You
know
JavaScript
Json,
CSS
and
SAS,
but
this
gives
you
an
idea
of
the
ones
that
have
natural
values
are
the
ones
that
then
are
aliased
to
a
values.
So
if
we
go
to
again
three
and
800
answers
to
that,
this
namespace
and
context
or
grouping
is
an
opinionated
decision
that
I've
made
during
the
process
of
this
POC.
All
this
is
up
for
a
debate.
A
You
could
also
have
this
be
the
best
token
as
well.
Okay,
but
what
I
want
to
show
you
here
is,
you
would
have
so
this
generates
out
all
the
things
and
then
we
have
so
colors.
We
have
the
base,
so
we
Define
all
the
colors,
and
we
also
have
base
dark
where
we
redefine
them
for
dark
mode
and
what
that
gives
us
in
the
dark
output.
Is
it
doesn't
give
us
everything
in
the
kitchen
sink
plus
dark?
A
The
other
SAS
file,
which
shows
inheritance,
we're
only
hot
swapping
out
the
values
so
yeah
the
hex
values,
and
in
this
case
we
change
black,
normal
and
white
to
different
shapes.
B
A
A
Yeah,
so
that
that
the
next
thing
is
like
how
we
actually
do
dark
mode
in
gitlab,
I
think
we
are
doing
CSS
files
and
the
default
value
is
the
SAS
variable
and
all
those
then
get
overwritten
in
the
dark
style
sheet.
A
A
Okay,
so
the
thinnest
slice,
the
thinnest
of
the
thinner
slices
to
me,
would
be
removing
these
definitions
from
you
know:
design.itlab.com
GitHub,
UI,
gitlab.com,
all
the
different
consumers
and
you
would
import
like
this
kind
of
colors
success
or
something
from
from
a
token's
output.
B
A
But
what
that
conceptually,
you
know
the
initial
dark
mode,
I
think
we've
spoken
about
this
before
or
you've
documented
about
different
modes,
that
sort
of
thing
conceptually
dark
mode.
You
know
swapping
out
the
colors
and
having
different
a
different
Cascade
of
colors.
That
would
be
inherited
later
that
that
could
also
be
applied
to
something
like
this
is
a
concept
I'm
playing
with
not
prescriptive
to
any
actual
outcome.
B
A
Yep,
so
you
could
also
have
them
any
other
mode
say
like
high
contrast
mode.
A
We
might
have
different
modes
for
different
color
blindness,
one,
the
one
that
is
you
know
more
of
an
opinionated
decision
would
be
something
like
you
could
have
Focus
mode
or
something
where
you
would
remove
borders
from
buttons
and
inputs,
or
something
so
that
everything
is
just
kind
of
kind
of
like
a
reader
mode
or
something
yeah.
A
B
A
And
we
strip
out
all
the
kind
of
UI
flourishes
like
background
and
borders
and
all
those
sort
of
things.
That
is
where
you
may
need
something
like
a
like,
an
actual
tangible
design.
Token
for
a
component
where
you
may
have
like
you
know,
button
default
border.
Is
this
and
focus
mode?
We
go?
No,
it's
not
it's.
You
know.
A
B
And,
and
from
just
from
my
education
at
what
point,
would
you
use
CSS
variables
versus
loading
in
a
separate
like
CSS
file
that
was
generated
based
on
these
variables?.
A
So
a
really
good
question,
because,
ultimately
that's
that's
two,
the
consumer
right
so
like
what
what
does
the
application
currently
use
and
how
does
it
Define
things?
I,
don't
have
enough
experience
with
large-scale
CSS
fast
enough.
There's
any
kind
of
you
know
noticeable
performance
or
whatever
impact
from
say.
Having
you
know
say
that
this
was
to
the
order
of
tenfold,
so
you
have
like
three
thousand
variables
at
the
root
level.
All
reference
to
each
other,
I,
don't
know.
A
I
would
think
we
would
possibly
lean
towards
outputting,
CSS,
custom
properties
from
design
tokens
and
consuming
those,
and
if
we
were
to
consume
SAS
variables,
it
would
be
wrapping
a
custom
property
so
that
all
the
values
would
happen
in
the
browser
at
runtime
and
we
can
sort
those
out
versus
I
believe
currently
dark
mode
is
a
separate
style
sheet.
It's
a
different
yeah
compiled
professional,
fit
the
reason.
A
I'm
thinking
that
and
it's
very
bliased
as
of
today
when
I've
been
playing
around
with
this
compact
mode,
which
I
haven't
got
the
demo
for
yet
is
you
can
have
compact
mode
with
dark
mode.
A
You
could
have
dark
mode
reader
mode.
These
modalities
could
be
combined
yeah.
So
you
don't
have
this
like
entire
compilation,
step,
here's
it
it's
parts
and
in
between
parts
that
would
get
updated.
B
Yeah
well
and
I
was
thinking
too
even
with
when
you
talk
about
system
or
browser
preferences,
like
you
know,
prefers
whatever
you
you'd
be
able
to
just
swap
the
tokens
based
on
that
or
not
the
tokens
that
swap
the
CSS
variables
based
on
that,
where,
instead
of
detecting
and
then
swapping
a
JavaScript
file,
you
you're
using
media
queries
or
or
you
know
what
not
to
to
just
pull
in
and
and
do
that
same
with,
like
responsive
and
yeah.
A
Yeah
so
especially
for
things
like
reduce
motion
and
those
sort
of
things
and
I
think
you
can
even
set
browser
config
for
like
prefers
high
contrast
or
something
now,
so
any
of
those
kind
of
user
preferences
could
be
an
inherited
and
the
me,
the
media
query
itself
would
update
the
values
and
not
necessarily
like
a
direct
intervention
like
a
user
preference
or
a
new.
B
Right
and
then
not
to
get
too
crazy,
but
even
if,
if
a
user
at
some
point
was
able
to
customize
their
own
theme
or
overrides
for,
let's
just
say
the
the
web
IDE
or
inline
code,
it
would
simply
just
be
updating
that
CSS
variable,
rather
than
relying
on
another
CSS
file,
and
so,
like
you
said,
you'd,
be
able
to
combine
these
things
and
not
have
that.
So,
okay.
A
Yes
and
that's
where
that's
where
probably-
and
this
is
actually
kind
of
from
the
distinction
I'm
making-
and
this
is
common
throughout
a
bunch
of
different
sort
of
design-
token
implementations
is
the
idea
of
the
separation
between
what
is
like
a
base
token
and
what
is
like
a
design
token
painting
a
better
name
but
a
base.
Token
being
something
like.
We
have
currently
SAS
variables.
A
We
have
the
the
Styles
in
figma.
Of
course,
it's
something
that
has
like
a
semantic
meaning
at
the
moment.
I'm
using
you
know,
color
info
or
color.
B
A
A
So
the
the
idea
of
you
know
well
under
the
umbrella
of
design.
Tokens
is
all
of
the
component
tokens
and
the
the
semantic
design
tokens
how
we
might
consume
those
and
how
we
might
use
those
I
think
is
a
larger
undertaking
because
it
means
updating,
figma,
gitlab
UI.
You
know
a
lot
of
things,
but
it's
worth
planting
that
seat,
to
figure
out
what
that
may
look
like
from
a
structure
so
that
those
things
can
be
automatically
passed
over.
A
We
can
do
Collision
detection,
which
is
the
I,
think
the
big
thing.
What
sets
what
variable?
Where?
How
does
it
inherit
it?
And
then
you
know
how
does
it
get
spun
out?
That's
the
benefit
of
style,
dictionary.
I
think
that's
probably
its
best
feature,
yes,
and
then
that
would
also
give
you
opportunity
for
something
like
you
shared
in
the
design
system,
Channel
an
ability
to
search
other
things.
I
want
a
border
for.
B
A
A
The
big
thing
that
I'm
sort
of
one
of
my
approaches,
I'm
taking
for
the
perfect
concept,
would
be
having
aliases
or
compatibility
to
map
what
might
be
a
semantic
term.
So
we're
going
to
use
like
GL,
color,
gray,
500
that
may
also
be
just
gray
500.
It
could
be
neutral
500.
It
could
be
whatever
we
can
map
those
to
the
existing
variable
usage
in
GitHub,
UI,
gitlab.com
or
consumers,
so
that
we
don't
have
to
update
the
Myriad
of
different.
You
know
variable
usage.
A
This
also
could
back
on
what
the
work
that
Mark
has
been
doing
with
Combi,
which
is
a
you
know,
I,
can
automatic
sort
of
what
I
call
it
like
a
code.
Mod
tool
which
goes
through
I
can
update
a
whole
bunch
of
things
at
the
same
time,
but
as
a
you
know,
Safeguard
a
compatibility
mode,
I'm
thinking.
We
could
have
these
future
proof.
This
is
the
structure
naming.
This
is
what
we
want
them
to
be,
but
a
list
to
current
usage.
All
these
should
be
deprecated.
B
A
B
Oh,
and
what
we've
been
doing
is
a
we're
our
release,
Cadence
with
the
UI
kit
and
with
that
file
in
particular,
is
just
at
the
end
of
every
Milestone
and
we're
doing
release,
notes
that
are
in
pajamas
that
highlight
anything.
So
if
we
change
anything
with
Styles,
you
would
you
would
know
about
it
at
that
point.
So
I
say
that
just
to
Just
note
that
you
you,
you
won't
be
out
of
date,
at
least
for
the
next
like
three
weeks
right
and
then
then
you
would
know
like.
Oh
these
Styles
updated
okay.
B
A
A
That
gives
me
an
opportunity
to
basically
like
what
you
what
you
step
through
all
the
different
styles,
how
to
use
I
want
to
see
how
they
are
consumed
or
shared
from
figma.
A
B
And
see
yeah
I
know
it
seems
kind
of
odd
to
wait
for
that.
But
I
I
know
timing,
wise
I
think
that
that's
a
it's
an
appropriate
buffer
and
then
it
then
we
don't
jump
the
gun
on.
A
B
Would
hate
to
be
like
yeah
we're
gonna
run
with
this
plug-in
and
then
we
spend
a
month
implementing
it
and
then
it's
like?
Oh,
this
is
native
now
and
like
we've
gone
through
pure
procurement
or
whatever
you
know,
it'd
be
great
to
have
that
thought.
So
I
think
that
would
be
good
cool,
well,
I'm,
gonna,
I'm,
gonna,
I
hate
to
run,
but
I'm
gonna
run
yeah.
A
B
But
I
will
maybe
record
a
video
for
you
regarding
the
type
stuff
that
we're
working
on,
because
right
now
the
way
the
SAS
works
there
is
it
spits
out
the
the
CSS
variables
that
are
then
consumed
by
the
elements,
and,
and
so
it
seems
that
it
would
be
kind
of
doubling
up
the
work
of
what
tokens
would
be
doing
where
we
would.
B
We
would
want
to
essentially
reverse
engineer
it,
and
so
you
know
there's
some
clever
things
happening
in
the
SAS
and
whatnot,
but
I
think
that
we
could
flatten
that
quite
a
bit
and
and
just
rely
on
tokens
in
that
way.
B
So
anyway,
I'll
record
a
video
on
that
and
ask
some
questions
because
there's
some
stuff
I
just
I'm
just
curious
about-
and
we
can
work
that
way
through
that
so
I'm
not
I'll,
try
to
get
to
that
tomorrow,
we'll
see
otherwise.
Next
week,
I'll
I'll
put
that
together.
So.
A
So
it's
good
because
that's
the
main
you'll
notice,
the
main
missing
part
is
the
is
the
top
scales.
I
haven't
haven't
gone
into
any
of
that
yeah.
B
B
I'm
gonna
post
this
in
unfiltered
and
under
just
private
and
I'll
I'll,
make
sure
you
have
a
link
and
then
has
a
link
to
it
and
and
go
from
there,
but
this
is
awesome.
I'm
excited
about
it.
Thanks
for
all
your
work
on
this.