►
Description
Shopify’s admin product component library helps them work together to build a great experience for all of their merchants.
https://github.com/Shopify/polaris-react
0:00 - Start
0:23 - What is Polaris?
5:40 - Who is Polaris made for?
7:50 - How is the project maintained inside Shopify?
11:45 - Design system component challenges
15:53 - Maintaining multiple design systems
21:54 - Interesting Design UI trends
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
Today,
our
design
systems
help
build
great
experiences
for
our
customers,
and
this
is
a
recording
from
open
source
friday,
where
I
sit
down
and
talk
to
alex
page
about
their
design
system
from
shopify
and
how
they're
supporting
over
a
million
businesses
in
their
admin
dashboard.
Now,
if
you're
interested
in
learning
about
the
latest
and
greatest
of
design
systems
you're
in
the
right
place,
so
let's
go
and
jump
right
in
so
why
don't
we
you
give
us
like
a
quick
introduction
of
what
polar
polaris
is
and
what
you're
trying
to
do.
B
Yeah,
so
polaris
is
shopify's
design
system,
it's
built
for
our
admin
products,
so
we'll
get
into
that
a
bit
later
on,
but
like
our
admin
is
where
our
merchants
go
to
manage
their
stores.
So
if
you
go
to
shopify.com
and
you
create
an
account
or
if
you
log
in
and
you're
you
know,
selling
t-shirts
or
you're
selling
whatever
product
it
is.
You
need
this
like
admin
interface,
so
admin
interface
has
lots
of
lists.
It's
like
show
me.
B
A
list
of
all
the
orders
that
have
came
in
today
show
me
a
list
of
all
the
products.
I
maintain
show
me
a
list
of
all
the
customers
that
have
bought
things
from
me.
So
polaris
really
is
like
a
tool
for
like
building
these
reusable
pieces
across
this
admin
experience
and
and
when
you
like,
then
click
on
one
of
these
list
items
you
get
lots
of
forms,
so
polaris
is
very
form
heavy.
It's
very
list
heavy.
It's
really
about
trying
to
create
a
consistent
experience
for
our
users.
B
So
when
someone
goes
to
a
list
of
customers,
we
would
hope
that
it
works
very
similar
to
a
list
of
orders,
because
you
know
they're
starting
to
learn
these
different
patterns
and
experiences.
But
we
are
also
like
noticing
other
problems
with
this
conformity.
So
I
want
to
touch
on
that
a
little
bit
too,
like
as
we
build
a
design
system.
We
hope
that
we
consolidate
designs
and
we
sort
of
create
consistent
experiences,
but
in
doing
that,
we
also
sometimes
sacrifice
the
quality
of
design.
B
We
want
you
to
like
challenge
that
understand
why
that
button
is
built
that
way
and
create
the
best
button
for
your
user
at
that
point
of
time.
So
it's
a
it's
really
interesting
space
in
terms
of
like
us
trying
to
create
this,
you
know
trying
to
create
this
cohesion,
but
also
trying
to
enable
creativity
and
push
the
experiences
forward
across
you
know
across
our
company.
A
B
That's
definitely
controversial
like
in
time
inside
our
company,
because
we
we
definitely
don't
see
polaris
as
the
true
north
and,
if,
like
a
lot
of
people,
understand
paris,
as
you
know
the
north
star,
and
it
tells
you
where
to
go,
and
I
think
that
could
have
been
the
intention
in
the
past.
I
think
a
reframe
on
that
would
be
like.
I
know
where
north
is
and
I'm
going
to
use
that
direction
to
like
go
south.
I'm
going
to
use
that
direction
to
go
east
and
I
think,
like
yeah.
B
We
would
much
rather
that
kind
of
thinking
where
it's
like.
I
I
understand
why
these
design
decisions
were
made,
but
I
also
want
to
break
them,
and
I
don't
want
to
go
true
north,
because
if
I
go
true
north,
then
I'm
going
to
give
the
user
the
most.
I
don't
know
we
want
people
to
give
the
user
the
best
experience
they
can
and
if
you
go
that
true,
north
you're,
just
you're,
usually
sacrificing
creating
trade-offs.
That
yeah
don't
lead.
A
B
Yeah
totally,
I
think,
like
what
am
I
trying
like.
I
think
if
I
look
at
the
lists
in
shopify
like
I
think,
resource
list
is
a
really
good
example
like
this
shows
up
everywhere
in
our
interface
and
even
like
radio
buttons
and
like
like
all
the
time,
and
I
think
I
even
like
challenge
that
to
be
like
this
pattern
exists,
but
just
because
there
is
a
radio
button
pattern
or
there
is
a
resource
list.
Pattern
doesn't
mean.
That
is
the
default
that
you
should
use
like.
B
Maybe
changing
that
or
building
something
new
or
expanding
on.
That
would
actually
give
your
users
a
much
better
experience.
So
that
comes
with
a
lot
of
problems,
though,
because
the
system
we've
created
is,
as
of
today
very
strict
and
very
focused
on
like
this
one
design
and
this
one
approach,
and
if
you
wanted
to
have
a
different
experience,
if
you
wanted
to
build
something
different,
you
get
yourself
into
a
very
tricky
place,
you're,
either
forking
things
and
then
you're
like
off
the
maintenance
path.
You
have
to
maintain
it
yourself.
B
You
have
to
write
your
own
tests
or
you
are
maybe
using
the
thing
as
is,
and
you're
just
hacking
things
in
there
and
that
also
like
doesn't
become
the
best
for
maintenance,
like
maybe
do
a
breaking
change,
and
now
that
breaking
change
is
a
lot
harder
for
your
team.
So
we're
trying
to
find
a
way
to
almost
describe
it
as
like.
Breaking
down
some
of
these
components
into
a
lot
smaller
pieces
and
giving
teams
the
ability
to
like
build,
build
above
or
like
build
on
top
of
these
pieces
that
we're
creating
so
yeah.
A
Cool
and
this
so
this
is
a
an
open
source
project,
which
is
why
you're
here
in
open
source
friday,
yeah
part
of
the
reason
why
I
reached
out-
and
I
just
realized-
I
haven't-
started
the
project.
So
there
you
go
giving
you
one
more
star,
and
so
I'm
curious
because
you
work
at
shopify
you're,
a
shopify
employee.
You
work
on
this
design
system
team.
How
do
you
approach
suggestions
or
contributions
or
a
better
better
question,
probably
is:
do
you
find
other
people
outside
of
shopify
using
this.
B
A
B
B
Yeah,
that's
a
really
good
question,
so
a
lot
of
our
planning
actually
happens
sort
of
internally
with
our
internal
teams.
So
there
was
a
point
in
time
where
we,
I
think
I
even
created
a
repository.
It's
called
like
github
project,
automation
plus,
and
I
pretty
much
just
made
it
so
every
single
issue
and
every
single
pull
request
that
came
into
this
repo
went
into
like
a
backlog
in
github
projects.
Yeah.
A
B
Then
we
could
like
drag
things
into
your
progress,
but
it
just
it
wasn't
useful,
that's
not
to
say
get
up.
Projects
wasn't
useful.
It's
just
like
all
this
information
wasn't
useful,
yeah
and
and
following
like
the
issues
and
the
poor
requests
that
came
in,
wasn't
actually
impactful
to
our
teams
internally
or
to
our
merchants
who
are
using
our
products.
So
what
we
ended
up
doing
was
working
a
lot
closely
with
these
teams.
So
right
now
we're
working
with
the
delivery
team
in
shopify
shout
out
to
their
team.
B
So
they
have
a
lot
of
duplicated
patterns
in
the
admin
or
forked
components
that
they
want
to
consolidate
and
they
want
to
almost
like
break
down
and
make
more
cohesive,
make
more
like
how
the
polarity
system
is
created,
so
work
with
them
to
help
them
achieve
that
goal
and
we'll
we'll
be
bringing
the
like
systems
mindset
and
like
challenging
to
like
the
way
that
they're
approaching
those
problems
but
like
they're,
they're,
very
close
to
the
business
into
the
merchant.
They
understand
those
problems.
B
Deeply
so
there's
a
really
nice
balance
there
of
like
for
us
to
figure
out
what
to
do.
We
work
with
these
teams
that
are
like
solving
these
hard
problems
like
yeah
address
that,
but
we
don't
have
a
public
roadmap
and-
and
that
is
definitely
a
challenging
thing,
with
an
open
source
repository
like
this.
It's
you
can
create
an
issue
and
it
can
sit
there
and
maybe
not
even
get
a
reply,
and
I
I
don't
feel
good
about
that
honestly,
like
this,
like.
A
Yeah
and
that's
something
that
I
so
full
disclosure
folks
who
are
sitting
here,
I
work
at
github
got
a
sweater
on,
and
everything
like
that,
so
it
makes
it
official
when
you
wear
the
sweater,
but
this
is
like
the
conversation
I
have
with
maintainers
like
yourself
of
projects
and
having
this
sort
of
like
weird
balance
of
internal
external
conversation
and
like
sometimes
in
projects,
issues
might
not
be
the
first
like
the
first
interaction.
A
lot
of
times
are
issues
the
open
issue
conversation
gets
started.
A
Sometimes
the
conversation
needs
to
be
something
more
synchronous
or
maybe
there's
like
a
sort
of
I'm
not
not
making
suggestions,
but
maybe
design
system
panel
or
conversation.
Where
folks
can
just
talk
about.
Oh,
I
use
polaris.
I
would
just
want
to
have
conversations
and
get
some
of
these
answers
out
of
the
way-
and
I
know
like
some
other
github
open
source
projects
internally
they're
maintained.
A
But
they
use
publicly.
We
have
like
some
outstanding,
like
bi-weekly
meetings
where
people
can
come
join
like
a
zoom
call
or
a
discord
stream,
and
just
sort
of
hang
out
with
folks
get
questions
and
basically
get
some
of
the
answers.
I'm
getting
right
now
from
you
get
those
in
like
a
place
where
it's
like
a
safe
space
for
you
to
ask
those
questions
which
speaking
of
which
it
folks,
if
you
have
questions-
and
maybe
you
use
polaris
sorry-
maybe
you
work
at
shopify
and
you've
always
wanted
to
ask
questions
to
the
design
system.
A
B
Yeah,
so
I
just
wanted
to
sort
of
like
step
through
a
few
of
those
patterns
that
I
talked
about.
So
if
I
went
to
like
a
a
resource
list,
you
can
sort
of
just
have
a
look
at
like
maybe
just
also
like
some
of
the
challenges
that
we
face
is
like
a
design
system
team
like
with
these
gigantic
components.
So
if
I
go
and
save
all
its
elements,
you
can
kind
of
see
it's
got
like
a
search.
It's
got
tags
that
you
can
add.
B
These
tags
show
up
down
here
as
well,
when
you
write
them
in
we've
got
bulk
editors,
so
these
components
are
much
bigger
and
have
a
lot
of
I'd
say
almost
like
business
logic
in
them
as
well,
which
becomes
really
hard
to
maintain.
This
is
a
big
problem
that
we're
trying
to
address
right
now,
but
I
wanted
to
also
like
take
this
example
and
show
just
quickly
in
my
like
test
store
like
what
this
looks
like.
B
So
when
you
own
a
shopify
store
like
this
is
this:
is
your
experience
like
when
you
log
in
you
can
sort
of
see
that
you've
got
one
order
to
fill?
There's
no
information
here.
That's
like
I
don't
know
bad
like
it's.
Just
all
my
me
doing
fake
orders,
but
you
can
sort
of
see
like
here's
one
order.
It
costs
a
dollar.
You
can
bulk
select
them.
You
can
sort
of
do
these
sorts
of
things,
but
then
you
can
also
go
to
draft
orders.
B
B
I
can
click
into
the
potato
product
and
sort
of
like
see
all
this
information
and
go
and
edit
it,
but
like
all
these
little
pieces
that
we're
seeing
are
bits
of
flowers
so
supposed
to
like
highlight
this
area
like
this
is
our
page
component
and
our
page
component
sort
of
has
the
pagination
or
we
call
it
pagination.
But
it's
like
a
back
button
to
go
back
to
the
previous
page.
It
has
some
key
actions.
B
It
has
titles,
it
has
the
layout
as
well,
so
everything
that
sort
of
gets
centered
in
this
middle
area,
but,
like
all
of
these
little
pieces,
are
bits
of
polaris.
So
if
I
went
back
to
here-
and
we
had
a
quick
look
at
page-
we
can
kind
of
see
that,
like
this
is
what
it's
talking
about
like
we
can
see,
there's
some
app
frame,
then
there's
the
page
component,
which
is
inside
the
art
frame,
so
lots
of
layers
of
pieces
fitting
together
yeah,
but
it's
very
different.
B
I
also
wanted
to
paint
a
picture
that,
like
shopify
as
a
company,
does
lots
of
different
things
like
we
have
our
shopify.com
site,
which
just
doesn't
use
polaris
and
we
wouldn't
even
expect
them
to
because
it's
built
for
a
different
audience.
It's
built
for
a
different
problem
if
they
were
to
use
our
typography
here
like
this
title,
would
not
look
good.
I
think
if
we
go
and
have
a
look
at,
I
don't
know
heading
as
a
component.
B
You
can
kind
of
see
like
that
is:
that's
probably
our
biggest
heading
in
the
admin,
because
we
have
really
tight
ui
and
if
you
were
to
use
that
heading
size
here
and
this
product,
it
just
wouldn't
be
a
good
experience
to
use
this,
and
it
would
be
almost
confusing
around
like
what
is
like
when
I
came
here.
Come
to
this
page.
What
what
is
this
company
trying
to
get
me
to
do?
Yeah.
B
B
B
A
Yeah-
and
I
have
some
background
so
my
previous
employer
was
netlify
and
I
was
I
was
like
early
conversations
in
building
out
their
design
system.
It
was
like
my
first
experience
too
and
being
involved
in
those
conversations
and
they
made
an
early
decision
to
have
a
marketing
design
system
versus
a
just
a
general
development
admin
dashboard
design
system.
So
I'm
curious
is
shopif.
Shopify
have
multiple
design
systems
to
maybe
yeah
the
dev
team
also
approach
with
this
yeah.
B
So
we
definitely
do
and
that's
something
we're
interested
in
like
exploring,
but
it's
not
something
we're
thinking
about
right
now.
I
think,
like
we
have
our
marketing
design
system,
which
I
think
some
parts
of
this
website
are
built
with
and
other
parts
of
custom.
We
have
a
rails
design
system
which,
like
sort
of
takes
a
lot
of
our
react
components
and
puts
them
into
rails.
B
We
have
the
react
design
system,
so
there's
like
lots
of
different
layers,
even
if
it's
just
by
split
by
technology
or
if
it's
split
by
user
but
like
there
are
some
interesting
things,
though,
like
we
would.
We
would
love
and
maybe
we're
a
bit
away
from
this,
but
we'd
love
to
like
have
logic
for
a
modal
or
pop-up.
B
So
if
I
talk
about
the
example
of
a
modal
like
when
a
modal
opens,
try
and
think
of
a
good
example
of
where
there's
a
modal,
I
mean-
maybe
even
like
here
like
same
sort
of
thing
like
things
pop
up,
and
it's
like
you
need
to
position
that
thing
on
the
page.
It
needs
to
sit
above
other
elements.
It
needs
to
maybe
have
a
shadow
like
there's
lots
of
different
patterns
that
I
can
get
replicated
just
in
these
smaller
pieces
that
we
definitely
want
to
make
more
accessible
to
teams.
B
B
The
escape
button
should
close
the
modal,
like
there's
lots
of
different
layers
there,
that
we
would
almost
not
want
every
single
team
to
think
about
across
shopify,
but
we
also
understand
that,
like
teams
need
to
use
the
right
technology
for
the
problems,
they're
solving
and
the
design
system
isn't
the
right
technology
for
every
team
and
every
problem
they're
solving.
So
it's
it's
definitely
a
challenge.
Well,
the
polaris
design
system,
as
it
is
today.
A
Okay,
awesome:
there
was
a
question.
I
came
in
the
chat
before
we
switched
to
your
screen,
but
I
wanted
to
ask
because
it
kind
of
segues
into
what
we're
talking
about.
Yeah
elenic
actually
dropped
this
in
the
chat,
which
was
what
would
you
say,
the
motivation
for
internal
teams
to
start
consolidating
their
patterns
to
work
with
something
like
the
polaris
team.
B
A
Okay,
cool
yeah,
and
it's
like
the
my
next
question:
would
it
be
like?
How
do
you
approach
because,
like
design
seems
to
always
have
iterations
change,
it
seems
like
when
one
company
does
something
a
lot
of
other
companies
follow
suit
like
basically,
I
guess
I'm
talking
about
trends
and
patterns,
yeah.
B
B
B
Here
that,
like
there's
this
green
color
and
this
green
color
is
called
border,
success
subdued
and
that's
sort
of,
like
our
token
value
for
this
color,
and
what
this
means
is.
If
we
wanted
to
go,
this
is
maybe
a
better
image.
Actually,
you
can
see
like
what
a
success
subdued
is
like
the
top
line.
Icon
success
is
the
icon,
color
and
surface
success
of
jude
is
like
the
background
color
on
this
little
section.
It's
really
small.
B
So
if
I
try
and
zoom
in
a
little
bit
so
that's
really
helpful
but
like
when
we
want
to
pivot
or
adjust
or
change
like
now.
We're
just
changing
these
semantic
values
so
say
that
we
wanted
to
experiment
with
success,
colors,
maybe
more
vibrant
or
higher
contrast
or
a
little
bit
more
in
your
face,
like
maybe
that's
like
there's
a
bit
more
attitude
in
this
design.
This
becomes
a
really
powerful
system
or
platform
for
us
to
go
and
do
this
so
clara's
tokens
is
a
private
repo.
B
Otherwise,
I'd
love
to
like
step
you
through
that,
but
it
has
a
lot
of
our
I'd
say
almost
like
variables
or
like
values
that
we
sort
of
define
for
our
design.
So
typography
is
another
great
example.
Like
you
can
kind
of
see.
You
know
this
is
display
extra
large
and
that
has
these
values.
This
is
display
large.
So
if
we
wanted
to
make
a
big
sweeping
change
to
our
type
scale,
we
could
come
in
here
and
we
could
make
that
adjustment,
which
is
really
great.
A
Okay,
cool
and
I'm
I'm
always
curious
about
this
question
too,
as
well
like
what
are
some,
and
maybe
this
is
stepping
away
a
little
bit
from
polaris.
But
what
are
some
trends
that
you're
seeing?
Could
you
show
the
shopify
dev
site
yeah
that
looks?
It
seems
like
this
feels
fresh.
It
feels
like
I've
seen
not
this
exact
approach
but,
like
I
feel,
like
I'm
gonna,
see
more
sites
that
look
like
this
in
the
future
yeah.
B
Yeah
I
mean
this
is
this
is
maybe
a
cop
out,
but
I
think,
like
tailwind,
is
a
really
big
trendsetter
right
now
and
the
things
that
I
spot
straight
away
is
like
the
vibrant
colors,
the
gradients.
This
has
always
stood
out
to
me
when
I've
like
gone
to
this
table
inside,
but
they're
like
choice
of
color
and
the
way
that
they
like
interlock
these
gradients.
Just
really,
I
think,
is
a
pattern
that
I
think
is
proven
to
be
successful.
B
B
Yeah,
it's
it's
a
very
popular
family.
I've
seen
that
show
everywhere
now,
but
I
think
these
like
thick
dark
layers
of
typography
is
like
really
something
that
stands
out,
and
this
is
just
as
an
aside.
This
isn't
my
expertise.
I
have
much
more
talented
people
in
my
team
that
like
have
opinions
on
this,
but
this
is
the
sort.
This
is
the
sort
of
stuff
that
I
think
personally,
when
I
think
of
like
design
trends
right
now,.
A
A
What
I
love
about
design
systems
is
that
if
I
could
have
some
solve
problems,
because
I
could
I
could
connect
a
redux
store
and
maybe
a
back-end
api
like
no
one's
business,
but
when
it
comes
to
making
decisions
around
modals-
or
I
was
actually
really
intrigued
around
this
clicking
and
activating
the
search
box
and
graying
out
the
rest
of
the
screen.
I've
never
thought.
A
To
like
okay,
you're
searching
this
and
start
typing
and
you'll
see
something
else
happen,
yeah,
just
mind-blowing,
and
every
time
I
see
a
trend
or
I
find
a
design
system
that
makes
good
use
of
of
my
eyeballs
and
like
getting
stuff
to
me
as
quickly
as
possible.
I
just
I
just
appreciate
it
so
much
more.
B
Yeah
definitely
so
it's
really
it's
a
really
interesting
space
to
be
in
because
it's
the
intersection
of
code
and
design
and
like
we
also
like
as
a
company,
we're
trying
to
hire.
I
think
some
ridiculous
number.
I
think
it's
like
2021
developers
this
year
and
to
hire
2021
developers
and
to
give
them
a
really
powerful
design
system.
B
For
you
know
the
product,
like
the
admin
products,
means
that,
like
you
know,
they
don't
have
to
be
masters
at
everything,
but
we
do
want
them
to
still
work
closely
with
design
teams
and
like
challenge
those
decisions
they're
making.
But
you
know
if
they
don't
have
to
think
about
every
single
layer
of
you
know
how
a
modal
should
work
or
how
a
search
box
should
like
attract
focus.
I
think
that's
a
win
and
I
think
there's
a
lot
of
areas
of
design
systems
can
help
in
that
space.
A
B
I
am
trying
to
hire
a
senior
engineering
manager
and
a
senior
front-end
developer,
so
there's
two
roles
that
I'm
trying
to
hire
on
my
team
right
now.
So
if
you're
interested
you
can
just
reach
out
to
me
on
twitter,
alex
page
underscore
and
more
than
happy
to
have
a
chat,
but
those
there's
two
roles
that
I'm
trying
to
hire
right
now.
Shopify
is
it.
B
B
Yeah,
I
mean
it's
one
of
it's
one
of
the
answers
yeah,
so
maybe
just
quickly
like
I
won't
show
this,
but
like
this
was
that
project
I
was
talking
about
before.
Just
like
help
us
manage
thousands
of
issues
and
put
requests,
I
did
want
to
talk
a
little
bit
about
creating
a
foundational
system,
so
yeah
like
we
were
talking
about
a
lot
of
the
problems.
B
This
is
all
open.
We
have
a
whole
bunch
of
like
open
source
conversations
here
that
you
know
they're
very
focused
on
what
our
team
needs
or
what
our
team
is
thinking
about
but
like
if
I
go
into
like
replacing
sass.
This
is
a
really
interesting
discussion
that
we
started
around
like
the
problems
that
we're
feeling
using
sas
as
a
design
system
team
and
how
we
think
that
we
could
like
address
them.
So
we
sort
of
went
through
a
whole
bunch
of
examples.
B
We
even
created
a
like
open
source
spreadsheet
that
people
could
like
drop
into,
and
we
got
a
lot
of
positive
feedback
around
this
like
way
of
thinking
and
doing
research.
So
I
just
wanted
to
share
this
as,
like,
I
don't
know
like
just
a
different
way
of
like
building
new
open
source
projects
or
like
trying
to
figure
out
problems,
because
I
think
that
this
is
a
really
interesting
way
of
doing
that.
A
B
B
Anything
in
here
that
anyone
using
fluorescent
react
would
need
to
worry
about
today,
but,
like
we
really
want
to
like.
We
want
to
start
thinking
without
restrictions
of
like
where
could
polaris
go
like?
How
could
we
build
a
foundation
to
enable
like
greater
variation
of
design
and
just
starting,
fresh
and
playing
around
has
been
a
really
great
way
to
like
build
opinions
on
that.
A
A
B
B
A
B
Oh
yeah
yeah,
we
love
github.
Actions
like
we
have
some
I'd
say
like
nothing
too
crazy.
We
need
to
like
this
is
actually
looking
pretty
good
but
like
we
have
the
old
k
sheen
in
here,
but
this
has
been
updated
but,
like
we
have
some
like
simple
ci
stuff
that
runs
and
like
accessibility
tests,
which
is
really
awesome,
really
helps
us
like
quickly
gain
confidence
on
pull
requests
like
are
these
meeting
our
expectations?
B
Another
one
that
I
really
liked
was
size
limit.
So
you
can
check
out
this
one,
but
it's
a
really
powerful
tool
to
just
see
how
pr's
are
impacting
the
sizes
of
packages.
So,
as
a
component
library,
we
would
love
to
like
see
a
reduction
in
the
size
of
the
things
that
we
want
to
maintain.
So
we're
trying
to
be
very,
I
don't
know
very
conscious
of
when
things
are
growing
and
this
this
action
is
a
really
powerful
way.
B
B
The
other
thing
that
I
think
that
is
like
top
of
mind
would
be
something
like
google
lighthouse,
just
like
running
that
sort
of
extension,
just
like
check
for
like
accessibility
performance
like
just
a
quick
bottle,
sorry
benchmarks,
just
to
make
sure
that
we
are
like
not
having
any
progressions
as
we
like
make
changes,
but
usually
that
happens
in
our
top
padding
so
top
adding
is
just
what
we
call
testing
you
put
a
top
hat
on
and
check
check
it.
I've.