►
From YouTube: PWA Studio Community Meeting 6 February, 2020
Description
Demos: UX research and finding for cart/checkout, Category and Search Filters, Cart Edit, and new Community Contribution board.
A
A
B
So
everybody
can
see
the
keynote
so,
as
Andrew
said,
they're
just
kind
of
quickly
share
some
of
the
latest
design
research
we've
done
Ravinia
and
today
we're
going
to
talk
about
shopping,
cart
and
check-out.
Do
some
quick
introductions?
I
think
you
all
know
so
me
and
Scot
the
designers
for
PWA?
This
is
my
first
time
here
so
I'll
introduce
myself
I'm
Katherine,
Chiodo
I'm,
a
researcher
here
at
Magento
I
work
across
our
products
that
have
lately
been
lucky
enough
to
be
working
with
some
Ian
Scott,
one
pwe.
B
So
where
did
this
research
come
from
last
year?
Last
summer
we
did
a
series
of
merchants
site
reviews
where
we
looked
at
merchants
sites,
and
we
did
kind
of
UX
evaluation
was
then
had
conversations
with
merchants
about
what
they
struggled
with
on
their
site,
what
they
wanted
to
do
to
improve
it,
that
kind
of
thing
and
what
we
saw
over
that
were
frequently
using
luma
out-of-the-box,
even
when
that
wasn't
necessarily
to
their
advantage.
We
also
heard
from
them
that
customization
was
tricky
and
expensive.
B
So,
knowing
that
and
going
into
vineya,
we
want
to
make
sure
that
whatever
out-of-the-box
functionality,
we
design
really
works
in
common
use
cases.
And
obviously
we
talk
to
our
partners
a
lot.
We
talk
to
community
and
we
have
luma
as
a
baseline.
But
here
we
wanted
to
fill
in
that
one
missing
piece,
which
is
how
our
shoppers
experiencing
kind
of
baseline
shopping
experiences
online.
And
how
can
we
roll
those.
B
B
So
this
is
what
this
research
came
from
and
a
quick
note
about
this
you'll
notice,
we
say
internal
participants,
so
these
are
Magento
employees
who
buy
stuff
online
and
who
were
willing
to
kind
of
put
on
their
shopper
hat
and
go
through
this
prototype
with
us
because
of
that
they're,
probably
a
little
more
savvy
than
your
average
shopper,
they
may
be
familiar
with
kind
of
cutting-edge
design
package.
That's
showing
up
online
and
I,
probably
understand
the
technical
stuff
behind
it.
More
that's
something
to
keep
in
mind
as
we
look
at
the
findings.
B
Our
goals
for
this
were
you
know,
baseline,
is
just
to
find
out
where
our
prototypes
and
met
expectations
and
where
they
did
not,
where
we
maybe
needed
to
change
them
and
improve
them.
And
here
we
want
to
get
insight
both
on
the
functionality
like.
Could
it
do
what
shoppers
expected
it
to
do
and
usability?
B
You
know,
could
they
figure
out
how
to
do
those
things,
but
we
also
wanted
to
kind
of
level
up
this
knowledge
a
little
bit
to
better
understand
the
context
and
behaviors
the
choppers
bring
to
curtain
checkout
so
a
little
bit
about
higher
level
stuff.
So
with
that,
I
will
jump
into
the
findings.
These
are
divided
into
five
kind
of
sections
going
linearly
through
from
cart
to
finishing
checkout,
though
here
we
have
cart
overview
and
one
other
thing.
I
should
note.
B
We
had
a
ton
of
findings
for
each
of
these
pages
and
here
we're
just
kind
of
pulling
out
the
two
that
we
think
will
be
most
roll
for
the
folks
on
this
call
or
the
ones
that
really
fed
into
our
design
decisions.
So
these
are
sort
of
the
cream
of
the
crop,
so
to
speak.
They're
here
we
had
a
hypothesis.
We
were
testing
for
this
first
finding.
We
had
seen
this
pattern
of
having
an
update
link
online.
Even
when
auto
update
was
in
place.
B
We
didn't
really
know
why
sites
were
doing
that,
but
it
seemed
like
something
that
was
maybe
useful.
Otherwise,
why
would
they
be
doing
it?
So
we
put
it
into
this
design
and
tested
it.
We
found
that
pretty
much
across
the
board.
It
was
confusing.
I
first
did
not
understand
why
it
was
there
if
auto
update
was
happening,
so
that
is
something
we've
changed
in
our
design
and
removed
it.
The
second
thing
we
heard
about
was
you
can
see
at
that
number
two.
There,
the
three
dots
arranged
vertically.
B
Item
and
we're
really
curious,
if
even
these
very,
very
savvy
shoppers
that
we
have
internally
Magento
would
would
get
what
this
was,
that
they
could
click
on
it
to
get
more
actions.
We
found
that
most
participants
did
not
get
it.
They
did
not
know
they
could
go
there
to
edit
or
remove
an
item
so
we're
now
considering
whether
we
can
expand
their
actions,
but
that
is
not
something
we
rolled
into
designs
yet.
B
That's
great
great
edition,
Scott
and
idea.
This
presentation
alternate
over
to
Scott
insomnia
to
answer
any
kind
of
specific
questions
about
stuff
like
that:
okay,
sorry,
next
section
to
a
five,
this
is
really
actions
in
cart,
I'm,
specifically
editing
or
removing
an
item.
We
also
looked
at
applying
coupon
codes
before
it's
that
kind
of
thing
in
messing
with
shipping
options,
but
none
of
that
really
cause
problems,
so
we'll
focus
on
the
edit
and
remove
item
at
the
top.
The
first
thing
we
heard
is
that
participants
really
expected
to
be
able
to
use
step.
B
The
item
number
down
to
zero.
You
can
see
in
our
prototype
the
stepper.
The
down
stepper
is
disabled
with
one
item.
This
is
an
update.
We've
gone
ahead
and
made.
We
also
heard
that
participants
expected
to
be
able
to
click
through
either
the
item
image
or
the
item
name
to
a
PDP
or
PDP.
Like
experience
right,
they
wanted
to
be
able
to
see
the
item
again
when
they
did
that,
and
this
was
something
that
the
prototype
didn't
cover.
B
It
was
good
for
us
to
know
that
expected
behavior
and
then
finally,
we
specifically
asked
what
they
would
expect
to
happen
if
they
wanted
to
say
it
by
two
of
these
pants,
but
only
one
was
available
and
we
heard
that
they
would
expect
to
get
an
error
message
explaining.
You
know
why
they
couldn't
add
it
to
their
cart.
B
Come
on
to
shipping
here
there's
some
more
kind
of
high-level
findings
that
may
be
useful
for
the
folks
on
its
call.
The
first
was
that
participants
really
called
out
the
Express
Checkout
option.
We
had
PayPal,
they
appreciated
it
and
we
even
heard
that
they
wanted
more
Express
Checkout
options
like
Apple
pay
or
ribbon
mill.
B
B
B
God,
let
me
know
if
I
break
up
again,
so
the
next
kind
of
phase
in
our
check
out
was
payment,
and
here
we
heard
kind
of
three
things
that
we
immediately
rolled
into
designs.
The
first
was
that
we
had
in
this
initial
prototype.
Two
email
addresses
one
for
shipping
and
one
for
billing,
but
they're
about
participants,
just
sort
of
thought
that
was
odd,
and
so
we
decided
to
consolidate
to
one
email
address
the
second,
and
this
is
something
that's
probably
my.
D
Context
around
the
first
finding,
though,
as
we
understand
currently,
the
email
is
collected
at
a
level
in
luma,
and
there
was
some
concern
from
community
when
Chekhov
was
first
demo,
that
there
was
no
way
to
be
able
to
change
the
billing
email,
and
so
what
we
did
was
we
included
this
in
in
the
test
to
see
if
people
would
be
there
in
time
to
do
that
and
the
major
use
cases
that
they
would
be
using
the
same
on
for
shipping,
even
a
movie,
to
see
context.
Perhaps
in
a
b2b
context.
D
You
know
people
may
want
communication
around
shipping
and
billing
to
be
sent
to
different
addresses,
but
we're
not
addressing
those
use
cases
in
this
b2c
version
of
venya
and
also
currently,
we
don't
have
the
ability,
from
a
Magento
end,
to
support
communication
going
to
two
different
email
addresses.
So
keeping
all
of
this
in
mind.
We
just
that
at
this
point
in
time,
we
would
not
be
able
to
offer
the
control
to
change
the
billing
email
and
have
it
be
different
than
the
shipping
one.
B
Okay,
thanks
Samuel,
another
kind
of
higher
level
thing.
We
heard
that
I'm
just
calling
out
on
this
page
is
that
poppers
wanted
to
be
able
to
see
what
they
were
buying
throughout
the
checkout
process.
They
wanted
that
reassurance
that
they
were
in
fact
buying
the
items
that
they
intended
to.
So
that
is
something
we've
gone
ahead
and
rolled
into
designs.
It's
showing
the
items
and
their
details
on
each
page
and
then
the
final
kind
of
interesting
call-out
here
is.
B
B
And
so
this
is
fascinating
right,
because
this
wasn't
his
real
credit
card.
This
is
a
prototype
test.
Don't
you
encounter
that
kind
of
resistance,
even
in
a
I
kind
of
make-believe
scenario,
it
suggests
a
kind
of
unease
that,
even
if
a
really
small
minority
of
shoppers
experienced
that
it
could
trip
them
up
in
the
checkout
process,
which
is
obviously
not
what
you
want.
So
we've
gone
ahead
and
changed
the
wording
on
the
continue
button
here
to
make
it
clear
that
they'll
have
another
stuff
where
they
can
review
their
order.
B
So
once
the
order
is
placed
we
arrived
at
the
confirmation
screen,
and
here
we
had
a
kind
of
one
big
take
away,
which
is
that
we
have.
This
create
account
button
which
you
know.
Obviously
you
want
people
to
create
an
account
that
you
know
users
check
out
I,
don't
really
need
to
explain
all
the
benefits
of
that,
but
here
most
our
participants
thought
that
if
they
clicked
create
account,
they
would
have
to
reenter
all
their
information.
B
We'd
love
to
hear,
if
folks,
on
the
call
have
questions
about
shopper
needs
or
hypotheses
about.
You
know
things
that
you
think
are
in
place
or
would
work
really
well
we'd
love
to
hear
about
them
so
that
we
can
roll
them
into
future
studies
and
investigate
them.
Some
of
the
areas
we're
talking
about
right
now,
as
are
things
we
might
want
to
look
into
our
bundled
products.
C
A
All
right,
I
think
so
I
think
I
mean
this
is
really
greedy
insight,
I
think
into
and
you've
seen
us
start
to
roll
out
additional
venue
features
right
and
storefront
features
that
there's
a
lot
of
thought
that
is
going
into
those
features.
Is
we
have
an
entire
team
dedicated
to
designing,
researching
and
make
sure
we're
making
clean
and
logical
decisions
for
what
we're
rolling
out?
So,
of
course
we
welcome
the
feedback
from
community.
If
you
guys
see
us
work
out,
somebody
see
us.
A
E
E
E
So
if
you
select
new
options,
there
adjust
things
and
if
you
decide
to
cancel,
you
can
just
close
that
close
the
modal
and
say
oh
I
meant
to
edit
my
dress.
Instead,
I
meant
for
an
extra
small
on
deck
goals,
so
it
just
persists
that
to
your
Magento
back-end
reflects
that
and
you're
good
to
go
so
kind
of
highlight
some
of
the
technical
features
there.
E
We
just
continued
heavily
leveraging
Apolo,
fragments
and
graph
QL
here.
So
the
really
neat
thing
that
once
once
I
committed
either
these
mutations
to
either
just
update
quantity
or
to
actually
update
the
configurable
options,
which,
surprisingly
enough
is
not
an
edit,
it's
actually
a
add
and
remove,
but
you'll
see
here
that
you
kind
of
automatically
rerender
that
cart
listing
all
I
had
to
do
is
import.
This
cart
page
fragment
here.
E
They,
when
remove
item
from
cart,
go
ahead
and
return
me
the
contents
of
my
cart
with
all
of
this,
so
like
very
little
effort
as
soon
as
this
mutation
comes
back
and
automatically
triggers
you
render.
So
this
pattern
has
been
amazing
since
we
started
implementing
it
so
kind
of
showcases
the
power
of
Apollo,
relying
on
that
cash
and
react
to
just
monitor
that
cash
and
reread
her
needs
to
kind
of
just
magic.
E
F
E
And
talks
about
like
on
mobile
I
can't
lead
Emma
this
desktop,
but
on
mobile
you
have
like
input
types
to
like
when
I
go
to
like
edit
this
on
mobile
you're,
like
your
number
pad
that
had
the
adverse
effect
of
adding
this
like
stepper
and
it
meant
like
we
couldn't
really
style
this
input.
How
we
wanted
to,
but
we
it
turns
out
that
that's
actually
like
the
the
number
input
type
is
not
really
usable
at
all.
So
we
backed
out
that
change.
E
E
I
J
K
K
A
So
we
have
some,
we
have
a
story
within
the
checkout
work
once
we're
done,
we're
fully
known
current
checkout
to
go
back
now
and
deconflict.
The
experiences
between
what
currently
exists,
with
that
kind
of
mini
cart
and
checkout
flow,
and
then
what
exists
without
this
full
page
view.
So
we
we
still
have
plans
to
address
that.
We
have
concrete
answers
for
how
we're
gonna
do
it
unless
Jimmy's
on
the
line
and
he
wants
to
dive
into
the
details.
But
we
have
the
story
in
the
backlog
to
address
that
once
we're
done
with
the
existing
work.
A
H
F
Alright,
so
I'm
gonna
show
off
two
things
today,
the
first
of
which
I've
shown
sort
of
in
part
before
the
filter
modal
that
you
guys
are
all
familiar
with
that
used
to
render
on
the
category
page
and
the
search
page
was
not
functional
before
and
so.
I
put
in
some
work
to
connect
connect
this
model
to
the
graph
QL
server
or
the
back
end
and
I
won't
get
too
far
into
the
technical
details,
but
basically
we
have.
F
We
have
working
filters
now
that
are
generated
based
on
the
possible
aggregations
that
you're
at
the
graphic
you'll
server
returns,
based
on
a
category
ID
if
you're
on
category
page
or
based
on
the
search
term,
if
you're
on
the
search
page.
So
you
know
I
wish
the
I
wish.
These
pictures
were
a
little
smaller,
but
we
can
apply
some
sort
of
filters
within
the
tops.
We
want
to
see
only
cotton
and
we
want
to
see
rain
or
whatever
that
means
and
things
that
are
more
than
$100,
sorry
more
than
$100,
and
there
you
go.
F
D
F
Sure
I
just
I'll
reset
them
so
so
from
from
a
starting
state
you're
on
a
category
page
and
you
open
the
filter,
modal
and
maybe
you
want
to
make
sure
you're
only
looking
at
that's
less
than
$100
and
you're
interested
in
gold
colored
items.
So
you
select
those
filters
this
none
of
this
has
changed.
None
of
this
experience
in
the
filter
model
has
changed
in
terms
of
selecting
the
filters
or
applying.
F
The
once
you
apply
the
filters
that
you
selected
are
put
into
the
URL
and
then
the
category
page
reads:
those
is
constantly
monitoring
the
URL,
Rives
them
and
then
performs
a
new
graph
you'll
query
for
for
for
a
subset
of
the
data
that
it
got
back
previously
on
the
category
page.
So
now
we
have
filtered
results
for
that.
Everything
on
your
will
be
under
$100
at
elite
gold
color
beyond
our
sample.
F
F
So
this
is
different
than
what
you
might
call
layered
navigation,
which
uses
those
aggregations
to
sort
of
drill
down
this.
Just
as
an
initial
like
give
me
all
the
things
that
are
filterable
for
this
category
and
then
drop
them
into
this
mode
on
the
side,
and
it
doesn't
ever
change
for
this
category
and-
and
so
this
is
a
much
better
experience
than
like
than
what
I
was
what
I
showed
off
say
to
two
weeks
ago
and
then
I'll.
Just
real
quick
show
you.
F
So
you
can
go
in
here
and
search
for
something,
and
we
can
say
like
give
me
the
tanks,
and
so
now
the
search
results
are
also
filterable.
So
these
are
you'll
notice,
there's
also
a
category
you
can
filter
for
tanks
and
inside
glasses
and
letters
and
a
certain
price
and
and
the
filters
are
applying
and
then
getting
you
back
results
that
that
PR
was
2166.
F
It's
been
merged
to
develop
now,
hopefully,
it'll
go
out
with
the
next
release
and
if
you
guys
want
to
poke
around
the
color
just
to
see
how
it
was
done
technically
or
get
a
write-up
of
what
I
did
in
this
PR
that'd
be
really
cool
and
I'll,
be
on
the
slack.
If
you,
if
you
have
any
questions,
I
have
one
more
demo.
If
there's
nothing,
if
there's
no
questions
right
now
about
the
soldier
here,.
K
F
I,
yes,
you're,
correct
I,
remember
you
you
added
sorting
for
the
category
page
and
when
I
actually
start
working
on
filtering
I
only
did
filtering
on
the
category
page
and
then
I
realized.
We
also
had
filtering
on
the
search
page
line
to
go
back
and
sort
of
reapply
it
there.
So
I
think
that's
a
good
opportunity
for
a
feature
request.
Yeah.
F
I'll
just
go
quickly
over
this
next
thing.
It's
in
progress
right
now,
so
I
just
wanted
to
sort
of
show
you
something
that
I
worked
on
yesterday,
a
little
bit
so
right
now
on
develop
I've
added
some
items,
my
card
right
now.
The
experience
on
develop
is
that
when
you
are
on
the
car
page
and
you're,
making
a
mutation
such
as
modifying
a
quantity
there's
a
brief
moment.
You
might
not
catch
it
on
the
call,
but
there's
a
brief
moment
where
the
entire
product
form
Gray's
out
and
the
reason
being.
F
We
have
a
race
condition
that
can
occur
when
you
fire
off
two
mutations
at
the
same
time,
where
the
second
we're
one
of
the
where
they
get
out
of
sync,
the
results
on
the
server
come
back
because
they
don't
have
the
context
of
the
prior
mutation.
Basically,
if
I
update
this
quantity
and
in
the
same
time
that
this
network
crust
is
going
on
and
I
clicked
on
the
the
other
quantity,
the
results
could
get
out
of
sync.
The
way
that
we
prevented.
F
That
was
by
monitoring
for
like
an
in-flight
mutation
and
then
whenever
we
had
one
we
would
just
disable
the
UI.
So
you
can't
do
anything
in
the
product
form
right.
So
that's
why
you
see
that
graying
out
experience
right
there,
so
one
way
around
that
is
is
to
not
do
anything
to
the
UI.
So
so,
just
just
to
put
this
out
there.
This
is
the
experience
that
Amazon
actually
has
they.
F
Actually,
if
you
go
on
Amazon
right
now,
and
you
like
change,
if
you
like
change
quantity
inside
your
cart,
they
put
like
a
mask
or
the
only
thing-
that's
gonna
loading
spinning.
You
can't
do
anything
other
sites,
old,
Navy
I,
want
to
say,
do
a
different
experience
where
they
don't
actually
let
you
interact
with
other
things.
They
don't
apply
mask,
but
but
but
it's
masks,
so
you
can't
see
anything
being
done,
but
it's
changed
like
doing
something
in
the
background.
F
F
This
is
the
way
we're
gonna
know.
I
just
wanted
to
show
you
guys.
This
is
a
little
cool
thing.
The
PR
is
20
20
to
15,
it's
just
I,
didn't
I,
didn't
make
it
a
draft
on
accident,
but
but
it's
it's
got
some
some
options
for
how
we
can
handle
this.
The
idea
was
just
to
sort
of
prevent
mutations
from
Rick
having
a
race
condition,
and
this
is
one
way
that
I,
prefer
I
think
is
really
cool
and
that
we
get.
F
G
A
F
So
a
pop-
and
this
might
be
I-
have
I,
might
not
have
done
the
due
diligence.
Yes,
sir
Apollo
has
Docs
room
their
uplink
system
and
they
provide
a
bunch
of
link
implementations
that
people
have
written.
There
is
one
called
link
batch
lets.
You
provide
a
custom
function
for
how
to
batch,
and
that
may
actually
do
what
we
want,
but
it
was
like
overkill
in
a
way
and
I
didn't
want
to
rely
on
someone
else's
implementation.
If
we
could
just
write
our
own
so
and
I
wanted
to
experiment
with
it
so
yeah.
F
This
could
be
a
very
simple
thing.
You
know
you
can
pass
in
the
you
can
pass
in
the
the
thing
that
you're
trying
to
make
sure
it's
cute,
you
know,
can
be
an
operation
name.
Make
sure
that
only
the
mutations
name
update,
item
quantity
get
cuter,
but
definitely
I
could
I
can
see
us
publishing
this
is
it
doesn't
have
to
be
part
of
PW
studio,
separate
packager.
You
know
to
meet
the.
G
Backgrounds,
that's
important
in
if
it
can
be
hard
to
remember
this
Tommy
I,
don't
know
if
this
is
you
looked
on
your
research,
but
for
those
kind
of
wondering
along
those
lines
why
Paulo
seems
to
be
missing
things
or
to
have
features,
we
can't
use
it's
because
a
great
deal
of
the
Apollo
client
is
optimized
or
the
Apollo
servers
that
in
perpetuate
the
link.
Batching
is
a
perfect
example
where
started
public
batch
is
a
perfect
example.
G
The
cheap,
easy
batching,
which
we
would
love,
is
not
available
to
us
when
we're
not
using
an
Apollo
server,
which
Magento's
graph
as
well
is
not
today,
I
shouldn't
talk
out
of
school,
but
an
Apollo
server
may
be
part
of
an
offering
that
we
end
up
with
or
depending
on
the
way
that
you
as
a
you
know,
community
solution,
integrator
deployed.
You
may
end
up
with
an
Apollo
server
in
front
of
Magento
yourself,
and
that
will
enable
a
lot
of
these
things.
G
F
I
think
I
think
this
we
tation
Q
League
is
like
a
really
basic
example.
That's
that's,
and
it's
totally
you
know:
it'll
exist
in
the
vinegar
and
your
or
your
entry
point
in
many
a
concept.
Never
what
it.
Whatever
your
entry
point
is
in
european--
your
own
app,
so
you
can
take
it
out.
If
you
don't
want
that
experience
or
you
know
it
might
not
land
we'll
see
it's
still
an
in-flight
PR.
So.
A
A
I'll
give
that
update
for
community
corner
for
him.
So
over
the
last
couple
weeks
you
know
we've
been
saying
that
we're
working
on
improving
the
process,
improving
our
documentation,
around
community
contribution
and
working
with
pwace,
to
do
I
think
for
a
lot
of
the
community
members.
You
guys
are
probably
used
to
some
of
that
same
process
across
other
projects
of
Magento,
and
so
we've
been
trying
to
figure
out.
How
do
we
evolve,
what
we've
been
doing
an
art
project
and
how
we've
been
working
with
everyone?
A
So
we
have
been
working
on
putting
together
a
community
backlog,
specific
project
within
within
github,
where
everyone
can
go
to
look
at
what
are
the
items
that
the
team
and
the
community
are
prioritizing
for
community
contribution
right
now
we
have
put
this
board
together.
Over
the
last
few
weeks,
we've
done
some
grooming
sessions
with
Jordan
and
Tommy,
helping
out
to
make
sure
that
these
items
are
all
relevant
and
valuable
for
the
project,
and
this
is
a
first
stab
at
kind
of
establishing
this
new
process
and
using
it
moving
forward.
So
we've
also
updated.
A
They
also
updated
our
contributing
documentation,
it's
not
being
right.
Now.
It's
in
process
it'll
be
updated
very
shortly,
but
the
new
process
will
be
outlined
on
this
page
within
the
dev
Docs.
So
you
can
go
ahead
and
read
more,
but
basically,
we've
created
a
compound
board.
You
can
see
what
are
the
items
that
are
in
the
backlog.
You
can
see
the
items
that
we
prioritize
and
say
we'd
like
for
someone
to
pick
up
next,
and
so
the
process
will
kind
of
work
through
the
community
maintainers
right
now,
that's
Jordan!
A
A
So,
for
example,
there's
a
push
notifications,
a
kind
of
proof
of
concept
item
here
and
so
we've
kind
of
defined
the
scope
and
for
this
particular
issue,
you'll
see
that,
typically,
by
the
time
they
hit
the
prioritize
phase,
it
should
have
some
detail
from
the
internal
core
team.
On
how
to
best
implement
this
particular
feature,
and
then
you
know,
once
it's
assigned,
the
team
will
kind
of
help
sherpa
across
the
line.
E
See
a
lot
more
I
think
we
got
some
feedback
to
that.
Like
a
lot
of
community
members,
they'll
submit
a
PR
and
then
look
at
a
ton
of
feedback
from
us
about
how,
like
it,
doesn't
really
fit
our
standards
or
like
that's
not
quite
what
we
were
looking
for
and
like
we
didn't
provide
you
guidance
to
like
this
like.
E
We
should
have
expected
that
so
now,
when
we
tag
something
as
Help
Wanted
we're
gonna
try
to
guide
you
towards
like
the
implementation
that
we
would
be
looking
for,
so
not
like
too
much
hand
Holdings
like
patronizing
community,
but
enough
guide
instead,
like
the
PR
you
submit,
should
be
very
easily
submitted.
If
you
followed
these
guidelines,
so
you
should
see
a
lot
more
content
like
this.
It
should
be
a
lot
easier
to
kind
of
pick
up
tickets
with
zero
hand
off,
but
still
we're
available.
E
If
you
have
any
questions
and
want
to
get
started
on
something,
but
this
is
a
good
example
developer
or
community
member
from
a
Twix
notice
that
we
weren't
using
merge
Cart.
It
is
ready
to
be
implemented.
So
this
would
be
a
great
first
issue
for
somebody
because
it
touches
on
talons.
It
touches
on
our
new
kind
of
opponent,
structure
touches
on
graph,
QL
and
Apollo,
so
I
think
it'd
be
a
really
good
way
to
kind
of
get
dip
your
toe
into
PW
studio.
If
anybody
is
interested.
A
So
right
now
this
is
a
very
set
list
of
items
you
can
see.
We
only
have
11
items
right
now
between
the
backlog
and
prioritize.
It's
a
very
curated
list.
We're
gonna,
evolve
the
process
and
and
of
course,
we'll
start
feeding
the
backlog
with
even
more
items
from
either
community
contributed
feature,
requests
or
bug.
The
community
finds
four
items
that
the
core
team
itself
has
said:
hey
you
know,
based
on
our
current
our
current
focus.
A
A
A
Birthday,
alright.
Well,
that
puts
us
with
a
minute
left.
If
there
are
no
other
questions,
I
didn't
see
anything
else
come
in
from
the
community
for
community
corner
in
terms
of
things
that
you'd
like
to
come
up.
But
if
you
have
those
men
report
again
reach
out
to
Jordan
for
community
corner
items,
that
is
it
for
us
so
onwards
and
upwards
onwards
and
upwards
I
hope
you,
like
it
Smith,
don't
forget
to
smash
like
and
subscribe.
Something
like
that
recording
is
that
it
have
a
great
weekend.
Smooches.