►
From YouTube: UX Showcase - Pajamas scaffolding, structure, and ops
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
All
right,
so
my
name
is
Jeremy
Elder
I'm,
a
Staff
product
designer
on
the
foundations
team,
and
there
is
a
recording
on
this.
It's
22
minutes.
Hopefully,
I
can
maybe
shave
off
some
time
and
spare
you
having
to
watch
me
on
that,
one
for
the
New
York
showcase
I'm
talking
about
pajama
scaffolding,
structure
and
Ops,
and
what
this
is
is.
Let
me
just
go
over
to
the
Epic
here.
I
won't
read
all
through
this,
but
it's
it's
about
two
parts
here:
one
is
creating
and
filling
some
gaps
in
pajamas
to
help.
A
A
So
when
we
say
a
pattern
or
organism
or
region,
doesn't
that
mean
everything
or
mean
the
same
thing
to
everybody
likely
not
and
so
working
on
really
firming
up
some
of
our
definitions
of
of
these
different
concepts
and
pajamas,
and
so
there's
there's
three
phases
that
initially
working
through
one
is
a
scaffolding
so
working
on
definitions,
working
on
how
that's
reflected
in
the
website
with
the
information
architecture,
content,
mapping
and
then
the
third
piece
of
that
is
a
gap
analysis.
A
So
that
would
be
determining
two
parts:
one:
what
are
just
gaps
that
exist
in
pajamas
itself?
Where
is
it?
Where
is
there
no
opinion
or
statement
about
how
to
do
something
and
the
other
would
be
where
are
gaps
between
pajamas
and
the
product?
So
are
there
things
that
we're
doing
in
pajamas
that
the
product
isn't
adopting
or
there's
really
strong
patterns
in
the
product?
But
we
don't
really
have
pajamas
documentation
to
to
point
back
to
so
identifying
those
gaps.
A
The
the
second
phase
is
Pajama
structure,
so
just
taking
some
of
those
IA
changes,
those
learnings
what
we
decide
on
and
just
implementing
it
into
the
website
itself,
which
is
where
all
of
that
kind
of
information
is
expressed.
And
then
this
is
just
a
question.
I
have
and
what
would
it
take
to
make
pajamas
a
single
source
of
Truth
and
and
what
I
mean
by
that
is
that
we
have
the
svgs
project.
We
have
gitlab
UI,
we
have
pajamas,
we
have,
maybe
our
utility
classes
that
you
can.
A
You
can
find
the
repo
on
there's
different
places
to
find
pajamas
information
and
what
would
it
take
to
make
pajama
site
the
actual
go-to,
the
jumping
off
point
for
all
of
that
to
make
it
more
of
a
single
source
of
Truth
so
that
we
can
address
all
audiences,
that's
kind
of
a
peripheral
question,
I'm
asking,
but
something
that's
in
the
back
of
my
mind
and
then
the
last
phase
is
what
I
call
pajamas
Ops,
so
you've
probably
heard
of
design,
Ops
and
obviously
devops,
but
pajamas
Ops
things
specific
to
pajamas
operations.
A
So
how
can
we
maybe,
with
storybook,
create
a
playground
with
features
and
accessibility
testing
and
the
ability
to
put
together
layouts
and
utility
classes
so
that
you
know
what's
possible
with
Pajamas
and
and
that
would
be
kind
of
a
crossover
between
design
and
Engineering
or
how
about
figma?
How
can
we
do
internal
plugins?
A
That
will
make
the
team
more
efficient,
so
embedding
content
from
the
svgs
project
or,
like
you
know,
like
a
third-party
logo
or
a
better
linking
of
a
figma
file
with
an
issueable
in
Gate
lab,
so
things
along
those
lines
also
a
triage
contributions,
some
of
that
workflow
related
stuff,
so
lots
of
different
things
here,
I'll
highlight
a
few
outcomes
and
then
I'll
jump
into
kind
of
where
I've
been
at
in
the
process
today.
A
So
the
outcomes
I'm
hoping
for
would
be
to
be
more
consistent
in
design,
execution
and
user
experience
have
a
shared
design.
Language
right
now,
I
feel
like
just
to
be
candid
pajamas
is
is
more
of
a
design
system
to
be
fair,
which
has
its
own
components
and
attributes
and
Concepts.
But
it's
not
quite
a
design
language
where
we've
got
the
parts
of
the
language
and
speech,
but
we're
not
always
using
them
to
articulate
a
complete
thought
and
I
want
pajamas
to
be
able
to
be
more
of
a
design
language.
A
Where
you
can,
you
can
see
these
parts
of
the
language
essentially
and
put
them
together
and
consistently
articulate
a
message
for
our
users
and
an
experience.
Another
outcome
would
be
to
have
more
informed
design
decisions
and
contribution.
A
So
if
we
have
clear
paths
on
on
our
opinion
on
what
design
should
be
or
or
how
we're
expressing
different
flows
having
that
documented,
so
that
we
have
a
better
place
to
point
to
and
then
lastly,
just
pajamas
and
product
planning
and
prioritization,
how
do
those
tie
together
so
that
we
can
be
the
best
at
making
decisions
and
pajamas
that
will
that
will
help
support
the
work
and
the
planning
that's
happening
in
the
product,
so
I'll
jump
in
here
with
what
I've
done
today
and
I'll
keep
this
fairly
abbreviated,
but
I
really
wanted
to
document
current
state.
A
So
that's
where
I
started
working
on
definitions.
These
definitions
come
from
the
pajama
site
today.
If
you
go
under
get
started,
structure
you'll
see
these
different
categories
of
of
what
we
consider
the
structure
of
pajamas
I
focused
on
the
main
ones
that
deal
with
the
UI
itself
at
first
so
foundations,
components,
regions
objects
won't
go
into
what
those
are
you
can
find
them
over
in
pajamas
and
I
just
took
a
look
at
the
current
IA
for
the
site
itself.
So
I
have
a
legend.
We
have
our
different
sections.
A
You
can
see
that
the
product
section
is
the
deepest
and
and
that's
to
be
expected
and
then
started
thinking
about
what
what
can
be
done
to
to
actually
change
this
up.
How
can
we
move
this
forward?
A
A
little
side
note
if
you're
familiar
with
atomic
design,
you've
probably
heard
me
say
that
I
feel
like
pajamas
is
missing
some
of
those
internal
layers
that
would
help
us
assemble
our
parts
to
to
have
kind
of
a
complete
design
and
we've
had
conversations
about
what
well,
why
not
adopt
Atomic
design,
and
the
reason
for
that
is
because
Atomic
design
is
very
much
structured
on
how
you
would
build
something.
A
It's
kind
of
your
Workshop:
how
am
I
going
to
assemble
these
different
parts,
but
when
it
comes
to
consumption
and
use,
you
need
more
of
a
storefront
and
bread.
Frost
articulates
this
really
well
and
you
need
a
more
of
a
storefront
where
somebody's
going
to
come
in
and
and
they
don't
necessarily
care
how
the
bread
was
made
or
what
all
the
ingredients
are,
but
they
just
want
bread,
and
so
pajamas
is
that
storefront
of
of
somebody
coming
in
and
saying
how?
A
How
can
I
take
this
off
the
shelf
and
use
it
and
apply
it
to
what
I
need?
So
that's
why
Atomic
design
and
that
thinking
is
there
but
I
think
our
expression
of
how
we
assemble
the
parts
needs
to
be
a
little
more
on
the
the
consumer
of
the
the
pajamas
product.
So
once
I
get
too
deep
in
that
we
can
carry
that
conversation
on
later.
But
what
I've
done
in
this
exercise?
A
This
is
where
I'm
at
today
in
15
2
worked
on
updating
some
definitions
and
you
can
see
I've
got
a
little
a
lot
of
little
speech
bubbles
here.
These
are
all
prompts
so
afterwards.
Well,
in
fact,
I
think
I
did
link
up
in
the
document.
This
figma
file
here
so
feel
free
to
jump
in
every
time.
You
see
my
little
face
in
one
of
these
bubbles.
That's
just
a
prompt
that
I've
asked
a
question
or
expressed
a
thought
about
where
I'm
headed
with
some
thoughts.
A
So
please
leverage
that
to
to
jump
in
and
add
to
the
conversation.
I'll
turn
those
off
for
a
second
and
so
with
Pajamas
working
on
definitions
is,
is
one
of
the
ways
that
I've
started.
So
how
can
we
build
out
these
Concepts
and
and
really
clarify
some
things
and
I
won't
read
through
all
of
these
or
any
of
them
really.
But
these
are
the
the
main
categories,
so
foundations
components,
patterns,
templates,
objects
and
flows.
A
So
it's
taking
something
from
a
very
opinionated
design
attribute
which
will
help
Express
Gate
lab
personality
and
then
carrying
it
all
the
way
through
into
flows.
So
how
is
the
user
experiencing
the
product
and
if
we
can
document
these
things
end
to
end
and
provide
meaningful
examples,
and-
and
you
know,
working
Concepts,
then
it'll
better,
enable
us
to
to
have
a
more
opinionated
git
lab
design,
carry
all
the
way
through,
so
that
when
we're
doing
efforts
like
unboxing
or
beautification,
we
have
something
to
stand
on
and
to
say
well.
A
Is
this
the
gitlab
design
language
is
it?
Is
it
speaking
that
does
this
feel
like
it?
Does
it
look
like
it
love?
Is
it
consistent
with
other
experiences
in
the
product,
so
lots
to
to
dive
in
on
here,
I
have
gone
through
some
just
visual
exploration,
I
like
to
kind
of
capture
a
thought
visually,
and
so
maybe
expressing
that
an
iconography
or
some
graphics
that
we
could
start
to
maybe
Infuse
into
pajamas
to
help
kind
of
cauterize
where
you,
where
you
might
be
in
pajamas
or
some
of
those
Concepts.
A
So
here's
the
stack
right
like
foundations,
components,
patterns,
templates,
objects,
flows
showing
how
it
builds
together
and,
like
I,
said,
there's
more
to
be
learned.
If
you
go
and
read
these
definitions
and
follow
up
on
some
of
the
conversation
happening
there
as
far
as
the
information
architecture
went
through
an
exercise
to
rework
that
a
little
bit
and
anything
that
is
green,
is
a
new
page
or
a
link.
Anything
that's
got
the
purple.
A
It's
it's
moved,
it's
renamed,
there's
other
Concepts
in
there
in
the
legend
that
you
can
take
a
look
at,
but
the
main
goal
is
to
really
organize
this
content
and
more
meaningful
and
concise
ways
and
hopefully
provide
easier
and
easier
experience
as
we
contribute
to
pajamas
in
the
future.
So
knowing
where
things
go
where
they
really
fit.
Today,
it's
a
bit
fuzzy
with
regions
and
objects,
and
so
how
can
we
make
that
through
decision,
trees
or
other
methods
and
organization
make
that
more
structured
and
easier
to
to
work
with
so
I?
A
Encourage
you
to
take
a
look
through
these
and
see
some
of
the
changes
and
see
what
sits
well
with
you,
or
maybe
what
doesn't
there's
some
section
mapping
so
taking
a
look
at
what
our
current
sections
are
in
pajamas
and
is
the
concept:
how
do
those
things
either
get
renamed
or
reworked
or
or
what's
new,
what's
reorganized
so
some
thoughts
there
and
also
I,
wanted
to
express
this
visually
with
just
the
nav
concept.
To
really
see
would
this
IA
carry
through
into
like
usability?
A
Does
it
make
sense
kind
of
at
first
blush,
and
so
this
is
just
a
quick
concept
of
pajamas
navigation
where,
if
I
took
all
these
Concepts,
how
would
I
flush
it
out
in
a
site
and
and
does
it
make
sense
structurally,
as
I
read
through
this?
Does
it
look
clean
and
and
I
think
to
me
at
least
the
answer
is
yes
like
this
seems
like
a
cleaner
presentation
and
more
concise,
and
that's
really
what
I'm
trying
to
do
with
with
the
approach.
A
One
thing
I
do
want
to
call
out
is
that
today
we
when
you
go
to
the
pajama
site,
you'll
see
gitlab
design
system
with
the
Tanuki
there's
no
real
pajamas
branding,
if
you
will,
on
the
home
page
and
as
part
of
this
exploration,
being
able
to
add
that
that
flavor
and
have
it
be
leading
with
pajamas
and
then
State
as
a
descriptor.
It's
the
git
lab
design
system.
So
this
is
just
a
rework
again
feel
free
to
jump
in.
You
can
see
with
all
the
the
chat
going
on
that
there's.
A
There's
plenty
of
conversations
to
be
had
so
I
would
encourage
you
to
do
that,
as
well
as
take
a
look
at
the
the
Epic
itself,
the
the
issues
under
it
and
by
all
means
please
I,
would
love
to
hear
your
thoughts
jump
in
on
the
conversation
and
the
the
outcome
will
hopefully
to
be
a
a
pajamas
design
system
and
design
language
that
helps
us
to
better
Express,
a
kind
of
a
git
lab
method
of
doing
things,
to
make
design
decisions
easier
and
more
consistent,
but
also
contributing
more
consistent
and
then
user
experience.
A
When
we
talk
about
flows,
I
know
Mike
Nichols.
You
have
some
great
thoughts
on
flows
that
have
greatly
contributed
to
to
this
effort,
and
so
that's
kind
of
the
ux
piece
of
that
as
well.
So
I
will
stop
sharing.
A
B
Can
I
ask
an
improp
two
question
that
I
have
yet
to
type
down
and
it's
related,
but
it's
not
Thomas
design
related,
and
maybe
this
is
a
dumb
question
that
everyone
already
knows
the
answer:
what's
the
story
behind
the
name,
pajamas
I
got
asked
this
in
an
interview
yesterday,
where
does
that
come
from.
A
So
what
I've
been
told
is
that
early
on
with
async
work
and
everybody
working
from
home,
it's
just
related
to
hey.
You
can
work
in
your
pajamas
and
that
was
kind
of
the
the
very
simple
version
of
that
I
think
Tori
could
probably
provide
some
more
color
into
that.
But
that's
what
I'm
aware
of.
C
Yeah
we
had
an
issue
a
while
back
on
naming
and
I
I
think
Pedro's
the
person
who
came
up
with
pajamas
and
yeah.
It
was
a
nod
to
our
remote
culture
before
the
whole
world
was
remote,
so
I'll
probably
dig
up
that
issue.
I
was
gonna.
Ask
three
like
what
year
is
that
issue?
How
when
did
you
open,
yeah,
either
2017
or
2018
I?
Don't
know,
I
can't
remember
some
sometime
around
then
I
think
probably
2018,
it's
more
accurate,
so
that
would
mean
pajamas
is
almost
five
yeah.
D
C
A
It's
still
there,
that's
that's
one
that
that's
a
battle.
I
didn't
want
to
go
like
and
I'm
like
socks
and
pajamas
like
I.
It's
to
me
that's
a
different
time
of
day
and
so
I,
but
I'm
I'm
not
gonna.
Go
there
I'll,
let
others
you
know,
maybe
in
the
winter,
in
a
colder
climate
or
if
I'm,
camping,
but
I
decided
not
to
go
there.
A
But
when
you
so
so
side
note,
since
you
bring
up
bring
up
socks,
if
you
didn't
know,
there's
another
design
system
for
gitlab
called
slippers,
and
this
is
for
the
marketing
side
of
things
and
I
will
I
should
note
that
if
you
get
a
chance
to
learn
more
about
that,
please
do.
But
that
is
out
of
scope
for
this
effort
as
well,
but
just
another
clothing
item
and
at
some
point
maybe
we'll
work
in
some
other
Easter
eggs
with
with
the
pajamas
theme.
But
that's
TBD.