►
From YouTube: UX Showcase: Color, Figma, and FE/UX Foundations updates
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
A
Again,
give
me
a
thumbs
up
if
you
can
see
the
screen
excellent,
well,
good,
to
see
everyone
welcome
to
a
new
month.
What
a
long
year
March
was.
I
am
Jeremy
eller
senior
product
designer
for
our
front-end
and
UX
foundations,
and
that's
a
new
team.
I
will
go
into
that
a
little
bit
at
the
end
of
this
week
over
here.
B
A
So
there's
three
things:
I
was
going
to
kind
of
address
today:
color
figma
and
foundations,
so
three
kind
of
massive
things
that
are
happening
and
hopefully
we'll
be
able
to
kind
of
break
that
down
pretty
concisely.
I
will,
let's
start
with
talking
about
color
a
lot
a
lot
going
on
with
color,
so
a
little
backstory.
This
is
this.
A
So
let's
go
into
business
school
because
there
is
a
huge
one
tie
to
this
for
one
accessible
UI
and
the
second
part
of
that
is
to
have
work.
Ag,
2.1,
double-a
compliance.
This
is
massive
because
this
this
goes
into
our
V
Pat,
which
is
our
voluntary
product,
accessibility,
template
and
many
like
government
educational
users
will
actually
require
a
V
Pat
with
mechag
2.1
double-a
compliance
in
order
to
use
the
product
so
current
state.
A
Today,
color
is
listed
as
as
not
supported
for
contrast
and
being
able
to
adjust
color
and
do
that
allows
us
to
have
compliance
in
there,
which
gets
our
v
pack
closer
to
100%
passing
grade,
which
makes
it
easier
for
government
and
other
organizations
to
actually
use
the
product
and
be
able
to
sign
off
on
it.
So
it's
it
does
have
a
positive
business
goal
attached
to
it.
A
Yes,
Styles
scss
they
sometimes
override
variables
and
get
lab
UI,
but
not
always
so
it's
very
tricky
to
identify.
When
you
make
changes,
what
is
going
to
be
changed
and
what
isn't
another
one
is
that
orange
and
green
hues,
which
we
use
extensively
for
status
and
meaning
and
actions
they're
they're,
very
notorious
and
difficult
to
maintain,
like
a
vivid
quality
with
the
color,
while
meeting
contrast
ratios,
so
you
know
what
we
on
one
hand
we
increase
the
contrast
ratios
to
satisfy
the
CAG.
A
The
other
side
of
things
is
that
when
you
increase
that
contrast,
those
hues
tend
to
get
darker,
which
makes
it
actually
tougher
for
users
with
with
red-green
color
blindness
to
distinguish
those,
and
so
you
know,
there's
there's
impacts
there
and
kind
of
anecdotally.
You
know,
I've
talked
to
others
in
the
accessibility
community
and
they're
like
you,
either
use
a
really
large
font
or
you
don't
use
these
colors.
So
we
have
some
good
problems
to
solve
from
here
on
out
and
that's
gonna
be
one
of
our
our
next
steps.
A
Number
four
is
testing
a
work
in
progress
to
merge
request
from
get
you
hit.
Love
you
I
in
the
GDK
is
not
really
easy,
so
it
makes
it
more
difficult
to
assess
impact.
We
can
test
it
kind
of
in
the
confines
of
get
lab
UI,
but
then
understanding
the
upstream
impact
of
the
product
can
be
difficult
and
there's
an
issue
linked
there.
As
far
as,
however,
how
we're
going
to
go
about
rectifying
that
5
is
just
evaluating
contrast
ratios
for
each
color
step
against
multiple
surfaces.
A
When
I
say
surface
I
mean,
like
the
background
colors,
that
we
use
in
the
UI
and
then
on
top
of
that
is
normalizing
those
same
steps
across
hues
and
I'll
discuss
what
that
looks
like
so.
First,
here's
kind
of
what
it
looks
like
to
to
take
a
look
at
all
the
contrast
values
against
the
surfaces
so
for
each
step
in
a
hue
we,
you
know
we
have
to
evaluate
the
contrast
level
and
make
sure
it
passes
in
those
different
circumstances,
and
in
that
way
we
can
create
normalized
rules
of
you
know.
A
You
can
always
use
a
500
value
against
50
value
and
meet
contrast
regardless
of
hue,
so
the
ability
to
be
able
to
do
that
is
very
helpful.
Here's
an
example
of
what
it
looks
like
to
normalize
right,
so
we
take
a
grayscale
view
and
we
see.
Okay,
are
these
steps?
Are
they
is
the
gradation
equal
across
hues?
There's
slight
variance,
but
we
want
to
get
as
close
to
that
gradation
as
possible
and
then
the
last
constraint
is
preference.
A
Color
is
subjective
and
it's
one
area
where
we're
in
a
product.
You
experience
the
subjectivity
meeting
the
objective
rules
of
actually
needing
to
pass
and
have
contrast.
So
it's
preferences
is
something
that
we,
we
really
you
know,
experienced
a
lot
of
collisions
with,
and
that
leads
to
to
this
right,
where
it's
just
you
kind
of
peek
over
the
edge.
And
it's
like.
Let's
that's
that's
a
lot,
but
that's
okay.
A
It's
a
good
problem
to
solve
so
out
of
all
that
that
led
to
a
lot
of
exploration
and
building
out
different
issues
to
track
things
anyway,
anywhere
from
adding
purple
to
our
primary
UI
palette,
so
that
we
had
an
additional
color
to
pull
out
some
different
meaning
that
we
might
not
have
today
to
working
on
a
palette
specifically
for
data
visualization
to
working
on.
You
know
actually
working
through
our
existing
palette
and
determining
meaning
all
the
way
to
normalizing
our
grays
and
considering
surfaces,
planning
for
dark
mode,
dark
theme,
etc.
A
Here's
what
it
looks
like
you
know
as
I
started
to
assimilate
that
and
work
through
kind
of
before
and
after
and
and
look
at
the
trends.
Look
at
the
change
to
see
how
colors
are
moving,
and
so
we
get
to
today's
state,
which
is
implementation
in
figma,
where
we
actually
have
a
full
document
where
you
can
see
the
colors.
The
contrast
ratios
makes
it
pretty
easy
and
one
little
I'll
just
jump
over
here,
really
quick
to
color.
A
One
of
the
things
that
we're
able
to
do
in
figma
is
is
actually
have
you
know
the
terminal
layers
back
on
here:
the
ability
to
kind
of
toggle
the
ratios
really
easily
for
all
of
our
all
of
our
hues,
and
that
makes
it
just
kind
of
a
nice
little
tool
within
that.
So
a
little
side
note
get
back
over
here
and
then
we
also
have
a
new
data
of
his
palette,
and
this
is
also
documented
in
figma.
A
A
This
week
is
leveraging
default
in
git
lab
you,
a
UI
for
our
CSS
overrides,
which
means
that
get
lab
UI
will
prescribe
default,
color
valuables
very
variable,
sorry,
but
then
the
product
will
be
able
to
overwrite
those
variables,
and
so
many
of
the
changes
that
we're
seeing
today
that
have
been
problematic
with
orange.
Looking
more
brown
well
should
be
reverted,
and
so
we
can
address
things
on
a
case-by-case
basis.
A
So
next
steps
going
to
remap
color
variables
in
the
actual
gitlab
s
CSS
to
make
sure
that
they
align
with
the
new
properties
evaluate
variables
instance,
my
instance
component
by
component.
I
explore
other
areas
where
we
could
use
color
in
better
ways,
hopefully
work
towards
updating
the
vpad
to
show
support
status.
For
contrast,
I
want
to
be
able
to
address
all
the
issues
in
the
accessibility,
color
palette
and
use
epics
so
that
we
can
close
those
out
and
keep
moving
forward,
eventually
communicate
all
changes
in
a
longer
larger
blog
post
and
then
continue
to
iterate.
A
So
a
lot
happening
there.
That's
the
end
of
the
color
section
see
here.
It
looks
like
we're
good
on
time.
I
will
save
any
time
for
questions
at
the
end
and
I'll
start
talking
about
figma,
alright.
So
for
those
of
you
that
don't
know
where
we're
migrating
from
sketch
to
figma
for
a
primary
design
tool
and
there's
many
reasons
for
this,
but
here's
some
of
the
top
ones-
we
really
want
to
choose
a
tool
that
aligns
with
everyone
can
contribute
right
now.
A
Sketch
is
mac
OS
only
it
is
virtually
desktop
only
where
figma
is
something
that
is
kind
of
more
platform
agnostic.
It's
browser,
it's
desktop,
and
so
it's
a
little
more
open
and
we'll
see
some
I
guess
some
of
the
benefits
of
that
with
community
contributions
and
even
our
own
workflow.
Just
the
next
point.
We
will
be
able
to
streamline
the
design
workflow
so
rather
than
checking
out
a
branch.
A
Creating
you
know,
do
duplicates
in
sketch
pushing
that
up,
you'll
be
able
to
essentially
make
a
a
change
in
figma,
publish
a
draft
share
it
and
be
done
so
a
lot
of
that
back-end
workflow
will
be
eliminated,
we'll
be
able
to
provide
more
visibility
to
in-progress
work.
So
just
by
nature,
when
we
have
public
projects
or
team
projects
in
figma
you
as
a
as
another
designer
will
be
able
to
go
in
or
PM
or
anybody
will
be
able
to
go
in
and
view
those
those
design
files.
A
You
know
kind
of
in-flight
if
possible,
and
what
that
does
is
allow
you
to
see
the
changes
real
time
to
experience.
What's
going
on
and
to
be
able
to
async.
You
know
pop
in
and
see
what
what's
happening,
rather
than
look
for
a
post
or
or
something
being
pushed
to
the
current
repo
second-to-last
we'll
be
able
to
simplify
ASIC
and
sync
work
by
working
in
one
file,
leaving
leaving
real-time.
You
know
commenting
actually
that's
design,
like
contextual
to
the
design,
so
right
now
leaving
comments
in
an
issue
for
a
designer
is
sometimes
problematic.
A
Just
because
those
comments
tend
to
be.
You
know
separate
from
the
actual
design,
so
you
have
to
kind
of
mentally
map.
This
comment
relates
to
this
part
of
the
design
with
figma
will
be
able
to
have
that
that
pinpoint
accuracy
of
what
a
comment
applies
to
and
then
sync
work
since
there's
kind
of
a
collaborative
mode
in
there,
where
everybody
can
actually
work
in
their
together
real
time,
and
you
can
see
what
others
are
doing,
it's
very
helpful
and
then
the
last
item
in
purpose
is
just
to
be
able
to
promote
open
source
design.
A
A
There's
21
of
the
37
components
that
we've
identified
are
complete
and
there's
several
more
that
are
in
a
state
of
review
that
should
be
done
in
this
milestone.
We
have
over
seven
team
members
that
are
working
towards
component
and
other
design
parity
with
what
exists
in
in
Sketch
today,
and
then
we
have
user
licenses
which
are
being
worked
on
in
procurement.
A
We've
got
new
issue
templates
interview,
so
if
you're
wanting
to
create
a
new
icon,
a
new
illustration,
etc,
it's
it's
gonna
be
relevant
to
figma
and
that
workflow
we
do
have
contributing
documentation
linked
there
for
team
members
in
the
greater
community
design
specs
are
starting
to
link
to
completed
figma
designs
and
we
have
a
figma
slash
channel.
So
a
lot
of
things
happening
around
the
the
figma
ecosystem.
A
Here's
an
example
of
the
figma
board,
where
we're
actually
tracking
some
of
our
issues
and
milestone
you
can
you
can
link
to
that
in
the
top
right
corner?
Here's
what
our
public
profile
looks
like,
so
I
mentioned
that
the
community
aspect
of
it
we're
part
of
the
community
beta
where
get
lab
actually
has
our
own
profile
in
the
figma
platform,
where
others
can
actually
search
for
our
resources
or,
if
they're
searching
for
UIKit
other
things
that
I've
tagged,
they
could
come
across
our
designs
and
learn
from
it.
They
can
use
it.
A
A
So
some
of
the
challenges
that
we've
had
as
we've
migrated
from
sketch
to
figma
is
just
first
determining
single
source
of
truth.
It's
it's
very
difficult.
Sometimes
to
determine
is
sketch.
The
latest
is
the
product,
the
latest,
and
so
it's
taking
a
little
more
a
little
more
friction
to
to
kind
of
create
parity
with.
A
Timing
and
scheduling
just
for
creating
and
reviewing
since
everybody
is
part
of
stage
work
and
working
on
their
own
projects
being
able
to
devote
time
to
this
while
learning
a
new
tool
and
a
new
workflow
is
a
challenge
and
then
lastly
just
feature
parity
within
a
learning
curve
from
sketch
to
figma
identifying
you
know:
do
we
need
plugins?
How
do
you
you
know?
What
are
the
terminology?
There's
there's
just
a
lot
around
that
that
we've
worked
through
those
challenges.
A
Next
steps
we're
going
to
attain
full
parity
with
what
exists
in
sketch
today
update,
get
lab
design,
pyjamas
handbook,
Doc's,
complete
the
issue.
Templates,
dress,
workflows,
we'll
set
up
office
hours.
Well,
we'll
have
two
time
zones
that
so
that
people
can
pop
in
and
we
can
work
through
that
and
then
get
the
licenses
purchased
for
the
team
so
that
we
can
work
through
that
get
other
designers
acclimated
to
the
product.
A
A
Alright,
so
foundations
is
a
new
category
and
a
new
team
and
Tory
feel
free
or
Jarek
feel
free
to
jump
in
and
kind
of
add
any
color
to
this.
But
if
you
were
to
look
at
where
we
are
we're
a
category
front,
energy
looks
foundation
that
reports
up
through
the
ecosystem
group
and
another
way
to
put
that,
is
that
it's
under
the
create
stage
under
the
development
product
section
so
I'll
leave
that
there
and
the
slides
won't
unpack.
Any
of
that.
A
But
that's
that's
just
an
idea
of
where
kind
of
we
fit
in
the
scheme
of
things.
I
didn't
put
this
in
the
slides,
but
Tory
Jarek
and
myself
are
the
designers
managers
that
are
going
to
be
working
on
this
team
Tory
will
be
managing
and
it's
it's
exciting.
So
we
we
actually
just
had
our
first
team
meeting
last
week
to
start
to
lay
out
where
we
want
to
take
the
team,
what
we
want
to
do
with
it.
Here's
kind
of
a
little
capture
of
some
of
our
documents
as
we
worked
through
the
meeting.
A
Some
of
the
things
that
each
of
us
want
to
do
to
see
happen
as
part
of
the
team
and,
ultimately,
just
to
summarize
it
the
the
front
end.
A
UX
foundations
team
is
going
to
be
responsible
for
leading
the
direction
of
the
experience,
design,
visual
design
and
technical
tooling
of
the
gitlab
product.
And
it's
important
to
note
that
it's
going
to
focus
on
two
things.
It's
focused
on
tooling
and
user
focused
enhancements,
and
this
is
probably
the
most
critical
piece
right
is
that
front-end
and
UX,
although
will
act
as
kind
of
a
centralized
resource.
A
The
arrows
point
both
ways
right.
So
this
is
not
a
dictatorship.
It's
not
a
top-down
type
of
a
of
a
workflow
right,
we're
here
to
work
across
all
teams
and
all
groups
and
to
contribute
to
the
design
system
and
then
also
to
help
triage
large
scale
like
technical
and
experienced
problems.
So
it's
it's
very
much
a
collaborative
approach
so
that
it's
its
inputs,
outputs
and
not
just
one
team
making
decisions
so
want
to
really
emphasize
that
that
this
is
a
collaborative
effort.
A
Everybody
is
still,
you
know,
encouraged
to
contribute
to
the
designing
system,
to
be
designing
your
components
to
be.
You
know,
kind
of
pushing
the
envelope
on
on
the
design
of
the
product
and
thinking
through
that
in
a
design
and
systems
mindset.
So
what
are
we
doing?
Initially,
we're
really
focused
on
shepherding
the
create,
build
and
style
faces
of
the
36
foundational
components.
There's
a
link
to
what
those
are.
There
is
actually
four
phases
of
the
the
implementation
of
a
component,
we're
focused
on
the
first
three
and
then
also
shepherding
the
migration
from
sketch
to
figma.
A
What
we're
not
doing
is
building
and
integrating
all
components
across
gate
labs.
So
that's
kind
of
that
fourth
step
of
a
component
is
actual
build
an
integration
and-
and
we
won't
be
doing
that-
it's
fully
expected
that
teams
and
and
other
designers
engineers
will
be
helping
to
implement
and
get
those
integrated
simply
because
there's
there's
so
many
ways
and
places
to
get
those
components
added
to
the
product.
It
would
not
be
possible
for
for
this
team
alone
to
do
that,
so
that
leads
us
to
what
you
know
we're
looking
at
kind
of
long
term.
A
First,
to
be
creating
a
comprehensive
action
plan
for
integrating
components
into
the
product,
so
that
we
can
kind
of
help
foster
that
process
and
help
Shepherd
that
process
auditing
and
updating
our
existing
V
Pat.
That
I
mentioned
earlier
in
color,
so
that
we
can
look
through
and
see
what
areas
do
we
really
need
to
focus
on
for
accessibility
in
the
product
which
leads.
The
next
point
is
building
comprehensive
accessibility
standards
into
our
workflows.
A
So
we
really
want
to
make
sure
that
those
workflow
standards
are
in
place
at
the
start,
so
that
they're
not
an
afterthought
and
it
doesn't
provide
any
extra
friction
at
the
back
end
or
hold
up
anything
getting
released
because
we've
already
thought
about
it
and
then
something
for
later
is
building
out
a
dark
theme
or
dark
UI.
That's
that's
something
that
has
been
out
there
for
a
long
time
and
there's
a
lot
of
emphasis
around
it.
A
B
That's
beautifully
done.
Thank
you
so
much
curious
Jeremy.
How
much
collaboration
have
you
had
with
brand
and
marketing
or
other
designers
in
the
organization.
A
That's
a
great
question:
when
I
first
started
one
of
the
individuals
that
I
first
connected
with
was
Luke
Babb,
who
is
on
the
marketing
team
and
I've,
been
working
with
Vicki
Bell,
who
does
illustration
and
then
our
our
own
Shayne,
who
moved
order
that
team
as
well
so
quite
a
bit
of
collaboration
with
the
brand
team
and
any
time
something
comes
up.
That
is
it's
part
of
that
visual
aspect
or
where
they
want
to
take
things.
We're
definitely
looping
them
in
good
question.