►
From YouTube: PWA Groomng Friday, July 20, 2018
Description
Grooming of the PWA stories
A
Well,
very
good:
well,
that's
let's
go
ahead
and
start
then
talking
about
the
the
homepage
for
for
venya
and
again
kind
of
taking
taking
arts
lead.
Here
we
wanted
to
talk
a
little
bit
more
about
the
page
here
that
we
see
in
the
in
the
the
design.
Documentation
is
on
deadlines,
and
so,
as
you
remember,
in
the
demo
itself,
art
did
a
great
job
of
going
through
the
shop
by
category
experienced
and
look
great.
So
at
some
point.
A
Well,
we'll
get
the
PR
and
merge
merge
that,
but
we
do
have
some
content
areas
like
the
sales
banner,
the
new
arrivals
carousel
and
and
a
few
other
items
that
are
essentially
seamless
block
components
and
sliders.
That
I
think
are
worth
we're,
spelling
out,
and
so
arts,
art
and
I
kind
of
talked
a
little
bit
about
this
earlier
this
week
and
I
told
them
that
you
know
that's
something
we
should.
We
should
definitely
talk
about
talked
about
today
and
use
a
scenario
based
approach
to
describe
them.
A
So,
let's
take
a
look
at
all
the
issues
that
that
come
off
of
this
and
so
I
think
one
of
the
one
of
the
easiest
ways
for
us
to
to
to
shortcut
this.
Unless
github
has
made
some
changes
overnight.
Yeah
to
a
clone
thing
is
this:
take
taken
the
example
that
we
used
for
shot
by
category
and
essentially
do
our
kind
of
our
own
pseudo
pseudo
clone
of
this,
and
so
we're
gonna
do
is
create
a
new
issue
based
on
that
yeah
I'm
curious,
actually,.
B
C
A
Just
copy
paste,
okay,
yeah
I
saw
one
add-on
for
chrome
that
looked
promising,
but
it
also
seemed
to
have
some
interesting
side
effects
to
it
as
well.
So
I
didn't
wanna
I
didn't
want
to
jump
in
it
didn't
look
like
it
was
coming
from
Google
or
a
reputable
source,
so
I'm,
certainly
I
would
love
to
I
would
love
to
find
one
that
would
save
a
lot
of
time
on
our
own,
especially
because
link
back
cool.
A
So
let's
take
a
look
at
what
we've
got
here,
so
we're
gonna
basically
take
the
idea
of
the
implement
shop
by
category
component
and
then
yet,
and
so
we're
gonna
be
take
the
same
same
mentality
here,
which
is
the
implement
you
know
page
component
or
alright.
What
do
you
think
I'm
this
only
so
if
you
look
at
what
we've
got
here
so
I
think
we're
really
looking
at
page
level
component
for
for
something
like
this
correct.
Is
that
what
you're
is
that
kind
of
what
you're
thinking
the
sales
banner.
D
Yep
I
will
interrupt
you
a
little
bit,
I
would
say
according
to
design
for
homepage,
we
have
Z
for
now
five
and
still
not
clarified
for
main
component
same
expression
same
as
block
and
two
sliders
depends
on
actually
our
way
gia.
It
can
be
two
different
sliders
or
even
one
difference.
So
we
will
continue
with
this
question,
but
for
now
let's
create
same
as
page
component.
D
B
C
A
So
just
kind
of
writing
this
out,
based
on
based
on
the
scenario
based
approach
that
we're
taking
so
and
this
one
will
just
say
as
a
developer.
I
want
to
create
a
CMS
page
component
for
venya,
so
that
I
can
so
I
want
to
relate
this.
To
relate
this,
to
some
of
the
things
that
we're
doing
on
the
sales
banners
and
such
so
sales
banner
not
recommended
I'm,
so
it
sales
banners
and
so
that
I
can.
D
E
A
That
I
can
say
revenue
so
that
I
can
yeah
I
want
to
so
that
goals
and
I
think
what
I'd
like
to
do
at
least
because
that
kind
content
can
be
any
piece
of
it
if
we
can
at
least
put
a
shopper
friendly
aspect
of
this
I.
Think
for
me,
that
would
include
examples
could
include
sales,
promos
and
other
content.
A
Inside
of
that,
so
assumptions
I
think,
are
pretty
fair.
It's
a
successful,
set
up
and
completion
of
any
examples,
sample
data
that
makes
sense
to
know
we're
tracking
that
on
another
story
and
as
far
as
the
acceptance
criteria,
so
I
think.
Basically
it's
just
it's
a
rework
of
this
display.
Cms
page
component.
A
We
won't
keep
it
really
simple:
just
testing
a
documentation
or
we're
creating
something.
That's
basically
CMS
level
component.
We
were
in
tested
document
it
so
pretty
basic,
but
I
think
based
on
the
idea
of
creating
a
component
that
is
based
on
data,
that's
inside
of
the
gen,
so
they
wouldn't
expose
that
in
a
meaningful
way.
At
the
beginning
of
something
and
I
think
we
want
to
be
look
at
some
examples
of
what
that
content
could
be
I.
Think
we've
got
some
good
ones
from
saamiya
there
that
we
we've
kind
of
mounted
but
I.
A
D
But
question
just
to
clarify
our
definition
of
done
for
some
tickets,
for
some
chests
can
be
situations
that
graph
QL
is
much
ready,
so
our
definition
on
done
will
be
use
a
simple
data
not
from
magenta
back
and
like
from
some
JSON
file
in
this
component.
What
we
have
to
wait
till
graph
query,
will
graduate.
B
D
B
Yeah,
that's
I
think
that's
exactly
right.
It's
just
in
in
the
future.
It
might
be
an
accelerator
because
there's
a
burden
on
a
developer
who
doesn't
know
what
our
standard
is
for
doing
mock
data
and
if
it's
clear
where
to
put
mock
data,
then
it's
and
it's
easier
and
faster
for
them
in
the
future.
Yep
yep,
perfect,
mm-hmm.
D
A
I
think
it's
a
good
point
right,
I
think
in
the
philosophy
of
kind
of
starting
small,
but
then
evolving
that
graph
kill
will
always
be
a
dependent,
so
we'll
have
to
track
carefully
but
I
think.
Well.
Maybe
we
can
use
this
as
an
opportunity
to
to
understand.
You
know
how
we
get
more
consistent
with
that
with
that
mock
date
and
kind
of
learn
from
what
we've
got.
So,
let's,
let's
see
what
we've
got
and
then
we
can
evaluate
it,
and
then
you
know
iterate
as
needed.
A
A
A
Ok,
very
good
and
I've
got
a
design
to
the
epic
here
so
as
part
of
the
homepage,
as
far
as
the
labels
itself,
just
a
quick
reminder,
so
this
is
going
to
touch
the
venue
concept
right
there
and
it's
in
the
backlog
and
art
I'm
assuming
you're
signing
it
for
this
one
yep
yep.
Do
it
good
just
making
assumptions
here
and
making
sure
and
that's
it?
So
let's
go
ahead
and
let's
go
to
submit
this
one
there
we
go.
A
This,
of
course,
would
be
a
great
place
for
a
cloning
button,
but
we'll
we
won't
beg
dress.
So,
let's
take
a
look
at
the.
Let's
take
a
look
at
the
block
component
here
and
again.
What
I'm
gonna
do
is
take
the
example
that
we
had
here,
but
also
attach
it
to
some
real
scenarios
that
we
that
we
have
in
the
designs
again,
even
if
we
put
those
as
footnotes
that
helps
us
evaluate
things
in
terms
of
a
demo
on
what
to
expect,
even
regardless
of
the
data
source
and
so
on.
A
A
A
You
thinking
this
one
if
it
if
we
do
intend
us
to
conclude
footer
content
unless
it's
the
footer
itself,
we'll
just
need
to
be
cognizant
of
what's
already
created.
I
know.
Jimmy
has
some
examples
already
for
that
one,
so
I
think
just
being
cognizant
of
that
I
think
we
did
a
pretty
good
job
with
that
with
the
recent
demo,
but
just
being
just
to
avoid
duplication
of
effort.
That
would
be
good,
James
and
I
hate
some
feedback
on
the
on
the
word
retreat.
What
did
you?
What
were
you
thinking
about.
B
Retrieve
implies
that
the
the
course
sort
of
story
criterion
is
to
use
live
data
which
we're
not
doing
yeah
I
would
say
so
that
as
developer
I
want
to
create
a
CMS
block
component
for
venía,
so
that
I
can
display
content
I
like
that
I
can
display
rich
content.
Yep
there's
another
bit
to
this
and
I
think
we
talked
about
this
last
time.
B
Ultimately,
we
want
everything
to
be
graph
QL,
but
we
have
set
a
precedent
that
we're
going
to
use
REST
API
is
where
graph
QL
is
not
available.
However,
that
precedent
so
far
only
holds
for
commerce,
cart
and
checkout,
which
this
is
not
that
so
yeah
I
mean
maybe
yeah,
maybe
don't
use
REST
API
is,
but
the
assumptions
have
to
be
I
think
that
the
mock
data
is
successfully
displayed
and
what
are
the
other
features
that
a
CMS
block
component
would
have
I?
D
That
you
can
approach
that
task
yep,
why
not
even
with
the
death?
Let's
do
it
with
API,
not
a
problem.
I
would
say
sorry,
I
would
say
in
addition
to
features
for
the
same
as
block
component
I
would
say
we
need,
in
addition,
titles
there
and
like
a
possibility
to
call
with
a
IG
or
identifier
and
yep
only.
B
Just
gonna
follow
this
sorry,
it's
like
we're,
anticipating
what
the
API
surface
is
going
to
be
so
yeah.
Do
you
want
to
try
and
make
a
two
component
architecture
with
one
that
does
as
a
fetch
of
the
CMS
content
and
then
an
inner
component
that
renders
it
or
are
you
expecting?
Oh,
you
said
that
you
would
like
to
be
able
to
just
simply
argue
a
CMS
block,
ID
or
CMS
record
yeah.
D
C
B
I
think
we
have
to
I,
don't
want
to
expand
scope
on
the
story,
but
I
I
think
we
have
to
think
about
what
the
merchants
sort
of
persona
is
gaining
from
there
being
a
CMS
block.
Not
just
the
developer
because,
but
you
know,
developer
doesn't
have
any
reason
just
by
ourselves
to
make
something
that
renders
which
content.
But
we
want
the
rich
content
that
the
merchant
or
content
author
creates
to
appear
in
our
progressive
web.
A
So
a
frame
it
this
way,
then
I
think
so.
One
of
the
things
I
think
when
we
talked
about
last
week's
last
week's
grooming
session
is
I.
Think
it's
most
useful
when
we
look
at
this
at
the
tasks
level
and
essentially
we're
looking
at
so
what
we're
doing
here
is
very
close
to
what
that
task
level
would
be,
and
the
instance
of
github
there's
no
way
to
assign
a
task
is
basically
just
a
small
story.
A
Probably
three
points
points
or
smaller,
and
so
for
the
purposes
of
this,
what
it's
I
think
would
it
feel
better
for
us
to
create
another
story
after
this,
this
links
into
that
is
an
epic
or
something
similar
that
has
that
shopper
experience
that
then
this
would
just
hang
off
and
essentially
as
a
task.
So
is
that,
is
it
hopeful
to
me?
It
feels
more
a
little
in
that,
but
I,
don't
wanna,
make
sure
we're.
B
Not
short-sighted
so
a
little
bit,
but
if
we
break
off
that
task,
then
what
remains
is
the
presentational
element
of
it,
which
assumes
that
it
has
already
received
the
data
and
it
appropriate
stayed
and
that
the
data
is
relevant.
Okay
when
it
comes
to
just
rendering
rich
HTML,
we
know
we're
gonna
have
to
do
it
using
the
sort
of
dirty
back.
You
know
like
channel
of
calling
the
secret
API
and
react
that
lets
you.
Do
it's
not
secret.
It's
just
you
know
they
discourage
you
from
doing
it
yeah.
B
B
So
yeah.
We
should
talk
about
what
the
merchant
scenario
is
like
the
merchant
poem.
Do
we
want
to
talk
about
the
merchant
publishes,
a
piece
of
content
based
on
a
name
that
the
merchant
knows
they
have
to
create
something
with
this
name
right
and
then
it
appears
that
would
so
that
translated
technically
the
implication
would
be
that
inside
the
implementation
you
have
to
look
and
see
if
a
block
exists
by
that
name
and
if
not,
you
know,
fail
silently
or
gracefully.
Okay,.
A
B
A
C
E
A
A
And
then
got
it,
lose
three
home
paging
and
we'll
modify
the
epoch
and
I
think
that'll
be
good.
All
right,
cool
I'll
submit
that
one
excellent
perfect
all
right,
so
we
had
two
other
things
on
the
home
page.
We
can
certainly
cover
quickly
on
what
I
also
want
to
do
is
just
to
make
sure
that
we've
got
Alex
on
here
as
well.
Alex
I
know
you
know,
I
want
to
make
the
most
most
use
of
your
time.
I
know
you're
working
on
the
bulk
API
work
as
well.
C
C
A
C
We
already
can
use.
There
are
two
pull
requests
which
JA
for
blocks
and
CMS
pages,
which
are
doomed,
was
not
merge
yet
yeah
that
something
I
can
check
on,
because
there's
some
tests,
I
felt
and
generally
more
take
this
administrative
function
for
for
the
speed
of
the
process
for
the
like
components
of
the
graphical
which
we
need
for
our
development,
yeah
I
mean.
B
Graph
QL
is
one
of
those
technologies
that
it's
very
easy
to
make
up
unnecessary
solutions,
because
it's
flexible
language,
it's
flexible
specification,
a
lot
of
the
things
that
you
think
you
need
to
create.
You
don't
we're
just
using
Apollo
right
now,
which
is
so
very
feature
full
that
we
recommend
getting
familiar
with.
B
C
A
What
it
seems
like
now,
that's
good
yeah
I,
mean
I.
Think
for
the
purpose
of
this.
We
just
want
to
make
me
I
think
you
sit
in
a
very
unique
position
with
either
even
this
products
dependencies
to
help
us
carry
this
further
again.
Just
put
it,
but
you
know
anything
we
can
do
to
at
least
build
your
and
help
your
understanding
of
this,
and
maybe
it's
just
continuation
of
these
components,
but
I
wanted
to
take
a
pause
to
make
sure
there
are
there
any
examples
or
demos
or
proofs
of
concepts
based
on
your
learnings
there?
C
B
Yeah
I'd
appreciate
it
if
you
could
iterate
on
yeah,
if
you
could
work
on
getting
those
Business
Objects
available
by
making
the
right
requests
to
them
correct
lately
in
the
core
team,
we've
been
asking
them
weird
questions
like
you
know:
how
do
you
expose
design
overrides
or
a
tree
of
page
builder
content?
Yeah,
you
know
those
are
design
level
questions.
This
is
just
covered,
so
you
know
thank
you
for
doing
the
kind
of
boring
work
of
just
extending
the
coverage.
That's.
C
A
Make
it
some
fun,
although
that's
what
it
seems
like
no
I
I,
haven't
talked
to
this
team.
A
lot
I
think
the
karke.
The
success
for
this
project
and
really
all
of
all
of
Magento
has
a
lot
to
do
with
the
coverage
that
we
make
there
right,
because
that
really
unleashes
the
possibilities,
and
so
we
appreciate
it
so
I'm
glad
you're
having
fun
with
it
as
well.
So,
okay!
A
Well
this
sort.
The
spirit
of
this
I
think
again,
looking
at
the
the
attendees
that
we've
got
here,
I
think
the
best
thing
we
can
do
is
probably
knock
out
these
last
two
stories:
yeah
both
products,
slider
and
gallery
I
think
we
had
a
lot
of
contents
or
to
work
from
there
and
then
and
then
we
can
call
it
call
it
an
afternoon.
So,
let's
so,
let's
take
again
take
a
look
at
our
templates.
We've
that
we've
created
here
I'm,
sorry
guys.
B
B
A
So
so,
if
we
take
a
look
at
what
we've
got
here,
so
we
talked
about
sliders,
we've
got
a
couple
different
related
items
when
I
think
about
sliders
I.
Think
about
this
carousel
here,
but
I
do
know
again
how
art
described
it.
There's
almost
a
superset
of
the
sliders
that
do-
and
don't
you
know
include
this-
is
this-
is
a
secure,
solar
as
a
slider.
A
A
So,
let's
take
a
look
at
where
we
left
off
with
the
last
story
and
that's
it's
a
venya
future
suggestion,
and
so
for
this
and
again,
let's
take
the
spirit
of
this
being
more
of
a
task
than
a
story
just
because
I
think
that's
most
helpful
for
this
forum
will
attach
this
to
more
the
the
scenario
than
with
with
the
epic.
So
when
taking
about
art,
you
are
working
on
this
and
as
a
developer,
I
want
to
create
a.
D
Ship,
according
to
this
logic,
yep
yep,
exactly
products
like
that
so
I
said
well:
I
want
to
create
yeah
components
for
root
component
sylvania
wisdom,
okay,
yes,
title
says:
new
arrivals
means
it's
a
new
one.
In
magenta
backend
we
have
a
shared
checkmark
set
this
product
as
a
new.
So
this,
oh,
we
can
collect
whole
products.
Some
amount
of
or
all
products
from
some
category
can
be
also.
B
If
it's
a
widget
that
has
a
configuration,
I
would
imagine
that
it
only
has
two
non-visual
configurations,
which
is
you
know
such
first
or
I
mean
well,
let's
see,
okay,
so
we've
got
a
carousel
that
displays
images
from
any
place
in
the
catalog
or
this
being
a
product
widget.
It
would
always
be
displaying
just
the
images
for
what
product
right,
yeah
I
think
yeah
yeah
okay,
so
this
is
just
confusing
to
me
because
new
arrivals,
oh
yeah,.
B
This
is
a
product
slider.
This
isn't
it
yeah,
so
yeah,
coz,
okay,
because
that
says
flower
fields,
maxi
dress.
What
I
want
to
know
from
you
Sonia
is
that
when
you
navigate
to
the
right
and
the
cover
flows
over,
is
this
the
same
product
and
a
different
picture,
or
is
it
a
new
product?
It's
a
different
program.
So
this
is
actually
a
check
request,
yeah,
so
that.
E
B
B
Are
scared
they
had
to
write
out
a
set
of
tools
that
are
the
only
thing
you
can
use
to
talk
to
graph
QL
onto
it,
and
it's
all
written
out
in
this.
You
know
in
in
the
domain-specific
graph
tool,
and
it
was
so
like
when
right
now,
there's
no
looked
up
a
single
product
interface.
So,
if
I
want
the
products,
what
I
do
is
I
filter
the
entire
product
collection
on
the
URL
and
then
I
take
the
only
result,
mm-hmm
and
that's
just
the
location
and.
B
B
There's
a
published
version
of
Deb
Docs
you'll
find
that
there's
this
concept
of
a
filter,
input
type
that
canned
on
a
number
of
different
operators
like
equals,
doesn't
equal
greater
than
less
than
contains,
and
you
can
run
them
on
on
the
entire
catalog
of
products
so
like
these
could
all
basically
be
the
same
query.
Just
a
products.
Query
that
passes
back
enough
to
populate
tile
and
it's
the
variables
that
get
sent
in
that
determine
what
kind
of
thing
it
is
which
is
great.
It's
it
pushes
that
logic
to
the
very
edges.
B
A
B
Right
great
I'm,
just
saying:
there's
some
discovery
to
be
done
and
don't
ask,
and
there
is
like
discovery,
whether
it
currents
stays
catalogue
graph
kills
capable
of
filtering
products
to
sense
by
new
rival
scenario.
That
says
new
arrivals.
So
we'll
take
it
we'll
say
you
know,
as
a
shopper.
I
want
to
see
the
newest
things
in
the
store
in
an
attractively
displayed
way
more
things.
B
I
want
to
do
quickly,
showcase
the
things
that
are
new
in
store
by
placing
a
you
know
component
that
can
be
configured
to
filter
on
anything
yeah
to
place
it
in
the
on
the
home
page
into
title
at
new
arrivals,
and
you
know,
and
as
a
developer,
I
guess:
I
want
to
fetch
products
by
criteria.
So
the
underlying
thing
fetching
products
by
criteria,
is
satisfied
by
the
graphic
ul
service,
but
there's
some
discovery
to
be
done
about
whether
it
satisfies
all
of
the
use
cases
got
it.
A
E
A
Alright
about
this
so
I
think
the
purpose
of
this
we
want
to
you
know
as
a
developer,
I'm
going
to
create
a
product
slider
component
for
vania,
so
that
I
can
display
rich
content
by
criteria
for
the
magenta
CMS.
So
it
just
has
the
ability
to
do
you
know
the
criteria
that
it
is
capable
of,
and
so
I
think
as
part
of
that,
as
example,
includes
them,
new
arrivals
carousel-
maybe
not,
but
that
is
like
they
were.
That's
the
idea.
That's
right.
B
A
Way
so,
let's
onion
so
I
think
with
the
assumptions
we
can
assume.
So
you
know
successful
setup
in
completion
sample
data.
Similar
we've
talked
about
will
forma
ensure
we've
got
that,
but
then
acceptance
criteria
is
a
summary
of
the
graph
QL
coverage.
Basically
say
we
we
were
going
to
display
as
far
as
what
we
know
and
then,
as
part
of
that
would
be,
this
is
actually
might
be.
Where
Alex
comes
in
would
be.
You
know,
kind
of
call
creation
of
graph
QL
tickets,
but
shared
basically.
B
A
I
think
I
mean
yeah.
Obviously
what
there's
some
of
the
earlier
designs
we're
gonna
win
with
some
assumptions,
but
if
we
know
it
with,
you
know
with
the
beginnings
of
it,
I
think
that
makes
sense
for
a
sample
and
reference
theme,
but
I
think
we
also
want
to
identify
the
case
of
where
it's
not
so,
that'll
make
extensibility
and
other
things
easier.
So
cool
mock
data
so
so
guys
help
me
with
out
a
little
bit
on
the
acceptance
criteria
for
this,
and
so
part
of
is
what's
covered.
A
B
What
I
think,
what
I,
what
I
assume
that
art
you
want
to
do
is
is
start
by
creating
the
visual
component
and
then
later,
when
the
component
is
done,
using
simple
mock
data
or
our
coded
values,
then
you
attend
to
hooking
it
up
to
data,
and
then
you
might
have
to
make
some
small.
You
know
changes
to
the
expected
to
model,
but
you
know
I.
It
sounds
from
the
type
of
work
that
you
typically
view
that
that
would
be
the
way
that
you
do.
It
am
I
wrong.
Yep.
C
D
More
one
more,
even
if
we
will
adhere
a
lot
of
logic
like
I
wanna
have
in
this
component,
whole
products
by
IG
I
will
add
their
IG.
When
I
will
put
this
component
in
the
template
or
I
want
to
have
the
products
from
categories
or
from
something
else.
In
this
case
you
can,
you
can
suggest
we
can
decide.
Do
we
need
second
component?
D
If
you
will
make
big
calorie
slider
component
inside
and
are
logically
any
any
type
of
view,
any
type
of
settings
any
whole
bunch
of
in
properties
we
actually
known
each
second
or
even
any
other
kind
of
gallery
visual
components.
We
can
use
only
one
with
a
lot
of
settings
or
we
will
create
true
or,
for
example,
three
according
to
design
simple
easy.
For
example,
new
arrivals
can
use
only
I,
just
category
I
mean
product
IDs
I
can
manually
add
their
or
please
show
me
our
products
from
category
Donald.
B
Concerned
about
overloading
one
component
with
functionality,
because
it
implies
that
there
is
well
there's
runtime
configuration
like
as
I'm,
assuming
that
you
have
one
gallery
component
and
the
way
that
you
make
it
choose
what
its
internal
template
would
be.
Is
that
you,
you
argue
in
a
react
component
constructor
as
a
prop
right,
yep
yep,
there's
a
lot
of
branch
logic
in
there
that
I
think
you
don't
need
to
do
that.
B
Runtime,
because
you
have
these
components
that
can
be
hard-coded
because
they
know,
because
it's
a
strongly
typed
system
that
the
contract
they're
receiving
is
product
and
I,
can't
think
of
anything
that
you
apply,
that
carousel
look
and
feel
to
them
products.
So
it
sounds
to
me,
like
you
might
be
doing
something
that
I
do
all
the
time
every
day,
which
is
make
things
too.
Generic
too
quickly
is
what
it
sounds
like
to
me.
B
B
We
are
building
view
and
then
instrumenting
it
as
much
as
possible
with
the
time
we
have
left
that
ringing
a
bell
for
anyone.
This
is
like
and
buy
view.
I
mean
view1
thing
to
use
and
you
are
writing
react
component
and
when,
when
it's
done,
then
we
can
talk
in
another
channel.
We
have
several
different
channels,
so
you
could
speak
through
about
different
stretch
goals,
attaching
it
to
live
data
yeah
coming
up
with
a
generic
pattern
for
it.
So
there
it's
totally
reused
but
not
suffer
from
you
know:
performance
loss
or
from
over
generic-looking
code.
B
You
know
when
I
unwrap
a
component
like
60
times
and
I,
find
out
there's
a
list
who
the
only
job
is
to
do.
Iteration
I
get
mad
I'm
like.
Why
do
we
need
this
thing
called
a
list
when
we
already
have
the
construct
in
the
language?
So
it's
you
know
I
do
it,
we
do
it,
but
yeah
I
mean
just
write
a
stroke.
You
know
right.
I
do
arrivals
come
on
start
there
yeah
that
makes
sense,
panned
engineer
size
outward
yeah.
B
A
Quite
a
hit:
do
it
one
all
right,
so,
let's
juice
good,
yes,
I,
think
so.
Fritz
I
think
with
that
in
mind,
if
we
really
simplify
this
based
on
a
very
simple
use
case,
I
think
we
started
off
with
you
know,
creating
a
summary
of
the
coverage,
understanding
that
it's
creating
a
simpler
components.
Do
we
want
to
do
anything
in
the
mock
data,
or
do
we
just
go
straight
to
kind
of
testing
of
documentation,
so
I
understand
here's
the
example
test.
A
B
C
B
B
D
D
B
Pretty
cool
I
think
you
will
notice
that
it
feels
like
you're
duplicating
test
logic,
but
I
would
caution
you
from
trying
to
import
the
same
logic
into
both
the
test
and
the
and
the
storybook,
because
they
operate
in
different
environments.
But
yeah.
If
you
make
a
storybook,
then
that
effectively
services,
both
testing
and
documentation,
because
I
know
another
developer,
pulls
out
that
storybook
and
sees
every
conceivable
states
of
the
of
the
component
in
isolation.
Yeah.
A
A
B
Please
don't
take
this
the
wrong
way
if
this
is
totally
unnecessary
for
me
to
say,
but
as
contributors
grow
and
we
get
junior
people,
we
might
have
to
remind
people
that
it
should
work
on
mobile.
So
maybe
don't
have
hover
State,
so
it
should
be
mobile
first
and
it
should
be
performant
and
it
should
not
scroll
in
a
jerky
way
got
one
day.
One
day.
E
G
A
Yeah
and
how
about
this,
but
I
think
we
should
get.
What
we
can
do
is
a
maybe
of
a
footnote
for
for
Sami
on
this
one
I
think
yeah.
We
should
probably
talk
about
sincerity,
but
formalize
of
documentation,
tasks
for
that
we
can
work
on
with
Calculon,
essentially
or
design
principles
like
basically
a
list
of
assumptions
that
we
could
use
this
boilerplate
to
link
to
fur
for
every
one
of
these
like
what
they
design.
A
We
believe
that
it
does
this
this
this
and
this
because
I
know
we
have
it
and
we've
talked
about
it,
but
just
making
making
something
with
that
as
a
something
we
fall
back
on.
In
terms
of
you
know,
expectations
or
browser
acquire
there's.
A
lot
of
things
like
that
that
have
probably
worthwhile
I
mean.
E
B
A
A
Let's
finish
off
this
in
terms
of
what
we've
received
an
estimate
we'll
copy
that,
and
then
at
least
us
at
least
get
us
started
on
the
product
gallery,
which
I
know
that
Martin
and
I
had
talked
about
earlier
so
art
on
this
one
so
based
on
where
we
just
left
off.
What
would
you?
What
would
you
consider
is
an
estimate
for
this.
D
A
D
Big
yep,
let's
update
okay
and
wonderful
clarifications,
is
see
all
new
arrivals.
It
looks
like
we
have
to,
for
example,
fun
hourly,
which,
as
a
blank
empty
button
just
add
cells
infusion
looks
like
we
have
to
create
some
War
real
with
some
some
page
for
for
these
products,
where
we
have
a
list
of
them.
We.
E
E
A
And
I
think
given
this
given
the
size
given
the
size
of
the
story,
I
think
maybe
you
and
I
offline
can
kind
of
break
this
out
and
a
little
bit
smaller
stories.
I
do
like
to
get
things
down
to
the
one-two-three
level
for
this
one
for
this,
and
so
maybe
we
can
break
those
down
as
almost
tasks
per
se,
but
I
think
I
mean
this
is
a
lot
right
now.
I
think
that's
good,
but
I
think
we
can
break
that
down.
I
think
that
would
be.
That
would
be
super
helpful.
A
I
would
I
would
not,
but
I
would
have
in
the
documentation
I
would
we
have
to
find
a
way
to
classify
things
as
essentially
stretch
goals
or
optional
like
work,
because
I'd
like
to
come
back
around
to
it,
but
a
food
fight?
If
we
need
to
I
think
we
need
to
find
a
way
to
clearly
denote
things
that
are
essentially
iterations.
A
A
Implement
product
component
orbit
all
right
again
without
a
clone
button,
we've
cloned!
So
let's
talk
about
a
little
bit
and
I
think
this.
This
this
discussion
make
may
cover
the
next
few
minutes
of
this.
But
I
know
that
when
we
think
about
galleries-
and
we
think
about
sliders-
there
they're
related
right,
but
so
we
think
about
galleries.
What
I
think
my
galleries
have
thinking
about
the?
Where?
Is
it
right
here?
A
Sorry,
this
guy
right
here
so
I'm
thinking
about
the
recommended
for
you
example,
so
I
think
I
think
that
just
to
get
kind
of
get
crisp
on
on
our
terminology
here,
and
so
when
I
think
about
this
as
a
shocker
scenario,
what
we'd
like
to
do
is
essentially
do
map
this
to
at
least
best
effort
on
recommended
for
you.
We
have.
B
To
do
with
our
own
implementation
of
it,
I
mean
barring
the
idea
that
one
of
them,
one
or
more,
might
be
personalised
and
so
needs
to
render
out
a
different
pipeline,
but
that's
it.
The
other
thing
is:
we
need
to
keep
reminding
ourselves
the
difference
between
a
slider
carousel
gallery,
zoetrope
album.
A
Runs
all
those
businesses,
so
yeah,
so
I
think
I
think
for
the
purposes
of
this
one
again,
if
we
really
think
about
this
and
I'm
really
I,
think
I'm
embodying
the
spirit
of
these
being
more
tasks.
I
think
I
mean
I
feel
like
we
can
relax
the
nomenclature,
but
I
think
as
a
follow
up
much
like
kind
of
the
design,
standards
and
principles
of
pretty
much
everything
we
do
here.
Will
that
be
moveable
first
and
others?
A
Let's
look
at
that
as
kind
of
referenceable,
almost
auxilary
documentation,
so
that
we're
crisp
we're
crisp
with
ourselves
externally,
but
internally
I
think
we
can.
We
can
be
a
little
bit
more
flexible.
What
that
is
just
in
the
spirit
of
tasks
and
instead
of
kind
of
you
know,
but
I
think
I
do
agree.
That's
that's
something
we
need
to
I
checked
down
so
with
the
the
product
gallery
component.
A
Again,
if
we
look
at
this
as
an
example
who
recommended
for
you,
carasau
I
think
there's
a
lot
that
we
can
a
lot
that
we
can
borrow
from
the
slider
story.
So
if
you
look
at
this
being
a
a
product
gallery
component
that
again
is
attached
to
a
shopper,
shopper
story
for
the
for
the
new
homepage
experience
it's
about
displaying
rich
content
by
criteria
from
the
CMS,
and
so
we're
gonna
do
our
very
best
to
get
as
far
as
you
can
with
the
coverage.
A
I
think
part
of
this
story
of
stuff
is
going
to
include
the
summary
of
coverage
and
understanding
what's
there
and
what
isn't
so,
there's
a
bit
of
discovery
there,
but
then
also
creating
that
that
component
of
the
the
product
gallery,
based
on
based
on
the
design,
work
that
Sammy
and
team
have
done
again.
It's
pretty
high
level.
It's
gonna
be
a
fairly
that
larger
one
and
I
do
want
to
break
this
up
afterwards
in
a
similar
way
that
what
we're
gonna
do
for
slider
and
kind
of
one.
Two
three
point
stories.
A
B
I
think
I.
Think
media
in
general
is
a
pretty
deep
topic
again.
We
should
make
sure
not
to
try
and
cover
every
possibility.
Now
look
at
the
API
media
objects
can
have
lots
of
unusual
properties
they
can
have.
They
can
be
images
that
can
be
videos,
they
can
need
to
be
resized,
and
we
should
make
sure
that
we
only
implement
this
so-called
happy
path
yeah.
So
it's
important
to
say
what
the
minimum
acceptable
behavior
of
a
of
a
product
gallery
is
versus
a
product
slider.
On
a
carousel.
B
E
It
doesn't
swap
so
this
is
what
I
had
discussed
with
Jimmy.
So
what
it
is
is
the
concept
is
that
if
a
merchant
wants
to
promote
certain
products
more
than
others,
because
either
sales
are
lagging
or
they
want
it's
a
new
sales,
for
that
would
have
a
greater
amount
of
real
estate
in
that
gallery,
where
they're
all
independently
clickable
items,
so
the
bottom
portion
of
it
can
be
swiped
or
it
can
be
rotated,
but
it
does
not
change
the
focus
image
so.
C
B
C
B
I
think
it
should
be
pointed
carefully,
because
this
is
still
an
area
of
great
deal
of
their
action,
so
it
needs
to
be
in
the
same
way
that
we
described
the
slider.
It
needs
to
be
an
accessibility
compliant.
It
means
to
be
mobile
first
in
its
interactions
and
it
needs
to
it
needs
not
to
break
the
illusion
of
native,
so
make
sure
that,
where
possible,
if
you
are
moving
down
that
surrounds
that
you're
not
layout
thrashing
that
you're,
not
this
is
more
technical.
B
You
know
fashion
you're,
using
hardware
acceleration,
so,
for
instance,
for
the
you
know,
the
scrolling
occurs
outside
of
a
regular
scroll
mechanism.
You'd
want
to
use
a
translate
rather
than
setting
a
positioning
property,
that
kind
of
thing
yeah,
yeah,
and
so
those
are
not
acceptance.
Criteria
for
the
story
so
much
as
like
those
are
the
details
of
what
we
would
roll
up
into
AC
as
accessible
and
doesn't
jank,
because.
C
A
Exactly
I
almost
see
them
as
two
different
resources.
One
is
I,
think
one
is
technical,
so
a
set
of
technical
standards,
but
then
also
experiential
ones,
right
ions
that
are
related
to
the
shopper.
Experience
that
do
things
like
browser
requirements.
Do
things
like
accessibility,
things
that
are
would
kind
of
an
end
user
in
mind.
So
yeah
yeah.
C
A
Think
that's
actually
really
good
finding
from
today
that
we
can.
We
can
look
at
ourselves
internally
and
and
share
what
the
team
of
the
not
coming
up.
It's
pretty
alright.
So
this
is
the
basics.
I
think
we've
revealed
a
really
good
correlation
or
lack
of
correlations
for
the
primary
and
secondary
image,
which
is
good.
We
made
this
a
little
bit
easier.
Art
again,
I
took
I,
took
the
basics
of
what
we
just
covered
in
the
and
the
slider
and
adapter.
A
D
E
E
B
And
again
I,
if
you
pull
up
the
schema,
you
might
observe
that
in
the
latest
alpha,
the
extended
attributes
are
actually
extended
directly
on
to
the
schema
like
there
is
a
first
class
property
in
the
product,
interface
called
like
Erin
recommends
or
whatever
that
lumen
extension
attribute
is.
So,
if
there's
a
reviews
and
a
bizarre
voice,
integration
that
populates
in
the
AV
that
you
could
get
at
it
them.
But
again,
we
would
definitely.
A
That
brings
great
clarity,
so
I'm
any
other
on
any
other
questions.
Nope
nope,
excellent,
all
right!
Well,
that
puts
us
at
time.
You
know:
we've
knocked
out,
I,
think
four
really
really
good
stories
and
then
we've
got
I,
think
some
follow-ups
in
terms
of
some
standards
and
other
things
that
we
want
to
spell
out
it
kind
of
a
larger
level.
So
that
gives
us
some
things
to
take
a
look
at
in
parallel.
So
our
you
know
appreciate
your
help.
As
always
yep
we
have
a
question
I.
G
B
A
Okay,
no
that's
good!
So,
let's
say
because
the
others
have
just
come
up
with
a
recent
sprint.
So
we've
got
new
external
content.
That
I
think
it's
a
good
point
by
samya.
We
will
weep
across
these
new
stories.
Add
them
I,
think
that
would
be
hugely
valuable
and
evaluate
the
wiki
content
with
jimothy
on
on
how
we
would
expose
that
with
the
documentation
as
needed.
So
it's.
G
E
A
All
right
well,
thank
you.
So
much
again,
thank
you
again
for
hanging
in
and
with
us
and
again,
congratulations
on
all
of
your
great
work
with
the
demo
looking
forward
to
see
the
PR
for
that
we're
gonna
take
a
look
at
that
and
bring
that
in
as
soon
as
we
can.
But
if
you
have
any
other
questions
or
anything
else,
don't
don't
hesitate
to.
Let
us
know
I'd
be
great
weekend
because
you're
ahead
of
us
on
that
one
and
and
then
we'll
talk
to
you
soon,
yeah.